The ADO Pilot Marketplace extension is **optional**. Reviews run through service-hook subscriptions that the onboarding wizard provisions directly in your Azure DevOps organization — they do not require the extension. Installing it is recommended: it registers a branded service-hook consumer and adds a **Run AI Review** button plus an in-ADO settings hub. See [Quickstart](quickstart.md) for where this step fits.

Beyond enabling the core integration, the extension also adds a **Run AI Review** entry in the PR action menu and a settings hub inside Azure DevOps.

{% callout type="info" title="Installing first is recommended" %}
Installing the extension before you run the onboarding wizard lets the wizard register subscriptions against the branded service-hook consumer. It is not required — reviews run through the subscriptions the wizard provisions either way. Complete [Quickstart](quickstart.md).
{% /callout %}

## What the extension adds

- **Run AI Review** entry on the pull-request action menu. Opens a confirm dialog with a **Run review** button that triggers an on-demand AI review of the pull request. Triggering a review spends review credits, same as any other review. See [Using the PR action menu](../extension/pr-action-menu.md).
- **ADO Pilot** hub under your organization's admin pages. Shows connection health and review status, and lets you trigger an on-demand review by entering any open pull request URL in the org; full configuration still lives at `adopilot.dev`.
- **ADO Pilot** appears as a service-hook consumer when an admin browses your organization's service hooks. Subscriptions managed from the consumer page redirect to `adopilot.dev`.

## What the extension doesn't configure

- All configuration — repository selection, branch filters, exclusion patterns, plan and billing — stays at `adopilot.dev`. The in-ADO hub is a status and trigger surface: it shows connection health and lets you launch on-demand reviews, but configuration tasks happen at the dashboard.
- The extension does not duplicate or modify existing service-hook subscriptions. Once subscriptions are provisioned by the wizard, the extension's role is to keep the branded consumer registered so those subscriptions continue routing correctly.

## Required scopes

The extension (the Marketplace item you install) requests `vso.code` and `vso.profile` from Azure DevOps. These two scopes are what appear in the Marketplace consent prompt when an admin installs the extension.

The personal access token (PAT) you provide during onboarding is separate and has its own scope requirements — those are covered in [Creating a PAT](../connecting-ado/creating-a-pat.md), not here.

Azure DevOps treats scope changes as a re-consent event for every existing install. The current scope set is intentionally minimal so future point releases don't force your administrators to re-consent.

## Install the extension

You need organization-admin permission in the target Azure DevOps Services organization to install the extension.

{% steps %}

### Step 1 — Open the Marketplace listing

Open the [ADO Pilot listing](https://marketplace.visualstudio.com/items?itemName=adopilot.adopilot-pr-review) on the Azure DevOps Marketplace, or follow the listing link from `adopilot.dev`.

### Step 2 — Install into your organization

Click **Get it free** (the Marketplace label for paid BYOL extensions; you pay ADO Pilot directly), select your organization from the dropdown, and click **Install**. Azure DevOps prompts you to consent to the scopes listed above.

### Step 3 — Confirm the install

Azure DevOps does not redirect you to a post-install page — installation finishes on the Marketplace page itself. Azure DevOps automatically notifies ADO Pilot when the extension is installed, via a signed server-to-server callback — no action is needed from you. If your organization has no ADO Pilot account yet, we separately identify the installer the first time an admin opens the **ADO Pilot** hub under organization settings (see below), and send them a one-time "get started" email pointing at signup.

To verify the install:

- Open any pull request in the organization. The **Run AI Review** entry appears on the action menu.
- Open **Organization settings** (the gear icon at the bottom of the Azure DevOps left navigation). **ADO Pilot** appears in the admin hub list and shows your connection and review status.

{% /steps %}

## After installation

Service hook subscriptions installed by the onboarding wizard remain in place — the extension does not duplicate them. You don't need to reconfigure anything. The **Run AI Review** action menu entry opens a confirm dialog to run a review on demand; automatic reviews fire on every pull request create and update through those subscriptions.

## Uninstalling

To remove the extension:

1. Go to **Organization settings** > **Extensions** > **Installed**.
2. Find **ADO Pilot** and click **Uninstall**.

What stops:

- The **Run AI Review** PR action menu entry.
- The **ADO Pilot** organization-admin hub.

What continues (with a caveat):

- Reviews. Your service-hook subscriptions are not deleted on uninstall, but uninstalling deregisters the branded consumer that routes events — refresh your service hooks from the ADO Pilot portal afterward so reviews keep firing.
- Billing. You still have an active plan and will continue to be charged until you cancel.

To fully stop reviews and billing, cancel your subscription in the dashboard. See [Uninstalling the extension](../extension/uninstalling.md) for the complete shutdown procedure.