Claude models keep failing deployment

Question

Claude models keep failing deployment

Krishnang Dalal 25

I am trying to deploy Claude models (Sonnet-4.6 and 4.5) but they keep failing deployment during the provisioning stage. I am on pay-as-you-go tier, and I am also subscribed to Claude models through their enterprise marketplace under the pay-as-you-go tier.

Any idea why is this happening? Deployment regions: eastus2 and swedencentral. Thank you!

Krishnang Dalal 25 Reputation points

2026-06-06T14:49:53.0333333+00:00

Where do I add payment type in Azure Foundry project?
SRILAKSHMI C 19,550 Reputation points Microsoft External Staff Moderator

2026-06-08T16:09:51.3366667+00:00

Hi @Krishnang Dalal

We are currently coordinating with the backend team to investigate this further. Kindly allow some time for an update while we review the issue in detail.

Thank you!
SRILAKSHMI C 19,550 Reputation points Microsoft External Staff Moderator

2026-06-10T09:21:58.9033333+00:00

Hi @Krishnang Dalal

Please try deploying this using the CLI or REST API as an alternative approach.

Thank you!
SRILAKSHMI C 19,550 Reputation points Microsoft External Staff Moderator

2026-06-16T09:35:48.96+00:00

Hi @Krishnang Dalal

Did you try the above solution.

Thank you!
SRILAKSHMI C 19,550 Reputation points Microsoft External Staff Moderator

2026-06-17T07:38:06.5966667+00:00
Hi @Krishnang Dalal

Just wanted to check in to see if the deployment issue has been resolved.

From the investigation, this behavior is currently a known limitation. For Anthropic (Claude) model deployments, the service requires additional metadata (ModelProviderData) including industry, organizationName, and countryCode. However, in the Azure AI Foundry portal, only the industry field is visible, and the remaining required fields are not exposed through the UI. This leads to incomplete requests being sent, resulting in the observed error.

As a workaround, deployments can be completed successfully by providing the required metadata using CLI or REST API.

Sample payload:

{ "sku": { "name": "GlobalStandard", "capacity": 2000 }, "properties": { "model": { "format": "Anthropic", "name": "claude-opus-4-6", "version": "1" }, "modelProviderData": { "industry": "technology", "organizationName": "<Organization Name>", "countryCode": "<Country Code>" }, "versionUpgradeOption": "OnceNewDefaultVersionAvailable" } }

Sample CLI command:

az rest --method PUT \ --uri "https://management.azure.com/subscriptions/<SUBSCRIPTION_ID>/resourceGroups/<RESOURCE_GROUP>/providers/Microsoft.CognitiveServices/accounts/<ACCOUNT_NAME>/deployments/<DEPLOYMENT_NAME>?api-version=2025-10-01-preview" \ --body "@body.json"

Important considerations:

Ensure all three fields (industry, organizationName, countryCode) are provided

Use API version 2025-10-01-preview or later to avoid validation issues

Using lowercase values for fields like industry may help avoid validation inconsistencies

Thank you for your patience.
Krishnang Dalal 25 Reputation points

2026-06-18T19:23:08.1+00:00

Hi @SRILAKSHMI C , sorry for the delay. I have not tried this yet as I was able to use another model as well as deploy it by creating another Foundry resource. I do have another issue where I have deployed the grok-4-20-reasoning model and the API is not returning thinking tokens in the metadata (only return reasoning token count) when using OpenAI SDK. It seems like there is an issue with the API version which is old but I am only able to deploy the model on that API version '2024-05-01-preview' (Version 1). Do you have any idea what might be going wrong?
SRILAKSHMI C 19,550 Reputation points Microsoft External Staff Moderator

2026-06-22T16:39:57.99+00:00

Hi @Krishnang Dalal

Could you please create a separate thread for this new issue and include all relevant details? This will help us track and investigate it more effectively.

Thank you!

2 answers

Your answer

Krishnang Dalal 25 Reputation points

2026-06-06T14:49:53.0333333+00:00

Where do I add payment type in Azure Foundry project?
SRILAKSHMI C 19,550 Reputation points Microsoft External Staff Moderator

2026-06-08T16:09:51.3366667+00:00

Hi @Krishnang Dalal

We are currently coordinating with the backend team to investigate this further. Kindly allow some time for an update while we review the issue in detail.

Thank you!
SRILAKSHMI C 19,550 Reputation points Microsoft External Staff Moderator

2026-06-10T09:21:58.9033333+00:00

Hi @Krishnang Dalal

Please try deploying this using the CLI or REST API as an alternative approach.

Thank you!
SRILAKSHMI C 19,550 Reputation points Microsoft External Staff Moderator

2026-06-16T09:35:48.96+00:00

Hi @Krishnang Dalal

Did you try the above solution.

Thank you!
SRILAKSHMI C 19,550 Reputation points Microsoft External Staff Moderator

2026-06-17T07:38:06.5966667+00:00

Hi @Krishnang Dalal

Just wanted to check in to see if the deployment issue has been resolved.

From the investigation, this behavior is currently a known limitation. For Anthropic (Claude) model deployments, the service requires additional metadata (ModelProviderData) including industry, organizationName, and countryCode. However, in the Azure AI Foundry portal, only the industry field is visible, and the remaining required fields are not exposed through the UI. This leads to incomplete requests being sent, resulting in the observed error.

As a workaround, deployments can be completed successfully by providing the required metadata using CLI or REST API.

Sample payload:

{ "sku": { "name": "GlobalStandard", "capacity": 2000 }, "properties": { "model": { "format": "Anthropic", "name": "claude-opus-4-6", "version": "1" }, "modelProviderData": { "industry": "technology", "organizationName": "<Organization Name>", "countryCode": "<Country Code>" }, "versionUpgradeOption": "OnceNewDefaultVersionAvailable" } }

Sample CLI command:

az rest --method PUT \ --uri "https://management.azure.com/subscriptions/<SUBSCRIPTION_ID>/resourceGroups/<RESOURCE_GROUP>/providers/Microsoft.CognitiveServices/accounts/<ACCOUNT_NAME>/deployments/<DEPLOYMENT_NAME>?api-version=2025-10-01-preview" \ --body "@body.json"

Important considerations:

Ensure all three fields (industry, organizationName, countryCode) are provided

Use API version 2025-10-01-preview or later to avoid validation issues

Using lowercase values for fields like industry may help avoid validation inconsistencies

Thank you for your patience.
Krishnang Dalal 25 Reputation points

2026-06-18T19:23:08.1+00:00

Hi @SRILAKSHMI C , sorry for the delay. I have not tried this yet as I was able to use another model as well as deploy it by creating another Foundry resource. I do have another issue where I have deployed the grok-4-20-reasoning model and the API is not returning thinking tokens in the metadata (only return reasoning token count) when using OpenAI SDK. It seems like there is an issue with the API version which is old but I am only able to deploy the model on that API version '2024-05-01-preview' (Version 1). Do you have any idea what might be going wrong?
SRILAKSHMI C 19,550 Reputation points Microsoft External Staff Moderator

2026-06-22T16:39:57.99+00:00

Hi @Krishnang Dalal

Could you please create a separate thread for this new issue and include all relevant details? This will help us track and investigate it more effectively.

Thank you!

Answer 1

kagiyama yutaka 3,925

Claude deploys only when the project region, the Claude offer’s subscription and tenant, and your RBAC all line up. Anything beyond those conditions is handled by Azure support using the Activity‑log error from the failed deployment.

kagiyama yutaka 3,925 Reputation points

2026-06-06T15:26:59.4133333+00:00

Foundry projects don’t have any place to add a payment method. You just update the payment method on the Azure subscription that the project runs under.

Answer 2

Deployment failures for Claude Sonnet 4.6 and 4.5 in Microsoft Foundry are typically caused by one of the following issues, based on the documented requirements and troubleshooting guidance:

Subscription type or region eligibility

Claude models require a paid Azure subscription with a valid payment method and must be in a country/region where Anthropic offers the models for purchase.
The following subscription types are not supported for Claude models, even if they appear pay-as-you-go–like:
- Enterprise Accounts located in South Korea
- Cloud Solution Provider subscriptions
- Azure 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 the subscription falls into any of these categories, deployments will fail during provisioning even though the Marketplace subscription exists.

Project/Hub region requirements

Claude models in Foundry are only available in:
- East US 2
- Sweden Central
The Foundry project (or hub) where the deployment is created must also be in one of these regions. If the project is in any other region, deployments will fail.

Foundry and Marketplace permissions

To deploy partner models like Claude, the following are required:
- Contributor or Owner role on the resource group / Foundry resource.
- Access to Azure Marketplace with the correct permissions to subscribe to model offerings.
If Marketplace access is not correctly configured or the user lacks Contributor/Owner on the resource group, deployment creation can fail.

Region availability / backend issues

Claude models use a Global Standard deployment type but are still bound to the supported hub/project regions (East US 2, Sweden Central).
If there is a transient backend or capacity issue in those regions, deployments can fail during provisioning. In similar cases for other models, users have resolved stuck or failing deployments by deleting the failed deployment and recreating it later.

Recommended checks and actions

Confirm subscription eligibility:
- Verify that the subscription is a supported pay-as-you-go type and not CSP, student, free trial, or credits-only sponsored.
Verify project region:
- Ensure the Foundry project used for deployment is in East US 2 or Sweden Central.
Validate permissions:
- Confirm Contributor or Owner role on the resource group.
- Confirm Marketplace access is enabled for Foundry Models from partners and that the Claude offer is successfully subscribed.
Retry deployment:
- If all prerequisites are met and the deployment is stuck/failing in provisioning, delete the failed deployment and recreate it after some time.

If deployments continue to fail after these checks, the scenario likely requires a support case so backend provisioning and regional capacity can be investigated.

References: