The 801800A issue is usually caused by a Windows client thinking it has a enrollment to Azure AD in progress. It will not “time out” so you will have to manually fix this…
Depending upon the version of the sync solution that you are using to replicate directory data from on-premises Active Directory to Office 365 there are different commands that you will need to use.
While doing a regular maintenance check on my customers servers when I came across a new event in the log.
I’ve previously wrote about changing the sync schedule on this server.
But today I noticed two event errors, ADSync event 6127 and 6127.
I finally I got some time to play with the new Azure Active Directory Sync tool and its configuration.
The installation was very straight forward. The step-by-step instruction are provided on MSDN. The administration tools and scripts are located in difference places compared to DirSync which was little confusing in the beginning.
By default DirSync runs every three hours; which for some environments or during testing may not be frequent enough…
You can install the Azure module directly from the PowerShell prompt and connect to the numerous services offered by Microsofts extensive cloud solution!