Some access is granted to your organization through a verification program and then turned on for each platform you use. If your organization relies on a program or a restricted model today, plan it as a separate step and allow lead time for it.
This guide is for admins of organizations on Claude Enterprise plans.
This article is part of Move from Claude Enterprise to Claude Desktop on a cloud provider, which defines the terms wave, overlap period, and cutoff date.
Custom roles and model access settings are set in your Claude Enterprise organization. In Claude Desktop on 3P, your own configuration decides which models the picker offers, so plan to set these up again.
Cyber Verification Program (CVP)
For eligibility, access tiers, data retention, and how to apply, see Cyber Verification Program. For the move, plan for these points:
Link each cloud account: In the Verification Portal, link your AWS account, Google Cloud project, or Azure subscription. The article gives the steps for each platform. You need an Anthropic account to use the portal, even if you only use a cloud provider.
Check availability: On Amazon Bedrock, availability is limited. Check the program article for who's eligible. On Google Cloud's Agent Platform, accept the Advanced AI Safety Addendum, then enable advanced AI capabilities and data sharing for each model and location you use. See Google's enrollment steps.
Allow lead time: On cloud providers, access to the program's restricted model follows approval by about five business days. A committed contract adds a form and a private offer in the cloud marketplace.
Credentials: The security requirements don't permit long-lived cloud credentials (for Defense Access, see the article for when this applies), and each approved user must sign in as themselves. Check them before you decide how users authenticate to your provider.
If you're already approved: Each Claude organization needs its own application. To add a cloud account, link it to the same Anthropic organization in the Verification Portal. You don't need a new application. Also turn on your tier for the new account.
Other programs
Each program lists the platforms it supports. For example, the Life Sciences Verification Program is in beta and isn't yet available on third-party platforms. Access under it stays on Enterprise plans, Team plans, and the API.
Restricted models
Some models are available only through limited access programs like these. Covered Models lists them, and each model's page lists the platforms it's available on.
Control who can use which models
Where | Control | Good to know |
Claude Desktop on 3P |
| A user in several groups gets the list from the highest-ranked of their policies that sets one. The lists aren't combined. |
Claude Code CLI | Set | On a cloud provider, it arrives by file or OS policy, or through a Claude apps gateway. |
Your cloud provider | AWS: Deny
Google Cloud: See Control access to Model Garden models.
Azure: A model must be deployed before it can be called, and an Azure Policy can restrict deployments to approved models. That policy is checked at deployment time. | These controls apply at the provider, outside the app. |
Important: Set hard limits at your provider. The Claude Desktop on 3P and Claude Code lists above set what users can pick in those apps. Sessions on a cloud provider authenticate against your provider, and its access policies govern them. Removing a user from the console doesn't end their access to the provider.
