End of Support for Microsoft products reliant on older Azure DevOps authentication

Angel Wong

Azure DevOps will no longer guarantee support for older authentication methods in use by out-of-support Visual Studio and Microsoft products. Known impacted clients include:

  1. Visual Studio 2010 (end of support: July 14, 2020)
  2. Visual Studio 2012 (end of support: January 10, 2023)
  3. Visual Studio 2013 (end of support: April 9, 2024)
  4. Dynamics AX 2009 (end of support: April 12, 2022)
  5. Dynamics AX 2012 (end of support: April 12, 2022)
  6. Dynamics AX 2012 R2 (end of support: April 12, 2022)
  7. Dynamics AX 2012 R3 (end of support: January 10, 2023)
  8. Team Foundation Server 2008 (out of support)
  9. Team Foundation Server 2010 (end of support: July 14, 2020)
  10. Team Foundation Server 2012 (end of support: January 10, 2023)

This may not be a comprehensive list of impacted products, but only affected products are expected to be out of support already per Microsoft’s product end of support policies.

We are making these changes to end the usage of less secure authentication mechanisms in favor of more secure and actively supported authentication available in newer versions of these products. Such changes will also allow our teams to focus on delivering the newest in authentication and security features, instead of allocating resources to maintain out-of-date authentication paradigms.

We recommend all customers to fully migrate from these older clients to newer versions by December 31, 2024. All listed products have newer versions that are actively in support. While these listed products may continue to work, we do not intend on continuing to support any functionality in those products reliant on older Azure DevOps authentication by March 2025.


Leave a comment

  • Ben Reisner 1

    Is Microsoft planning to release any actively supported Source Control for Microsoft Access to mitigate this change?

    The last supported Source Control Environment from Microsoft for Access is a plugin for Access 2010 that relies on Visual Studio 2012. It works fine with DevOps right now. If Microsoft actively breaks VS 2012’s ability to authenticate against DevOps it would leave anybody stuck with an Access project without a viable Source Control Solution from Microsoft.

  • Tobias Schön 0

    These 2010 and 2013 TFS installations.
    There’s no where to get the installation medias. This makes it extremely hard to actually migrate them.

    I have been looking and not been able to get hold on these installationmedias sadly. Especially when some requires a stop to go to a version of the newest ones. Are able to explain how we are supposed to get the installationmedias in our hands?

Feedback usabilla icon