Skip to main content

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.

Launching the wizard gives you access to the Rule System, findings, and other advanced code review features and improves overall performance and reliability. The process involves installing Qodo using the new wizard and then cleaning up your old setup to avoid conflicts. Without migrating, your existing installations will continue to work but you will not have access to advanced features such as rules and findings.
1

Install Qodo app in Azure DevOps using the new wizard

Follow the installation wizard to complete your new Azure DevOps setup.
2

Verify the new installation is working

Before removing your old setup, confirm the new installation is active.
1

Open a pull request

Open a pull request or use an existing one in any connected repository.
2

Post /config as a comment

Add /config as a comment on the pull request.
3

Check the response

Confirm the review is triggered from the correct user:
  • If the installation was created using a Personal Access Token (PAT), the review should appear from the PAT user.
  • If the installation was created using the OAuth app flow, the review should appear from the Service Principal user.
If two installations are running, you will see two sets of 👀 reactions. Once you see the new installation responding as expected, proceed with the cleanup steps below to remove your old setup.
3

Review webhooks

The new installation automatically replaces existing Qodo webhooks when scopes match or expand. Use the table below to understand what happens based on your scope change:
Existing scopeNew scopeResult
ProjectProjectWebhooks are replaced (same scope)
RepositoryRepository (same repos)Webhooks are replaced (same scope and repo set)
RepositoryProjectWebhooks are replaced (project-level overrides repo-level)
ProjectRepositoryWebhooks are not replaced; new webhooks are added alongside existing ones
If you are moving from project scope to repository scope, you may experience:
  • Duplicate webhook events
  • Duplicate PR comments
  • Repeated automation
To avoid this, manually remove the old project-level webhooks:
1
Go to Azure DevOps.
2
Open Project Settings.
3
Select Service Hooks.
4
Remove the old Qodo webhooks.
4

Review Qodo users

Remove any old Qodo users or service principals that are no longer needed. This keeps your Azure DevOps organization clean and avoids confusion with the new installation.
1
Go to Azure DevOps.
2
Open Organization Settings.
3
Select Users.
4
Remove any old Qodo users or service principals that are no longer in use.
Do not delete the user named Qodo-code-review as this belongs to the new installation.
5

Review Azure applications (optional)

Old app registrations from your previous Qodo installation may still remain in Microsoft Entra ID. Removing them keeps your environment tidy, but this step is optional and should only be done if you are confident the app is no longer in use.
1
Go to Microsoft Entra ID.
2
Open App registrations or Enterprise applications.
3
Identify any old Qodo apps.
4
Remove them only if you are sure they are not part of the new installation.
Do not remove an app or user if you are unsure whether it belongs to the new installation. If you are unsure, contact your Qodo Account Manager for guidance.
Your Azure DevOps integration is now fully migrated to the new wizard. Qodo is running through the new installation on your selected repositories.

​
What’s next