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

# Troubleshooting guide for connecting an Azure DevOps repository to Maia

export const m_runner = "Maia runner";

export const maia = "Maia";

export const designer = "Designer";

This page is a list of troubleshooting guidance in the event that you experience issues when connecting your Azure DevOps repository to a {maia} project. Each scenario includes both an issue and a solution.

For basic connectivity issues, make sure the [Hybrid SaaS {m_runner}s and Git repositories IP addresses](/docs/security/network-access-and-ip-allowlist-requirements#hybrid-saas-agents-and-git-repositories) are allowed on your repository.

***

## App installation fails

### Possible cause 1: There are no Azure DevOps organizations connected to the chosen Azure tenant

Solution: If you have not used Azure DevOps before, first log in to the [Azure Portal](https://portal.azure.com), and search for `Azure DevOps organizations`. From this landing page, choose `My Azure DevOps organizations`, which will take you to the Azure DevOps portal. You will be prompted to create your first DevOps organization, along with a project to organize your resources, including a new repository.

Once created, retry the app installation through the {designer} Project setup process.

### Possible cause 2: You don't have sufficient permissions to install applications to your Azure tenant

Solution: Reach out to one of your Azure administrators to either:

* Grant your user account sufficient permissions to install applications within your tenant.
* Request an admin to install the application into your tenant.

### Possible cause 3: You can't sign in here with a personal account. Use your work or school account instead

Solution: It's not possible to use a personal email address (such as those from Skype, Hotmail, or Outlook) to install {maia} for Azure DevOps due to restrictions on Enterprise applications within Azure. You will need to sign in with a work or school account that is an existing entity within Microsoft Entra ID. This account doesn't have to match the email address you used to register with {maia}, but it must still meet the specified requirement. For more information about the different account/identity types, read [Identity and account types for single and multitenant apps](https://learn.microsoft.com/en-us/security/zero-trust/develop/identity-supported-account-types).

***

## Authorization fails

### Possible cause: Maia can't reach Azure

Solution: If you receive an authorization error, refresh the page and try again. If the issue persists, either Azure or {maia} may be experiencing an issue.

* [Azure status page](https://azure.status.microsoft)
* [Azure DevOps status page](https://status.dev.azure.com/)
* [Matillion status page](https://status.matillion.com/)

***

## How to authenticate using a different Azure DevOps user login

Solution 1: Reauthorize with Azure DevOps from {maia}:

1. Follow the instructions in [Reconnecting your Git user account](/docs/guides/reconnecting-git-user-account).

Solution 2: Revoke {maia} app user access to Azure DevOps. To do this, follow these steps:

1. Go to your user profile in the [Azure Portal](https://azure.microsoft.com/en-gb/get-started/azure-portal), then click **Revoke sessions**.
   1. Revoking access can sometimes take up to 60 minutes.
2. Once access is revoked, make sure you're logged in with the correct Azure DevOps user.
3. Go to {maia} and trigger a Git remote action such as **Pull remote changes**. This will prompt you to reauthenticate using your other Azure DevOps user.

   <Note>
     Clicking **Revoke sessions** will revoke all of your Azure sessions and will require you to sign back in from all devices.
   </Note>

***

## Related pages

* [Prerequisites](/docs/guides/connect-azure-devops-repository-prerequisites)
* [Installing the {maia} app in Azure](/docs/guides/installing-matillion-app-azure-devops)