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. These changes will begin slowly rolling out now until end of year.
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. As a reminder, many of these older products are past end-of-support, so we’re unable to maintain compatibility with deprecated in-product authentication flows. Upgrading your clients to later versions that rely on modern authentication likely comes with additional security and product improvements.
Hi Angel,
I hope you’re well. I’m following up on your posts from October 28, 2024, and April 23, 2025:
- “No new Azure DevOps OAuth apps beginning April 2025” - No New OAuth Apps
- “Spring Cleaning: A CTA for Azure DevOps OAuth Apps with expired or long-living secrets” - Sprint Cleaning Blog Link
These notes indicate that existing OAuth apps will “continue working until the platform’s official retirement in 2026.” However, I was unable to locate a precise date (month/day) for when OAuth support will be disabled or deprecated.
To help us manage our migration safely and...