
Azure AD Connect is a critical tool for syncing identities between your on-premises Active Directory and Azure Active Directory. It's been around since 2014.
The first version of Azure AD Connect was released in November 2014, marking the beginning of a new era in identity management.
Since then, there have been several updates and releases, with the latest version being Azure AD Connect Health. This feature allows for real-time monitoring and troubleshooting of Azure AD Connect.
Azure AD Connect Health was released in April 2020, providing a more streamlined and efficient experience for administrators.
Take a look at this: Azure Ad Directory Roles
Azure AD Connect Version History
Azure AD Connect has undergone significant changes and updates over the years. As of August 31, 2022, all 1.x versions of Azure AD Connect will be retired due to the lack of support for SQL Server 2012 components and Azure AD Authentication Library (ADAL) components.
You should prioritize updating to the most recent 2.x versions of the software or to the newer Azure AD Connect cloud sync. If you're running any 1.x versions in production environments, it's high time to start planning your migration.
You might enjoy: Azure Aks Versions
Azure AD Sync requires the .Net framework version 4.5.1 to be installed, starting from its release in 2015 April.
Here's a brief overview of the major releases of Azure AD Connect:
Note the significant updates made to Azure AD Connect, including the release of new versions and the retirement of older ones.
Azure AD Connect has been released for download on several occasions. Here are the notable release dates:
These release dates indicate the frequency and regularity of updates to Azure AD Connect.
Version Numbers
As of August 31, 2022, all 1.x versions of Azure AD Connect will be retired due to outdated SQL Server 2012 components and Azure AD Authentication Library (ADAL) components.
Here's a quick rundown of the retirement dates for 1.x versions: August 31, 2022.
If you're running a 1.x version, especially in production environments, it's time to start planning your migration to the latest 2.x versions of Azure AD Connect.
For Microsoft Entra Connect 2.x versions, retirement occurs 12 months after a newer version is released.
Here's a list of some 2.x versions and their retirement dates:
2.x Versions

All 1.x versions of Azure AD Connect will be retired by August 31, 2022, due to outdated SQL Server 2012 components and Azure AD Authentication Library (ADAL) components.
These versions include SQL Server 2012 components and Azure AD Authentication Library (ADAL) components, which will no longer be supported as of August 31, 2022.
The 2.x versions of Azure AD Connect sync will be retired 12 months after their release, starting from March 15, 2023. Here are the specific versions that will be retired:
- 2.0.89.0
- 2.0.88.0
- 2.0.28.0
- 2.0.25.1
- 2.0.10.0
- 2.0.9.0
- 2.0.8.0
- 2.0.3.0
Microsoft Entra Connect 2.x versions will also be retired 12 months after the release of a newer version. For example, version 2.2.1.0 will be retired on October 11, 2024, and version 2.3.2.0 will be retired on February 21, 2025.
How Automatic Upgrades Work
Automatic upgrades work by regularly checking for newer versions of Azure AD Connect, but not all releases are made available for auto-upgrade. Only more tested, validated, and approved versions are released.
If your server is enabled for automatic upgrade, the software will update itself with no intervention from you. Nice!
Critical security fix versions are certainly released for auto-upgrade, ensuring your system stays secure.
You might like: Latest Version of Azure Ad Connect
Features and Changes
Azure AD Connect has seen its fair share of updates, and one of the most notable changes is the updated SQL related drivers. These drivers have been updated to OLE DB version 18.7.4, which should improve overall performance.
We've also seen some important bug fixes in the latest versions of Azure AD Connect. Issues like admins being unable to enable seamless single sign-on due to an existing AZUREADSSOACC computer account in Active Directory have been resolved.
Here are some of the key fixes:
- We fixed an issue where admin can't enable seamless single sign-on if the AZUREADSSOACC computer account is already present in Active Directory.
- We fixed an issue that caused a staging error during V2 API delta import for a conflicting object that was repaired via the Health portal.
- We fixed an issue in the import/export configuration where a disabled custom rule was imported as enabled.
Updated Features
The SQL related drivers shipped with Microsoft Entra Connect have been updated to OLE DB version 18.7.4.
This update brings several improvements to the database management system, making it more efficient and reliable.
Here are the details of the update:
- SQL related drivers have been updated to OLE DB version 18.7.4
The update was released on April 1, 2024, and is available for download.
Features and Changes
Microsoft Entra Connect has been updated with various bug fixes and improvements.
A notable fix addressed an issue with Privileged Identity Management (PIM), Microsoft Entra roles, and PIM for Groups to verify that PIM is enabled and that the user has the Hybrid Identity Administrator role enabled.

The update also fixed an issue where AD FS commands were failing when Connect Sync is installed on a non-ADFS server.
Microsoft Entra Connect Health has been updated to 4.5.2466.0 to address an endpoint discovery issue that could occur in some clouds.
Several issues were fixed in a recent update, including one where admin couldn't enable seamless single sign-on if the AZUREADSSOACC computer account is already present in Active Directory.
Another issue was fixed where a staging error occurred during V2 API delta import for a conflicting object that was repaired via the Health portal.
A bug was also fixed where a disabled custom rule was imported as enabled.
The update also fixed a bug where there would be a false warning about the local DB size on the localized builds during upgrade.
Another bug was fixed where there would be a false error in the app events for the account name/domain name swap.
An error was fixed where Microsoft Entra Connect would fail to install on a DC, giving error "member not found".
Here are the release dates for Microsoft Entra Connect:
Deprecated Features

Deprecated Features are no longer available in the Synchronization Service Manager.
The feature that used to validate object against schema has been deprecated and is no longer available in the Synchronization Service Manager.
The "enableldap" Command Line (Preview) feature has been deprecated and is no longer available when you run the Wizard.
These changes may require you to adjust your workflow to accommodate the new restrictions.
Broaden your view: Azure Ad Connect Sync Service Not Running
Functional Changes
The Functional Changes section of the Microsoft Entra ID features and updates is a significant part of the latest release.
The mS-DS-ConsistencyGuid feature has been added for group objects, allowing you to move groups between forests or reconnect groups in AD to Microsoft Entra ID where the AD group objectID has changed.
This feature is automatically enabled for all synced groups, so you don't need to do anything to enable it. The mS-DS-ConsistencyGuid attribute is automatically set on all synced groups.
The Get-ADSyncRunProfile cmdlet has been removed because it's no longer in use.
Take a look at this: Azure Ad Groups

The warning message when using an Enterprise Admin or Domain Admin account for the AD DS connector account has been updated to provide more context.
The old CSDelete.exe tool has been replaced with the new Remove-ADSyncCSObject cmdlet. This new cmdlet takes a CsObject as input, which can be retrieved using the Get-ADSyncCSObject cmdlet.
Here are the key changes related to the CSDelete.exe tool:
- The old CSDelete.exe tool has been removed.
- The new Remove-ADSyncCSObject cmdlet has been introduced.
Release Information
Azure AD Connect has a long history of updates and improvements. The first release was in April 2015.
Azure AD Sync, a precursor to Azure AD Connect, was initially released in April 2015. It required the .Net framework version 4.5.1 to be installed.
Azure AD Connect has undergone numerous updates over the years. For instance, a bug fix was released on November 2, 2022, which addressed an issue with the new employeeLeaveDateTime attribute.
Here are some key release dates for Azure AD Connect:
Microsoft Entra
Microsoft Entra has made some significant changes to its features and functionality. Microsoft Entra Connect now synchronizes password hashes, not passwords, which is reflected in the User Sign-in page option being changed to "Password Hash Synchronization".
The Set-ADSyncAutoUpgrade cmdlet has also been updated to no longer block AutoUpgrade of future builds if the auto-upgrade state is set to Suspended. This change is a result of Microsoft Entra's efforts to improve the user experience and make its features more efficient.
This means that users can now take advantage of new features and updates without having to worry about previous settings holding them back.
Non-Functional Microsoft Entra Versions
All Microsoft Entra Connect Sync 1.x versions are unsupported and synchronization does not function.
Customers using cloud sync or supported versions of Microsoft Entra Connect 2.x remain fully operational.
If you're still using an unsupported version, be aware that it might unexpectedly stop working.
You might also not have the latest security fixes, performance improvements, troubleshooting and diagnostic tools, and service enhancements.
The retirement of all 1.x versions is described in the Decommission Azure AD Connect V1 article.
Microsoft Entra Connect 2.x versions retire 12 months from the date that a newer version is released.
You might enjoy: How to Connect to Azure Cosmos Db Using Connection String

This policy went into effect on 15 March 2023.
Here's a list of some retired versions of Microsoft Entra Connect 2.x:
If you require support, Microsoft might not be able to provide the level of service your organization needs if you're running a retired version.
Retiring Microsoft Entra 2.x
Microsoft Entra 2.x versions are being retired, and it's essential to understand the implications and take necessary steps. Microsoft Entra Connect 2.x versions retire 12 months from the date that a newer version is released.
The retirement policy went into effect on March 15, 2023. If you're running a retired version, it might unexpectedly stop working, and you won't have the latest security fixes, performance improvements, troubleshooting and diagnostic tools, or service enhancements.
To avoid these issues, make sure to upgrade to the latest version before the retirement of your current version. For new installs, always install the latest version. The table below shows the end of support dates for various Microsoft Entra Connect 2.x versions:
If you require support, Microsoft might not be able to provide the level of service your organization needs if you're running a retired version.
Authentication
In Azure AD Connect, authentication has undergone some significant changes over the years.
The Microsoft Entra Connect Authentication Agent is now the name of the agent required for Pass-through Authentication.
Enabling Pass-through Authentication no longer automatically enables Password Hash Synchronization by default.
Here are the changes to keep in mind:
- Microsoft Entra Connect Authentication Agent replaced Microsoft Entra private network connector for Pass-through Authentication.
- Password Hash Synchronization is no longer enabled by default when enabling Pass-through Authentication.
Pass-Through Authentication
The name of the agent required for Pass-through Authentication has been changed from Microsoft Entra private network connector to Microsoft Entra Connect Authentication Agent.
Enabling Pass-through Authentication no longer enables Password Hash Synchronization by default. This means you'll need to explicitly configure it if you want to use both features together.
Broaden your view: Azure Auth Json Website Azure Ad Authentication
Seamless Single Sign-On
Seamless single sign-on is a feature that allows users to access multiple applications without having to log in multiple times. This feature is particularly useful for organizations that use multiple applications.
A common issue with seamless single sign-on is that it can return an error if you try to enable it. Specifically, the error message is “Configuration of Microsoft Entra Connect Authentication Agent failed.”
Existing customers who had manually upgraded the preview version of the Authentication Agents for Pass-through Authentication may be affected by this issue.
A unique perspective: Azure Active Directory Authentication
Featured Images: pexels.com


