- Cause 1: The on-premises AD DS is no longer available. Therefore, you can't manage or delete the object from the on-premises environment.
- Cause 2: You deleted an object from the on-premises AD DS. However, the object wasn't deleted from your cloud service organization. This is unexpected behavior.
- Install the Azure Active Directory Module for Windows PowerShell. For more info, go to the following Microsoft website:
- Connect to Azure AD by using Windows PowerShell. For more info about how to do this, go to the following Microsoft website:
- Disable directory synchronization. To do this, type the following cmdlet, and then press Enter:
Set-MsolDirSyncEnabled –EnableDirSync $false
- Check that directory synchronization was fully disabled by using the Windows PowerShell. To do this, run the following cmdlet periodically: This cmdlet will return True or False. Continue to run this cmdlet periodically until it returns False, and then go to the next step.
Note It may take 72 hours for deactivation to be completed. The time depends on the number of objects that are in your cloud service subscription account.
- Try to update an object by using Windows PowerShell or by using the cloud service portal.
- Step 4 may take a while to be completed. There is a process in the cloud service environment that computes attribute values. The process must be completed before the objects can be changed by using Windows PowerShell or by using the cloud service portal.
Force directory synchronization by using the steps on the following Microsoft website:
- If some updates and deletions are propagated, but some deletions aren't synchronized to the cloud service, perform typical directory synchronization troubleshooting procedures.
- If all updates and deletions aren't synchronized to the cloud service, contact Support.
Set-MsolDirSyncEnabled -EnableDirSync $true
Article ID: 2619062 - Last Review: Dec 28, 2016 - Revision: 1