Consider the following scenario:
- You have an on-premises Active Directory object.
- Directory synchronization is used to sync the Active Directory object to Microsoft Azure Active Directory (Azure AD). This creates a linked object.
- You delete the on-premises Active Directory object.
In this scenario, the linked object isn't removed from Azure AD.
This issue may occur if one of the following conditions is true:
- Directory synchronization hasn't yet occurred.
- Directory synchronization unexpectedly failed to delete a specific cloud object and results in an orphaned Azure AD object.
To fix this issue, follow these steps:
- Force directory synchronization. For more info about how to do this, go to the following Microsoft website:
- Check that directory synchronization occurred correctly. For more info about how to do this, go to the following Microsoft website:
- If sync is working correctly but the Active Directory object deletion is still not propagated to Azure AD, you can manually remove the orphaned object by using one of the following Azure Active Directory Module for Windows PowerShell cmdlets:
For example, to manually remove orphaned user ID firstname.lastname@example.org that was originally created by using directory synchronization, you would run the following cmdlet:
Remove-MsolUser –UserPrincipalName John.Smith@Contoso.com
Still need help? Go to the Office 365 Community
website or the Azure Active Directory Forums
Article ID: 2709902 - Last Review: July 9, 2014 - Revision: 17.0
- Microsoft Azure
- Microsoft Office 365
- Windows Intune
- CRM Online via Office 365 E Plans
- Microsoft Azure Recovery Services
- Office 365 Identity Management
|o365 o365a o365e o365022013 o365m KB2709902|