Install Qodo on Azure DevOps

Documentation Index

Fetch the complete documentation index at: https://docs.qodo.ai/llms.txt

Use this file to discover all available pages before exploring further.

• OAuth app registration (recommended): Best for enterprise environments. Uses Azure AD app registration for automated access.
• Personal access token (PAT): Suitable when Azure AD admin access is unavailable.

​

Prerequisites

• Access to your Qodo portal.
• A Qodo environment configured for Azure DevOps (provided by your Qodo Account Manager).

• OAuth: Azure AD administrator permissions to create app registrations and grant admin consent. Before proceeding, review the requirements and common issues below.
  ⚠ Common issues and detailed requirements

  If you encounter issues, these are common causes:

  • Missing admin permissions: You cannot create or install the app without Project Collection Administrator access.
  • No available licenses: The installation fails if no Basic access licenses are available.
  • Restricted consent policies: Your organization’s Microsoft Azure security policies may block authorization.

  ​

  Required permissions

  To install the app, you must be a Microsoft Entra ID administrator (Cloud Application Administrator or Global Administrator).To complete the setup, you must also be an Azure DevOps organization administrator (Organization Owner or Project Collection Administrator) to add the service principal and grant access to projects, repositories, and webhooks.

  How to assign Microsoft Entra ID roles

  1. Go to the Microsoft Entra admin center.
  2. Navigate to Users, select a user, then open Administrative roles.
  3. Click Add assignments.
  4. Assign Global Administrator or Cloud Application Administrator.

  Changes may take a few minutes to propagate.

  

  ​

  Access rights

  • Azure DevOps organization settings.
  • User management.
  • App registrations in the Azure portal.
  • Install and remove applications.
  • Manage users and permissions.

  ​

  Licenses

  • At least one Basic access license must be available for the Qodo app user. Free organizations may have a limit (for example, 5 users). If no license is available, the installation fails.

  ​

  Tenant-level consent and policies

  • User consent settings: “Do not allow user consent” may prevent app authorization.
  • Admin consent requirements: Your organization may require admin approval for app permissions.
  • Microsoft-managed consent policies: These can restrict which apps can be installed or what permissions they can request.
• PAT: A personal access token with the required scopes.
  How to create a personal access token

  Before you begin

  • Ensure you are added to the required Azure DevOps organization.
  • You must belong to the Project Collection Administrators group. Go to Organization Settings → Permissions → Project Collection Administrators → Members to verify.

  

  1. Go to Azure DevOps.
  2. Open User Settings in the top-right corner.
  3. Select Personal Access Tokens from the dropdown.

  

  4. Click New Token.

  The Organization dropdown controls the token’s scope. Selecting a specific organization restricts the token to that organization only. Selecting All accessible organizations grants access across all organizations.

  

  Required scopes

  PAT scopes alone are not sufficient. The user who creates the PAT must also have project-level permissions (typically Project Admin) for webhook creation and PR operations to succeed.

  Scope	Access	Purpose
  Code	Read & Write	Repository and PR access.
  Project and Team	Read & Write	Webhook (Service Hooks) management.
  Pull Request Threads	Read & Write	Commenting on pull requests.
  Wiki	Read & Write	Read, create, and update the project wiki.

​

Access the Azure DevOps integration

​

Install Qodo on Azure DevOps

1

Installation type

Select the authentication method that fits your environment. OAuth app registration is selected by default. If you are using a personal access token instead, select the Personal access token (PAT) tab below. Steps 2 and 3 do not apply. Proceed directly to Step 4.

• OAuth app registration (Recommended)
• Personal access token (PAT)

This method connects using Azure AD app registration and is best for enterprise security and automated access.

• Click Continue to proceed to the manifest review.

This method connects using a personal access token and is suitable when Azure AD admin access is unavailable.

1

Enter your token

Enter your personal access token in the field provided.

Token validation errors

• Failed to validate PAT: the token was copied incomplete. Check that the full token was pasted and try again.
  
• Invalid Personal Access Token: the token is expired or revoked. Generate a new token and try again.
  

2

Organization URL (if prompted)

If the Organization URL field appears, enter your org URL in the format https://dev.azure.com/{your-organization}.

The field appears in two cases:

• Single-org scoped token: Your token has limited scope. Enter the URL to proceed.
• Expired or revoked token: The field appears, but entering the org URL will result in an “Invalid Personal Access Token” error. Regenerate your token and try again.

3

Continue

Click Continue to proceed to repository selection.

2

Review manifest

OAuth only. PAT users: skip to Step 4.

Review the application manifest before installation.

The manifest defines the permissions and scopes Qodo requires.

• Click Continue.

3

Install guide

OAuth only. PAT users: skip to Step 4.

The wizard displays a guide for the two steps that will take place in Microsoft’s environment. Review them below, then click Install to proceed.

1

Azure Admin

Create an Azure application for Qodo. You must be an Azure AD administrator and grant admin consent to complete this step. The process on the Microsoft Azure portal may take up to a minute.

2

ADO Admin

A service principal (the app’s identity in Azure AD) is added to your Azure DevOps organization, granting Qodo the required access rights. You must be an Azure AD administrator and grant admin consent to complete this step.

• Click Install (opens in a new tab) to begin.

4

Connect repositories

1

Find your repositories

Use the search bar to find specific repositories, or browse the tree: Organization → Projects → Repositories.

This step may take up to a minute to load.

2

Select repositories

Select individual repositories, an entire project, or the full organization.

Repositories that already have Qodo installed are not available for selection. To reinstall, remove the existing installation first.

3

Continue

Click Setup to continue. If you see an error, see Common issues and detailed requirements.

5

Check connection

Qodo automatically sets up the required webhooks.

Once complete, a confirmation is displayed.

• Click Sync to proceed.

6

Enable Qodo

Qodo is now enabled for the selected repositories.

The confirmation screen shows the number of connected repositories and confirms that AI code review, auto rule generation, and codebase context are active.

• Click Finish installation.

​

Verify the installation

​

What’s next