POST /oauth2/token → endpoint removal
Deprecated, no date
The POST /oauth2/token endpoint is deprecated and scheduled for removal in 2026 without a specific shutdown date. Calls hitting this endpoint will eventually fail once it is removed. This affects existing Azure DevOps OAuth applications using the legacy authentication flow.
Calls it hits
POST /oauth2/token
What to use instead of these calls
Register an application in Microsoft Entra ID and request tokens from login.microsoftonline.com/{tenant}/oauth2/v2.0/token using the Azure DevOps scope 499b84ac-1321-427f-aa17-267ca6975798/.default. Moving requires a new app registration in a Microsoft Entra tenant rather than just changing an endpoint, and it does not work with personal Microsoft accounts.
Moving to Microsoft Entra ID OAuth needs a new app registration in a Microsoft Entra tenant; it does not work with personal Microsoft accounts.
In app.vssps.visualstudio.com's words
Azure DevOps OAuth is deprecated and scheduled for removal in 2026. This documentation is for existing Azure DevOps OAuth apps only.
Facts
- API
- app.vssps.visualstudio.com
app.vssps.visualstudio.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against app.vssps.visualstudio.com's own pages
Questions
When does this change take effect?
app.vssps.visualstudio.com deprecated POST /oauth2/token without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: app.vssps.visualstudio.com has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from app.vssps.visualstudio.com 1
-
No date
GET /oauth2/authorizeEndpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.