Anthropic Claude models are not available in all regions or subscription types, and there are specific prerequisites for deploying them in Azure AI Foundry.
1. Subscription and access requirements
Anthropic Claude models in Microsoft Foundry require:
- A paid Azure subscription with a billing account in a country/region where Anthropic offers the models for purchase.
- Enterprise or MCA-E subscription eligibility for Claude models. Subscriptions that are not supported include:
- Enterprise accounts located in South Korea
- Cloud Solution Provider (CSP) subscriptions
- Subscriptions without an active pay-as-you-go billing method (for example, student, free trial, startup credit–based accounts)
- Sponsored subscriptions that only use Azure credits (if a credit card is on file, the card is charged instead of credits)
If the subscription is not eligible, a “subscription eligibility error” will block deployment.
Some Anthropic variants (Claude Mythos 5 and Claude Mythos Preview) are gated research previews and require Anthropic-approved access, prioritized for defensive cybersecurity use cases.
2. Region availability
Anthropic Claude models are not available in all Azure regions. For Foundry deployments:
- Claude models use the Global Standard deployment type.
- For both serverless/classic and standard deployments, the Hub/Project region must be:
If the AI Hub/Project is created in any other region (for example, East US, West Europe, etc.), Anthropic deployments will fail with region errors or the models may not be deployable.
Additionally, offer availability is limited to Microsoft-managed countries/regions (excluding Belarus and Russia). If the billing account region is not in the supported list, deployment will not be allowed.
3. Waitlist or special access
- General Anthropic Claude models (such as Claude Opus, Sonnet, Haiku series) require only that subscription and region prerequisites are met.
- Claude Mythos 5 and Claude Mythos Preview are available only as gated research preview. Access is granted solely at Anthropic’s discretion and prioritized for defensive cybersecurity use cases. These require separate approval from Anthropic.
4. Prerequisites and common deployment blockers
To deploy Anthropic Claude models successfully in Azure AI Foundry:
- Subscription eligibility
- Ensure the subscription is Enterprise or MCA-E and not one of the unsupported types listed above.
- Region alignment
- Create the AI Hub/Project in East US 2 or Sweden Central.
- Anthropic models cannot be deployed if the project/hub is in another region.
- Permissions
- The user deploying must have Contributor or Owner role on the resource group and Foundry resource.
- For Entra ID-based access (for calling the model), the Cognitive Services User role may be required.
- Quota and capacity
- Anthropic models are subject to quota and rate limits. If hitting HTTP 429 or quota errors, check quotas in the Foundry portal under Operate > Quotas and request increases if needed.
- Endpoint and configuration
- For calling deployed Claude models, use the Anthropic Messages API endpoint pattern:
-
https://<resource-name>.services.ai.azure.com/anthropic/v1/messages
- For Entra ID auth, use scope
https://ai.azure.com/.default.
5. Why deployment may be failing in the described scenario
Given the environment described (Pay-As-You-Go, region like East US):
- If the AI Hub/Project is in East US (not East US 2) or any region other than East US 2 or Sweden Central, Anthropic deployments will fail with region-related errors.
- If the Pay-As-You-Go subscription is not an Enterprise or MCA-E type (or falls under unsupported categories such as trial/credit-only), a subscription eligibility error will prevent deployment.
To proceed:
- Verify that the subscription type is eligible (Enterprise or MCA-E, not CSP, trial, or credit-only).
- Create a new AI Hub/Project in East US 2 or Sweden Central.
- Deploy the Anthropic Claude model from the Model Catalog into that project.
If these conditions are met and deployment still fails, check for specific error codes (401, 403, 404, 429, subscription eligibility error, region not available) and apply the corresponding troubleshooting guidance.
References: