Skip to main content
Connect your Azure DevOps Server instance to CodeRabbit Cloud to review pull requests in your repositories. Users sign in to CodeRabbit through Enterprise SSO, then link their Azure DevOps Server account with a personal access token (PAT). A separate bot PAT lets CodeRabbit post reviews and comments. Complete Enterprise SSO setup before following this guide. Azure DevOps Server uses PATs for this connection; there is no CodeRabbit OAuth application or callback URL to configure on the server.

​
Before you start

Have the following ready:
  • An Enterprise SSO workspace and a CodeRabbit workspace admin who can register the server.
  • The server’s HTTPS base URL, including its installation path if it has one, such as https://ado.example.com/tfs.
  • The collections, projects, and repositories you want to connect.
  • A dedicated Azure DevOps Server user for CodeRabbit, with access to every collection and repository it will review.
  • A PAT for that bot user and a separate PAT for the person completing setup.
Confirm your Azure DevOps Server version and network requirements with your CodeRabbit account team before onboarding.

​
Network access

CodeRabbit must be able to reach the server for authenticated API requests and Git access. Azure DevOps Server must also be able to deliver service hooks to CodeRabbit. For a direct connection, use a publicly reachable HTTPS server URL. If users access a different address, the registration form accepts an Alternate host URL (optional) for CodeRabbit’s server-to-server requests. Both addresses must route to the same Azure DevOps Server. Preserve an installation path such as /tfs in the alternate address when applicable. If the server is reachable only on a private network, contact CodeRabbit support to arrange private access before registering it. Entering a private address alone does not establish connectivity. Ask your account team for the network requirements for your CodeRabbit region.

​
Prepare the two tokens

In Azure DevOps Server, open User settings > Personal access tokens and create a token while signed in as each account. Choose an expiration date and save each token securely when it is shown. PAT scopes and the account’s permissions both apply. A token does not grant access to a project or repository that its owner cannot access. Keep the bot account separate from the people who open pull requests.

​
Register the server

1

Open Azure DevOps Server onboarding

Sign in to the CodeRabbit application through your organization’s SSO. In your workspace, open Git provider onboarding and select Azure DevOps Server. You can also select this provider during initial workspace onboarding.
2

Enter the server address

Select Add server if the workspace already has a registered server. Enter the Server URL without a collection, project, or repository path. Include the server installation path when applicable.For example, if a collection is at https://ado.example.com/tfs/DefaultCollection, enter https://ado.example.com/tfs.Use HTTPS and omit credentials, query parameters, and URL fragments. If your network setup requires a separate reachable address, enter it in Alternate host URL (optional). Otherwise, leave that field empty.
3

Register the bot account

Paste the dedicated bot user’s PAT into Bot personal access token and select Register server. CodeRabbit verifies the bot identity and saves the server connection.If the server is already listed under Registered servers, select Continue with its URL instead of registering it again.

​
Connect your account and collections

1

Link your own Azure DevOps Server account

Enter your own PAT in Your personal access token and select Connect account. Use your individual account’s token here. It determines which collections, projects, and repositories you can see.
2

Add collections to the workspace

Select the collections you want to add from the onboarding flow or the Add collections dialog in Git provider onboarding. Each collection becomes an organization in your CodeRabbit workspace.Only collections accessible to your linked account are available. Check that the bot account can access the selected collections as well.
3

Connect other team members

Team members sign in through SSO, select the registered server, and connect their own personal PAT. SSO workspace membership does not grant Azure DevOps Server repository access.Configure review seats using the separate workspace seat assignment guide.

​
Install repositories and verify a review

1

Select a collection and project

Switch to the collection’s organization in CodeRabbit and open Repositories. Select the Project containing the repository. Use Load more projects or Load more repositories if needed.
2

Install CodeRabbit

Select Install beside a repository and wait for Installed to appear. Your CodeRabbit role must allow repository management.CodeRabbit checks your personal repository access and the bot account’s repository permissions, then creates and verifies the review service hooks using your personal PAT. The bot token is used to perform reviews.
3

Verify service-hook delivery

In the Azure DevOps Server project’s Service hooks settings, confirm that the CodeRabbit review subscriptions are enabled. Check their delivery history after opening or updating a pull request. Use the subscriptions created by CodeRabbit, which contain the Server-specific callback and authentication settings.
4

Open a test pull request

Use a human account to open a non-draft pull request with a code change against the repository’s default branch. Confirm that CodeRabbit posts a review under the bot account. If your repository has custom review settings, check that automatic reviews are enabled for this pull request.

​
Maintain the connection

Before the bot PAT expires, create a replacement for the same bot account with access to every connected collection. As a workspace admin, open Git credentials, select Azure DevOps Server, find the server, paste the new Bot personal access token, and select Update bot token. Verify a review after rotation; saving the token does not establish that every repository permission or write scope is correct. If your personal PAT expires or your access changes, reconnect your account through Git provider onboarding with a valid personal PAT. Updating the bot token does not update team members’ personal tokens.

​
Troubleshooting

If setup still fails, contact support with the failing step, error message, and time of the attempt. Do not include PATs or service-hook secrets.

​
What’s next

Configure reviews

Customize review behavior with a repository configuration file.

Seat assignment

Choose how workspace members receive review seats.