On Dec 31 Azure AD will no longer accept communications from DirSync and Azure AD Sync

aad

DirSync & Azure AD Sync refused by Azure AD per December 31st. Upgrade to Azure AD Connect NOW!

Azure AD Connect is the best way to connect your on-premises directory with Azure AD and Office 365. The time to upgrade to Azure AD Connect from Windows Azure Active Directory Sync (DirSync) or Azure AD Sync has come! As these tools are now deprecated and will reach end of life on December 31, 2017.

The two identity synchronization tools that are deprecated were offered for single forest customers (DirSync) and for multi-forest and other advanced customers (Azure AD Sync). These older tools have been replaced with a single solution that is available for all scenarios: Azure AD Connect. To be able to continue to synchronize your on-premises identity data to Azure AD and Office 365, you must upgrade to Azure AD Connect.

The last release of DirSync was released in July 2014 and the last release of Azure AD Sync was released in May 2015.

What is Azure AD Connect

Azure AD Connect is the successor to DirSync and Azure AD Sync. It combines all scenarios these two supported. You can read more about it in Integrating your on-premises identities with Azure Active Directory.

Deprecation schedule

Date Comment
April 13, 2016 Windows Azure Active Directory Sync (“DirSync”) and Microsoft Azure Active Directory Sync (“Azure AD Sync”) are announced as deprecated.
April 13, 2017 Support ends. Customers will no longer be able to open a support case without upgrading to Azure AD Connect first.
December 31, 2017 Azure AD will no longer accept communications from Windows Azure Active Directory Sync (“DirSync”) and Microsoft Azure Active Directory Sync (“Azure AD Sync”).Azure AD will no longer accept communications from Windows Azure Active Directory Sync (“DirSync”) and Microsoft Azure Active Directory Sync (“Azure AD Sync”

How to transition to Azure AD Connect

If you are running DirSync, there are two ways you can upgrade: In-place upgrade and parallel deployment. An in-place upgrade is recommended for most customers and if you have a recent operating system and less than 50,000 objects. In other cases, it is recommended to do a parallel deployment where your DirSync configuration is moved to a new server running Azure AD Connect.

If you use Azure AD Sync, then an in-place upgrade is recommended. If you want to, it is possible to install a new Azure AD Connect server in parallel and do a swing migration from your Azure AD Sync server to Azure AD Connect.

Solution Scenario
Upgrade from DirSync
  • If you have an existing DirSync server already running.
Upgrade from Azure AD Sync
  • If you are moving from Azure AD Sync.

 

Source: Microsoft Azure

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s