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

# Azure DevOps Setup

> Connect Azure DevOps through the current OAuth flow, complete any follow-up confirmation, and verify repository access before enabling repository features.

# Azure DevOps Setup

Azure DevOps follows the same general pattern as the other Git providers, but you should expect a
provider-specific follow-up confirmation after the initial redirect.

## In The UI

1. Go to `Settings` -> `Integrations` -> `Git`
2. Choose **Connect Azure DevOps**
3. Complete the OAuth redirect
4. Finish any follow-up selection or confirmation step the integration requires
5. Verify the repository list from the integration detail page

## Guest Users (B2B) In Another Directory

If your Azure DevOps organization belongs to a Microsoft Entra directory where you are a **guest
user**, the default sign-in lands in your home directory and the connection fails with
"No Azure DevOps organizations found for user". In that case, open the Azure DevOps start page
(choose **Start Over** after a failed attempt) and fill in the optional
**Microsoft Entra directory (tenant)** field with the tenant ID or a verified domain of the
directory that owns your DevOps organization before connecting.

## What To Verify

Before you rely on the integration:

* The integration is active
* Repositories are visible where you expect them
* Repository settings open successfully
* Review features can be enabled at the repository level if you need them

## Next

<CardGroup cols={2}>
  <Card title="Connect Git" icon="code-branch" href="/getting-started/connect-git-provider">
    Return to the shared Git setup guidance.
  </Card>

  <Card title="PR Reviews" icon="git-alt" href="/features/pull-request-reviews">
    Enable reviews only after the repository list is stable.
  </Card>
</CardGroup>