Deployment Failure for claude-sonnet-4-6 in Sweden Central

The error details and subscription-specific investigation requested require access to internal Azure telemetry and support tools, which isn't available here. However, the behavior described matches known classes of issues for Claude deployments in Microsoft Foundry and can be narrowed down with the following checks and actions on the tenant side before (or in parallel with) opening a support ticket.

1. Validate subscription and region eligibility

Claude models in Foundry have stricter subscription and region requirements than standard Azure services:

• Confirm the subscription is an Enterprise or MCA-E subscription and not one of the unsupported types (CSP, free trial, student, credit-only, or certain enterprise accounts such as those located in South Korea).
• Ensure the Foundry project and the Claude deployment are both in a supported region for Claude models: East US2 or Sweden Central.
• Verify that Azure Marketplace access is enabled for the subscription and that the Anthropic offers are allowed for the subscription’s billing country/region.

If the subscription or billing region is not eligible, deployments can fail even when quota has been granted.

2. Confirm Foundry and Marketplace prerequisites

On the admin side, verify the following for the Foundry resource used for claude-sonnet-4-6:

• The Foundry project exists and is created in Sweden Central.
• The account performing the deployment has at least Contributor or Owner role on the resource group that contains the Foundry resource.
• Azure Marketplace permissions are in place to subscribe to third‑party model offerings (Anthropic) for this subscription.

If Marketplace purchase or eligibility checks fail, deployment can fail with generic provisioning errors.

3. Check for common partner-model deployment issues

Third‑party models in Foundry (including Anthropic) can fail deployment for reasons such as:

• Offer not available in the subscription’s billing country/region, even if the technical region (Sweden Central) is supported.
• Marketplace purchase eligibility check failing for the specific SKU.
• Azure Marketplace rejecting the model subscription due to rate limits or repeated subscription attempts.

In these cases, the recommended next step is to contact support and include the subscription ID and region so the Marketplace/Foundry backend can be checked.

4. Validate Claude model deployment and configuration

For claude-sonnet-4-6 specifically:

• Ensure the model is deployed as a Foundry model in Sweden Central using the Foundry portal, following the standard deployment flow for Claude models.
• After deployment, confirm the deployment’s provisioningState is Succeeded and note the Target URI and Key from the deployment’s Details tab.
• If the deployment remains in ProvisioningFailed, delete the failed deployment and attempt to redeploy after some time. Transient backend issues have been resolved in the past by deleting and recreating the deployment once the underlying incident was fixed.

5. Check Claude Code / client workspace configuration

On the client side (workspace / Claude Code / tools using the model):

• Confirm the Foundry resource name used by clients matches the actual Foundry resource.
• Verify that the deployment name used by clients matches the claude-sonnet-4-6 deployment name in Foundry.
• If using Claude Code with Foundry:
  • Ensure CLAUDE_CODE_USE_FOUNDRY=1 is set so it uses Foundry rather than Anthropic’s public API.
  • Ensure ANTHROPIC_FOUNDRY_RESOURCE is set to the correct Foundry resource name.
  • Ensure ANTHROPIC_DEFAULT_*_MODEL values (for Sonnet/Haiku/Opus) match the actual deployment names.
• Run /status in Claude Code and confirm:
  • API provider: Microsoft Foundry
  • Foundry resource: the correct resource name
  • Model: the expected deployed model (for example, claude-sonnet-4-6).

If the model is not available or misconfigured, clients can see generic errors when trying to use it.

6. Check for authorization and tenant issues

Both admin and client environments should verify:

• Authentication method:
  • If using Azure AD/Entra ID: ensure az login has been run in the correct tenant that owns the Foundry resource.
  • If using API key: ensure ANTHROPIC_FOUNDRY_API_KEY is set correctly.
• Tenant alignment:
  • If an error like “Token tenant does not match resource tenant” appears, sign in with az login --tenant <tenant-id> for the tenant that owns the Foundry resource.
• Role assignments:
  • Ensure users and service principals have access to the Foundry resource (for example, Cognitive Services User plus Contributor/Owner as needed).

Authorization failures can surface as generic client-side errors even when quota is present.

7. Region and quota considerations

Even with approved quota, deployments can fail if:

• The model or deployment type is not actually available in the selected region at that moment.
• There is temporary capacity or quota enforcement behavior in Sweden Central.

If the portal or CLI shows errors related to region availability or quota, consider:

• Verifying that claude-sonnet-4-6 is listed as available in Sweden Central for the chosen deployment type.
• Requesting a quota adjustment or trying a deployment in East US2 (if policy allows) to confirm whether the issue is region-specific.

8. When to open or escalate a support ticket

Because the specific error code 715-123420 and the internal provisioning failure details are not exposed publicly, the next step is to open an Azure support ticket with:

• Subscription ID and region (Sweden Central).
• Foundry resource name and project details.
• Exact deployment name for claude-sonnet-4-6 and timestamps of failed attempts.
• Screenshots or logs showing ProvisioningFailed state and the client-side error code.

In the ticket, request:

• Backend log review for the failed Claude deployment in Sweden Central.
• Confirmation of subscription and Marketplace eligibility for Anthropic offers in the subscription’s billing region.
• Confirmation of any ongoing incident or capacity issue affecting Claude deployments in Sweden Central.

Support can then perform the backend investigation and apply any necessary fixes or configuration changes.

References:

• Deploy and use Claude models in Microsoft Foundry (preview)
• Configure Claude Code for Microsoft Foundry
• Foundry Models from partners and community