Identifying DirSync provisioning errors in Office 365įor more information about how to troubleshoot, refer to the following articles: Identify directory synchronization errors in Office 365 To do this, refer to the following support articles: Get-AzureADGroup -SearchString | fl ObjectIdĬheck for DirSync errors. Get-AzureADUser -SearchString | fl ObjectId Get-MsolGroup -SearchString | fl ObjectId Get-MsolContact -SearchString | fl ObjectId Get-MsolUser -UserPrincipalName | fl ObjectId The ObjectId parameter value can be found in Azure AD (It will be in the form of XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX). This request must be made by using the ObjectId parameter. If there is no result, ask Microsoft to submit the object for a forward sync from Azure AD to Exchange Online. If the object is present in Azure AD, confirm whether the object is present in Exchange by using the Get-User cmdlet. If object is not present in Azure AD, make sure that the object is in scope of Azure AD Connect. Note If a user needs a mailbox, the UsageLocation parameter is mandatory and has to be populated. Then each time you connect, run the following to access the AzureAD commands.Ĭonfirm that the object exists in the Azure AD by using the Azure AD PowerShell module. For more information see Azure Active Directory PowerShell. To use the AzureAD module, install the following module (one time and in a PowerShell window running as administrator). Then each time you connect, run the following to access the MSOL commands. For more information see Azure ActiveDirectory (MSOnline). To use the MSOL module, install the following module (one time and in a PowerShell window running as administrator).

There are two Windows Azure Active Directory modules to administer Azure AD through PowerShell. An Exchange Online object (such as a user, contact, or group) is not created or updated in Azure Active Directory (Azure AD) Connect.

Outlook identity not updated