Troubleshooting Azure DevOps repository errors

This guide lists and explains some common error messages that you may encounter when connecting an Azure DevOps repository to your project. Where applicable, it also explains how to resolve the underlying issue. After following the steps to resolve an issue, if the error persists, raise a Support ticket. For more information about Support tickets, read Getting support. If you encounter an error that you think we should add to this guide, contact our Support team to let us know.

---

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, 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.

---

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
• Azure DevOps status page
• Matillion status page

---

Requests blocked by an IP allowlist

If your Microsoft Entra Conditional Access policies only allow certain IP addresses and don’t include the Maia IP addresses, Azure DevOps can block Maia. Azure DevOps applies these IP checks to the requests that Maia makes when your Azure DevOps organization has the Enable IP Conditional Access policy validation on non-interactive flows policy turned on. Maia then can’t list your repositories, connect a repository, or perform Git actions that interact with the remote repository, such as Pull remote changes. To resolve this issue, ask your Microsoft Entra administrator to add the Maia IP addresses for Git repositories for your region to a named location that your Conditional Access policies allow. For more information, read Conditional Access policies on Azure DevOps in the Microsoft documentation.

---

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.

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, 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.
   Clicking Revoke sessions will revoke all of your Azure sessions and will require you to sign back in from all devices.