This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(275.2, 54%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAR%3C/text%3E%3C/svg%3E)
I recently performed an in place upgrade from Server 2016 to Server 2022, and after the upgrade was completed, Azure AD Sync no longer seems to function. I am running the most recent version of Azure AD Connect (2.2.1.0) and I have already attempted uninstalling and reinstalling Azure AD Connect with no success. The installation goes fine and by everything I can see on the local server the sync is performed and is successful, however in the Azure Health Portal there are no completed syncs since the upgrade. There are also no sync errors shown other than the sync has not been completed in over 24 hours.
Any help is greatly appreciated.
A cloud-based identity and access management service for securing user authentication and resource access
so AADConnect shows a successful export to Azure and the Azure objects are being added/updated etc?
That is correct, I get success messages for the Export, Delta Synchronization, and Delta Import and I can even see that the scheduling is working as it should.
I wonder if you just need to remove and re-add the health agent? Ensure the Azure health service is running on the server itself as well.
No luck there, removed the Azure Health service and re-installed, installation completed without any errors, the Azure Health service has been confirmed as running, but the error persists on the Azure Health Portal. There is now also an error saying the Password Hash synchronization heartbeat was skipped in the last 120 minutes as well.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi @Anthony Rico , did you need any more help with this question? If not could you please mark "Accept Answer" on the appropriate answer so other users can reference it?
Thank you,
James
I would note that in place upgrades of the Windows O/S are supported with AADConnect:
Hi @Anthony Rico , It's recommended not to perform an in-place upgrade of the OS for your Azure AD Connect server. Instead, you should prepare a new server with the desired operating system and perform a swing migration. Since you have already performed an in-place upgrade, you can try the following steps:
If the issue persists, you may need to consider setting up a new server with the desired operating system and perform a swing migration as recommended in the documentation.
We can also open a free support ticket for you to save you some pain. Please let me know and I can help you further.
If this answer helps you please mark "Accept Answer" so other users can reference it.
Thank you,
James
I wanted to check in and see if you had any other questions or if you were able to resolve this issue?
If you have any other questions, please let me know. Thank you for your time and patience throughout this issue.
If the information helped address your question, please Accept the answer. This will help us and also improve searchability for others in the community who might be researching similar information.
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
