Skip to content

Azure DevOps Integration

Connect your Azure DevOps repositories to Capawesome Cloud to streamline your workflow for Live Updates and Native Builds. This integration allows Capawesome Cloud to access your source code and automate deployments directly from your Azure DevOps repository.

Prerequisites

Before you begin, ensure you have:

  • A Capawesome Cloud account with an app created.
  • A Microsoft account with access to Azure DevOps and the repository you want to connect.
  • Admin or owner permissions for the Azure DevOps repository.

Connect your repository

Follow these steps to connect your Azure DevOps account to Capawesome Cloud:

  1. Navigate to the Git page in the Capawesome Cloud Console.
  2. Click on the Azure DevOps tab in the Git Providers section.
  3. Click the Connect button in the Azure DevOps section and authorize Capawesome Cloud to access your Microsoft account. Review the permissions requested and click Authorize to grant access.
  4. After authorization, you will be redirected back to the Capawesome Cloud Console. In the Git Repositories section, select Azure DevOps as your Git provider, choose an organization and project, and select the repository you want to connect to Capawesome Cloud.
  5. Click the Save button to finalize the integration.

Your Azure DevOps repository is now connected to Capawesome Cloud.

Troubleshooting

Connection issues

If you encounter issues while connecting your Azure DevOps account, consider the following common problems:

  • Account type: Only Business or School Microsoft accounts are supported. Personal accounts (e.g., @gmail.com) cannot be used.
  • Custom domains: Custom domains must be verified in Microsoft Entra.
  • Organization connection: Your Azure DevOps organization must be connected to your Microsoft Entra tenant (Organization Settings → Microsoft Entra → Connect).

Missing organizations

If an Azure DevOps organization (Git owner) does not appear in the selection dropdown, one of the following is usually the cause:

  • Mismatched Microsoft Entra tenant: Each organization is tied to a specific Microsoft Entra ID tenant. Sign in with an account from the organization's home tenant, or attach the organization to your default directory.
  • No direct membership: Only organizations where you are a direct member are listed. Guest/external invitations, group-based access, or "Stakeholder"-only access can hide an organization.
  • Disabled or removed user: If your user has been deactivated or removed from the organization, it will not appear.
  • Limited OAuth scopes: If the original authorization granted only a subset of the required scopes, disconnect and reconnect your Azure DevOps account to re-authorize.
  • Organization not linked to your Microsoft profile: Some legacy organizations backed by a Microsoft account (MSA) may not be associated with your profile. Visit https://aex.dev.azure.com to confirm the list of organizations visible to your account.