Consider the following scenario:
- You have an on-premises Active Directory object.
- Directory synchronization is used to sync the Active Directory object to Windows Azure Active Directory (Windows Azure AD). This creates a linked object in Office 365.
- You delete the on-premises Active Directory object.
In this scenario, the linked object isn't removed from Windows 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 Windows Azure AD object.
To fix this issue, follow these steps:
- Manually run a directory synchronization update. 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 Windows Azure AD, you can manually remove the orphaned object by using one of the following Windows Azure Active Directory Module for Windows PowerShell cmdlets:
Remove-MsolContact
Remove-MsolGroup
Remove-MsolUser
For example, to manually remove orphaned user ID john.smith@contoso.com that was originally created by using directory synchronization, you would run the following cmdlet:
Remove-MsolUser –UserPrincipalName John.Smith@Contoso.com
For more info about Windows PowerShell cmdlets, go to the following Microsoft website:
Still need help? Go to the
Office 365 Community
(http://community.office365.com/)
website.
Article ID: 2709902 - Last Review: May 15, 2013 - Revision: 8.0
Applies to
- Microsoft Office 365 for enterprises (pre-upgrade)
- Microsoft Office 365 for education (pre-upgrade)
- Windows Azure Active Directory
| o365 o365a o365e o365062011 pre-upgrade o365022013 after upgrade KB2709902 |