ThinkReview now supports Azure DevOps Server (on-premise)

[mshenawy22]

ThinkReview now supports Azure DevOps Server (on-premise)

We're happy to announce that ThinkReview now works with Azure DevOps Server on-premise (custom domains). If your organization runs Azure DevOps Server (formerly TFS) on your own infrastructure, you can use the same AI-powered code reviews directly in your pull requests.

Supported versions: Azure DevOps Server 7.1 and above, including:

• Azure DevOps Server 2022 Update 1 (API 7.1)
• Azure DevOps Server 2022 Update 2 (API 7.2)
• Newer releases (e.g. Azure DevOps Server December 2025 RTW and later) that support the same REST API (7.1+).

What this means for you

• Custom domains — Use your own URL (e.g. https://devops.yourcompany.com/DefaultCollection) instead of dev.azure.com.
• Same experience — The same AI Review button, review panel, and features you get with Azure DevOps Services (cloud).
• One-time setup — Configure your collection URL and a Personal Access Token in the ThinkReview extension; no extra services to run.

How it works

1. Create a Personal Access Token in your Azure DevOps Server with Code (Read) permission.
2. Open ThinkReview → Settings and enter your Azure DevOps Collection URL (e.g. http://devops.thinkode.co.uk/DefaultCollection).
3. Restart your browser so the extension can attach to your on-premise host.
4. Open any Pull Request and use the AI Review button on the bottom right.

The AI will analyze the diff and provide suggestions, security checks, and best practices in the same way as with cloud Azure DevOps.

Full setup guide

Step-by-step instructions (including screenshots) are in the docs:

Azure DevOps On-Premise setup guide

Troubleshooting

• AI Review button not showing — Do a full browser restart (not just a refresh).
• Auth errors — Confirm your PAT has Code (Read) and the token is valid.
• Wrong or missing repos — Double-check the collection URL and that it includes the collection name (e.g. /DefaultCollection).

If you hit any issues or have feedback, open an issue or reply in Discussions—we’d love to hear from teams using on-premise Azure DevOps.