> ## Documentation Index
> Fetch the complete documentation index at: https://docs.codeant.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Control Center

> Connect your Azure DevOps Services organization and verify that its repositories appear in CodeAnt AI.

> [!NOTE]
>
> This guide uses a personal access token. For a connection without a PAT, follow the [Microsoft Entra workload identity guide](https://docs.codeant.ai/setup/azure_devops/cloud/entra_workload_identity.md). For Azure DevOps Server, use the [self-hosted connection guide](https://docs.codeant.ai/setup/azure_devops/self-hosted/control_center.md).

## Before you begin

* A company email address you can use to sign in to CodeAnt AI and receive a verification code. Public email addresses such as Gmail or Yahoo are not supported by this sign-in flow.
* An Azure DevOps Services account with access to the projects and repositories you want to analyze.
* Permission to create a PAT under your organization's policy.
* The organization name from your repository URL.

## Connect your organization

**1. Sign in to CodeAnt AI**

Open the [CodeAnt AI dashboard](https://app.codeant.ai). Choose Azure DevOps to sign in.

Enter your company email address, then enter the verification code sent to your inbox.

**2. Create a personal access token**

In Azure DevOps Services, open **User settings** → **Personal access tokens** and select **+ New Token**.

Name the token `CodeAnt AI`, select the intended organization or collection, and choose an expiry date permitted by your organization's policy. Select the scopes for the features you plan to use:

| Scope | Access | Used for |
| - | - | - |
| Code | Read & write | Repository access and analysis |
| Pull Request Threads | Read & write | Review comments and threads |
| Build | Read | DORA metrics |
| Work Items | Read & write | Metrics and ticket creation |

**Code** and **Pull Request Threads** are the scopes for scans and reviews. Add **Build** for DORA metrics and **Work Items** for work item data and Azure DevOps ticket creation.

Select **Create** and copy the token before closing the page. See [Microsoft's PAT guide](https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate?view=azure-devops) for token creation requirements.

**3. Enter your connection details**

Use the following values for a repository such as `https://dev.azure.com/my-organization/my-project/_git/my-repository`:

| Field | Value |
| - | - |
| Base URL | `https://dev.azure.com` |
| Organization name | `my-organization` |
| Access token | The PAT you just created |

If your repository uses the legacy URL `https://my-organization.visualstudio.com/my-project/_git/my-repository`, still use `https://dev.azure.com` as the base URL and `my-organization` as the organization name. For this URL format, the organization name is the subdomain, not the project path.

![CodeAnt connection form with Azure DevOps base URL, organization name, and access token fields](https://mintcdn.com/codeantai/cPAPWnajTUNzakyT/images/setup/azure-devops/cloud/control_center/creds.png?fit=max\&auto=format\&n=cPAPWnajTUNzakyT\&q=85\&s=5883c2aa8ccc777a6259bcd94b442aeb)

**4. Save the connection**

Review the values and select **Submit**. CodeAnt fetches the projects and repositories available to the token's account.

## Verify repository access

Confirm that a repository you expect appears in CodeAnt AI. If it is missing, check the token account's access to that project and repository before configuring analysis.

Use [repository analysis configuration](https://docs.codeant.ai/repositories/analysis_configuration.md) to choose the scans and files to include.

For automatic PR reviews, complete the [service hook setup](https://docs.codeant.ai/setup/azure_devops/cloud/pull_request.md). Connecting repositories to the dashboard does not replace that setup.

## Troubleshooting

> [accordion] I have not received my sign-in code
>
> Confirm that you entered your company email correctly. Check your spam, junk, and quarantine folders. If the code is still missing, ask your email administrator to check delivery or [contact CodeAnt support](mailto:support@codeant.ai).

> [accordion] The connection fails when I submit the form
>
> Compare the base URL and organization name with the examples above. Confirm that the PAT has not expired or been revoked and belongs to an account with access to the intended projects. Use `https://dev.azure.com` even for legacy `visualstudio.com` URLs.

> [accordion] My repository is missing
>
> Check that the PAT covers the intended organization or collection and that its owner has repository access. A PAT cannot grant more access than its owner has. If the repository remains missing, [contact CodeAnt support](mailto:support@codeant.ai) with the organization, project, and repository name. Do not include the PAT.

> [accordion] Repositories appear, but pull requests are not reviewed
>
> Complete the [pull request review setup](https://docs.codeant.ai/setup/azure_devops/cloud/pull_request.md) for the project, including both service hook subscriptions. Then open a new PR or post `@codeant-ai: review` on an existing PR.

## Next steps

> [card] [Enable pull request reviews](https://docs.codeant.ai/setup/azure_devops/cloud/pull_request.md)
>
> Configure service hooks and verify your first review.

> [card] [Configure repository scans](https://docs.codeant.ai/repositories/analysis_configuration.md)
>
> Choose which analyses run and which files they include.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.