Rovo AI Vendor Concern – Anthropic Supply Chain Risk Designation

Teal Wilkes

Hi team,

We've recently designated Anthropic as a supply chain risk within our organization, which means we need to cease use of any tools powered by Anthropic's models.

We currently use Rovo across our Atlassian products and understand it is powered by Anthropic's Claude. We have two questions:

1. Is it possible to configure Rovo to use an alternative AI model/vendor that is not Anthropic? If so, what options are available and how do we make that change?

2. If no alternative vendor option is available, can you provide us with step-by-step instructions to fully disable Rovo across our Atlassian environment so that no Anthropic-powered features are accessible to our users?

We'd appreciate an urgent response given the compliance implications. Please let us know if you need any additional information about our account or environment.

Arkadiusz Wroblewski

Hello and Welcome to Atlassian Community @Teal Wilkes 

One important clarification regarding compliance: Rovo uses a mix of model providers (OpenAI, Anthropic, Google, and Atlassian-hosted models), but admins can't selectively disable Anthropic while keeping Rovo active. Because routing is dynamic, keeping Rovo "on" means Claude could still be used behind the scenes.👀

If you need to block native AI entirely, an Org Admin can disable it under admin.atlassian.com (Rovo → Rovo access) across all site apps (and separately in Bitbucket workspace settings).

Just keep in mind this won't cover third-party Marketplace apps like Claude Agent for Jira, which need to be audited separately.🤠

While Cloud Enterprise offers Atlassian-hosted LLM options, only Atlassian Support can provide a binding compliance attestation regarding model routing. I'd recommend opening a support ticket directly to confirm the exact guarantees available for your plan.

Best,

Arek 🤠