Luckily, Azure AD Connect Health will send you notifications when running an unsupported version of Azure AD Connect, right? Running an unsupported Azure AD Connect version, means staying on that unsupported version, until you perform a swing migration to a new Azure AD Connect version following the steps in our release management process for Azure AD Connect. This means that on unsupported platforms and for no longer supported Azure AD Connect versions, enabling Automatic Upgrades to remedy the situation is not part of the solution you’re in an unsupported configuration. The big take-away of Automatic Upgrades is that they only work for supported configurations. Running Azure AD Connect with a Microsoft SQL Server (cluster) back-end is probably the biggest blocker at this moment for many organizations. Many configurations have been enabled for automatic upgrades in recent versions of Azure AD Connect, although a couple of configuration scenarios are not supported. Automatic Upgrades for Azure AD Connect are only supported in supported configurations. When talking about the support experience, I feel it’s also important to talk about the Automatic Upgrades feature in Azure AD Connect. Within Microsoft this might lead to a situation where the product team loses resourced, because with low adoption perhaps it’s not something that organizations need… With a lot of supported versions, a product team is bogged down and resources cannot be spent towards new versions and quality control. Obviously having to maintain a lot of versions of Azure AD Connect takes time. The optimal support experience means that Microsoft can reproduce an error or vulnerability you or your organization may experience and provide an answer, workaround, mitigation or a solution. It needs to happen to allow the team to focus on a handful of releases, instead of the nearly forty releases that have been released in the meantime. Two and a half years ago, Microsoft deprecated old versions of Azure AD Connect, Azure AD Sync and DirSync. Please refer to this article to learn more about how to upgrade Azure AD Connect to the latest version. If you have enabled Azure AD Connect for sync you will soon automatically begin receiving Health notifications that warn you about upcoming deprecations when you are running one of the older versions. If you run a deprecated version of Azure AD Connect you may not have the latest security fixes, performance improvements, troubleshooting and diagnostic tools and service enhancements, and if you require support we may not be able to provide you with the level of service your organization needs. You need to make sure you are running a recent version of Azure AD Connect to receive an optimal support experience. At that time we will begin this process by deprecating all releases of Azure AD Connect with version 1.3.20.0 (which was released on ) and older, and we will proceed to evaluate the deprecation of older versions of Azure AD Connect every time a new version releases. Starting on November 1st, 2020, we will begin implementing a deprecation process whereby versions of Azure AD Connect that were released more than 18 months ago will be deprecated. This, week, the Azure AD Connect team made the following announcement on the Azure AD Connect: Version release history page:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |