"As part of our ongoing commitment to security and modernization, we're updating outdated authentication mechanisms used by older versions of clients reliant on our older Visual Studio client libraries. For full details on all known impacted clients, refer to the official announcement we made in April 2024: End of Support for Microsoft products reliant on older Azure DevOps and Visual Studio authentication."
"In order to minimize disruption due to removing these legacy tokens, over the past few months, we've worked on seamlessly transitioning these legacy tokens to Entra-backed authentication when possible. This change enhances security and aligns with current identity standards-but it may also result in more frequent interactive reauthentication prompts, due to the 1-hour lifetime of Entra tokens. If you're still experiencing authentication issues, we strongly recommend upgrading to a supported version of your client or tool that relies on the legacy tokens."
Outdated authentication mechanisms used by older Visual Studio client libraries are being updated to Entra-backed authentication to enhance security and align with current identity standards. The transition has targeted seamless conversion of legacy tokens where possible to minimize disruption. Entra tokens have a one-hour lifetime, which can increase the frequency of interactive reauthentication prompts. Users who continue to experience authentication issues should upgrade to supported client or tool versions. Many older products are past end-of-support and cannot maintain compatibility with deprecated in-product authentication flows. Upgrading delivers additional security and product improvements.
Read at Azure DevOps Blog
Unable to calculate read time
Collection
[
|
...
]