Installing and sharing the extension

You install the ADO Pilot Marketplace extension from the Azure DevOps Marketplace to add two UI conveniences to your organization: a "Run AI Review" entry in the pull request action menu and an "ADO Pilot" hub under organization administration. The extension is optional.

What the extension adds

Installing ADO Pilot from the Marketplace adds two contributions to your organization:

• A pull request action menu entry that opens a confirmation dialog where you can run an AI review for that pull request. See Using the PR action menu.
• An organization administration hub that shows whether reviews are active for the organization, a Connection health panel listing per-project subscription status, a Run a review form for triggering a review on any open pull request, and a link to the app.adopilot.dev dashboard. See The organization admin settings hub.

The extension does not hold API keys, webhook secrets, or your personal access token (PAT). Subscriptions are provisioned by the ADO Pilot backend during onboarding using the PAT you supplied at signup. All configuration happens at app.adopilot.dev; the extension does not write configuration to Azure DevOps.

Before you install

You need:

• An Azure DevOps Services organization (cloud-hosted). On-premises Azure DevOps Server is not supported.
• Permission to install Marketplace extensions for that organization. In Azure DevOps this is typically the Project Collection Administrators group.
• An active ADO Pilot subscription provisioned through the adopilot.dev onboarding wizard. Without onboarding, the extension installs but the settings hub will show "Not configured".

Install from the Marketplace

1. Open the ADO Pilot listing on the Azure DevOps Marketplace (publisher adopilot).
2. Click Get it free to begin the install gesture. The Marketplace shows a "Paid" indicator on the listing — the listing itself does not collect payment because ADO Pilot is Bring Your Own License (BYOL); billing happens at adopilot.dev.
3. Choose the Azure DevOps organization to install into from the Select an Azure DevOps organization dropdown.
4. Click Install. Azure DevOps lists the scopes the extension requests and asks you to confirm.
5. After confirmation, Azure DevOps redirects you to the organization with the extension installed.

The Marketplace upload is asynchronous on Microsoft's side. New installs are usually available within a minute, but allow a few minutes for the contributions to appear in pull requests and organization settings.

Scopes the extension requests

The extension requests minimal scopes. The declared scopes are vso.code (used to resolve repository names to GUIDs when triggering a review, to evaluate organization-administrator permissions, and to identify your Azure DevOps user) and vso.profile (a declared profile scope that the extension does not currently use for any active feature). Review traffic is processed by the backend with your PAT.

If a future release needs additional scopes, every existing install will be prompted to re-consent. ADO Pilot communicates scope changes ahead of any release that requires them.

What changes after install

• The pull request page shows a new entry in the action menu (the three-dot menu next to the Approve and Complete controls). Selecting it opens a confirmation dialog with a Run review button and a Cancel button.
• The organization administration page shows a new "ADO Pilot" item in the left navigation. Only Organization Administrators can open it; other roles see an unauthorized message. The hub includes a Connection health panel showing per-project subscription status and a Run a review form for triggering a review on any open pull request.
• Reviews continue running. If reviews were already firing before you installed the extension, nothing changes about how they are triggered or posted.

Installing in multiple organizations

Each Azure DevOps organization is a separate install target. Repeat the install steps above for each organization where you want the extension's UI — the ADO Pilot listing is public, so there is no publisher-side sharing step for a customer to use.

Each organization needs its own ADO Pilot subscription at adopilot.dev. The extension does not move subscriptions between organizations.

Updating the extension

Azure DevOps auto-updates Marketplace extensions when a new version ships. You do not need to take any action to receive non-breaking updates. If a release requires new scopes, Azure DevOps will surface a re-consent prompt the next time an administrator opens the extension management page.

If install fails

• "You don't have permission to install" — your account is not in the Project Collection Administrators group for the target organization. Ask an organization administrator to install on your behalf.
• The contributions don't appear after install — Marketplace validation can take a few minutes. Refresh the pull request page or the organization settings page. If the entries are still missing after ten minutes, see Frequently asked questions.
• "Not configured" in the settings hub after install — onboarding has not completed, or the PAT used at onboarding has expired. Open the adopilot.dev dashboard to finish onboarding or rotate credentials.