GSX Blog

Top Office 365 Issues: Unable to login due to Azure AD Connect sync issues

Posted by Pavan Reddy on Tue, Jan 24, 2017

robot-user-3.png

When users are unable to access their mailbox or SharePoint on Office 365, this can sometimes be due to sync issues. Most organizations will use AAD connect (previously called DirSync, and AD sync) to sync their on-premise identities to their Office 365 environment, so it’s important that these two systems communicate to make it possible for users to access what they need on Office 365.

An administrator will go through a couple of steps to identify the issue in this case. First, they’ll request the on-premise account ID from the user. Then, they’ll check the sync time in AAD to see if the sync failure happened and re-run the sync schedule. They’ll request that the end-user wait until the sync completes to try again, and hope it works this time.

With GSX, administrators can significantly reduce the time spent identifying sync issues. GSX monitors the Azure AD connect server synchronization cycle and notifies the administrators in case the sync cycle fails or stops for any reason. GSX gathers the information on a number of objects available on-premise and in AAD, allowing administrators to identify the objects not available or not synced to Azure, letting them proactively address the issue before a user complains.

GSX provides out-of-the box monitoring to ensure your Unified Communications applications are performing the way they should, whether they're on-premise, hybrid, or in the cloud. Find out more >>

landing365Top.png

Tags: Office 365 monitoring, Azure AD Connect performance, Azure AD Connect, SysAdmin Top Issues, office 365 health, office 365 performance, fixing office 365, Use cases