Still Running DirSync and AAD Sync–Really Time To Update

This post is for those customers who continue to run outdated and legacy versions of the synchronisation tools to connect on-premises Active Directory to Azure Active Directory.  It was noted back in April this year that legacy versions of the synchronisation tools should be updated to a supported version of Azure AD Connect.  Preferably the latest available version.

If for any reason this was not done, the time to act is now!  Microsoft does not guarantee these older versions to work after December 31st, 2017.  Customers must be on a supported version of Azure AD Connect.   From Upgrade Windows Azure Active Directory Sync and Azure Active Directory Sync:

DirSync and Azure AD Sync Depreciation Schedule

The replacement for the older synchronisation tools is Azure Active Directory Connect 1.1.  Customers must have this version of AAD Connect deployed. This is the tool which is being actively maintained, and receives updates and fixes.

Azure AD will no longer accept communications from the unsupported tools as of December 31st 2017.

If you do need to upgrade, the relevant documentation is below:

Upgrade from DirSync

Upgrade from Azure AD Sync

This change was announced previously in the Office 365 message centre in April 2016, via MC45036, we will be removing the Windows Azure Active Directory Synchronization feature from Office 365, beginning April 13, 2017. Azure Active Directory (AD) Connect is the best way to connect your on-premises directory with Azure AD and Office 365. Azure AD Connect is replacing DirSync and Azure AD Sync and these two older sync engines were deprecated from April 13, 2016, reaching end of support April 13, 2017. You are receiving this message because you are using DirSync, Azure AD Sync, or an Azure AD Connect installation released before 2016. After April 13, 2017, you will no longer be able to open a support case without first upgrading to Azure AD Connect



Rhoderick Milne [MSFT]

Leave a Reply

Your email address will not be published. Required fields are marked *