How can we disable the “Enable Copilot Code Review for your Azure Repos pull requests” prompts in Azure DevOps?

Daniel-4204 375 Reputation points
2026-10-08T16:32:08.21+00:00

Is there a supported way to permanently disable or hide the “Enable Copilot Code Review for your Azure Repos pull requests” prompts throughout Microsoft-hosted Azure DevOps?

These prompts are currently appearing in multiple locations, including the project interface and Organization Settings. Neither our administrators, project managers, nor developers want to enable or use Copilot Code Review. We understand the feature, its data policies, and potential costs, but would like to opt out of the promotional prompts entirely.

One senior developer even asked (if we had to) whether we could enable the feature and then disable its functionality simply to make the prompts disappear, which we would prefer not to do.

Is there an organization-level setting, policy, or other supported method to suppress these Copilot Code Review prompts without enabling the feature?

User's image

Azure DevOps
0 comments
Answer accepted by question author
Allan Solomon Mejia 10,385 Reputation points
2026-10-08T17:14:55.2533333+00:00

Hi @Daniel-4204

Microsoft currently provides a supported organization-level control for disabling the Copilot code-review feature:

  1. Open Organization settings.
  2. Select Repos > Repositories.
  3. Under GitHub Copilot code review, set Allow repositories in this organization to use Copilot code review to Off.

Turning off the organization-level setting disables Copilot code review for every repository in the organization. The feature also requires explicit organization-level enablement by a Project Collection Administrator before projects or repositories can use it.

However, it doesn’t suppresses promotional banners, “What’s new” cards, or enablement prompts throughout the Azure DevOps interface. There's no documented organization policy or user setting specifically for hiding those promotional messages.

Enabling and then disabling the feature isn’t a documented or recommended method for dismissing the prompts. If the organization toggle is already Off and the prompts remain, they appear to be part of the Azure DevOps preview rollout rather than evidence that Copilot code review is enabled or generating charges. Billing applies to completed Copilot code reviews and requires the documented enablement configuration.

For an organization-wide prompt-suppression option, submit feedback through the Azure DevOps Developer Community, which Microsoft identifies as the feedback channel for this preview.

References:

Get started with Copilot code review

Azure DevOps Developer Community

Help make this community better for everyone: If this answer helped or resolved your issue, please accept it or upvote it. If not, share more details in a comment so we can continue the discussion and find the right solution. Thank you.

Was this answer helpful?

1 person found this answer helpful.
0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Rakesh Mishra 11,510 Reputation points Microsoft External Staff Moderator
    2026-10-09T10:08:55.32+00:00

    Hello @Daniel-4204 ,

    The organization toggle covered in the @Allan Solomon Mejia answer is the main control. Since your teams don't want to use the feature at all, here are a few more ways to make sure it stays unused while the preview prompts are still visible.

    1. Use the audit log to confirm it's off

    Azure DevOps records Copilot Code Review configuration changes on the Organization settings > Auditing page. This includes:

    • the feature being enabled or disabled at the organization, project, or repository level
    • changes to custom instructions
    • changes to the agent pool
    • changes to the default effort level
    • branch policies added for automatic reviews

    If none of these events appear, nobody has turned it on. You can also set up an audit stream if you want these changes sent to your SIEM.

    2. Keep it off in Preview features too Copilot Code Review is also listed under Preview features as Copilot Code Review for Pull Requests. A Project Collection Administrator can change the scope to for this organization and confirm it's turned off there. That way users aren't opted in at the organization level.

    3. Check branch policies Automatic reviews are set up through branch policies at the project or repository level. If your admins periodically check that no policy requests a Copilot review, nothing will run automatically when pull requests are created.

    4. Use a cost alert as a safety net Each Copilot review is billed to the Azure subscription linked to the organization through Azure Cost Management. Costs can be tracked by Azure DevOps project, and you can set budget alerts on them. A small budget alert on that subscription will tell you right away if a review is ever charged.

    About the prompts The prompts showed up after Copilot Code Review became a public preview available to every Azure DevOps Services organization without signing up. They're part of that rollout and don't mean the feature is active. If you post a suggestion on Developer Community asking for an organization-wide way to hide them, other customers can upvote it, which helps the product team decide what to work on.

    References

    Please let me know if any further questions.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.