Upcoming changes to Azure DevOps authentication
Starting March 3, 2025, Microsoft will no longer accept new registrations for Azure DevOps OAuth apps, as part of their plan to sunset the platform by 2026.
Existing integrations with Azure DevOps will continue to function normally until the end-of-life date, and new customers will still be able to authenticate and use Azure DevOps with Gearset for the time being.
We are actively planning to transition to the Microsoft Identity (Entra) platform to ensure continued compatibility. If you have any questions or concerns, please reach out to our team.
Connecting to your source control repository with Gearset allows you to deploy to and from your source of truth. This article shows you how simple it is to connect to your cloud-based repo on https://dev.azure.com/.
Once you're logged into Gearset, head to the Source control and services section and click on the Connect to Azure DevOps link.
This will take you to Azure DevOps's OAuth page for authentication.
Once complete, it should look like this (with your authenticated Azure DevOps username being visible):
Additionally: within your Azure DevOps "User settings: Authorizations" page, you will find an authorized app for Gearset. You have the ability to revoke the application at any time from this page. Depending on the security settings of your organization, an admin of your org will need to grant approval for this app upon initial connection:
Having trouble finding your repositories, after connecting to Azure DevOps?
You may have multiple Azure DevOps tenants, see here for more details.