Unable to deploy claude opus 4.5 model in foundry, getting Provisioning state : Failed

The error indicates a terminal provisioning failure without a detailed cause in the message. For Claude Opus 4.5 in Foundry, the main deployment prerequisites and common failure causes from the available information are:

1. Confirm region and project location
   • Claude models in Foundry are only supported in East US 2 and Sweden Central.
   • The Foundry project/hub itself must also be in one of these regions, not just the subscription or other resources.
   • Verify that the Foundry project/hub where the deployment is being created is in East US 2 (or Sweden Central). If it is in another region, create a new project/hub in East US 2 and deploy there.
2. Check subscription eligibility and marketplace constraints
   • Anthropic models are only available to subscriptions whose billing account is in a supported country/region (Microsoft-managed countries/regions except Belarus and Russia).
   • If the offer is not available for the subscription’s billing region, deployments can fail at provisioning time even if the marketplace agreement exists.
   • If the subscription is a CSP subscription, third‑party model offers (like Anthropic) are not supported; use a non‑CSP subscription or a first‑party model instead.
3. Handle marketplace/offer issues
   • Even with the agreement object present, Azure Marketplace can still reject the deployment request (for example, if the offer is not available in the subscription’s billing region, or if there have been too many subscription attempts for the offer).
   • In such cases, the deployment can fail with a generic internal error and terminal Failed state.
   • If this is suspected (especially after multiple attempts), open a support case and include the subscription ID so support can check the Marketplace side.
4. Retry deployment after failure
   • There are known cases where a Foundry model deployment gets stuck or fails with a generic provisioning error and later succeeds when recreated.
   • Delete the failed deployment from the Foundry portal once it is in Failed state, then:
     • Re‑attempt the deployment in the same project/hub if all prerequisites above are satisfied, or
     • Create a new deployment in a new Foundry project/hub in East US 2 and try again.
5. If the deployment remains failing
   • After confirming:
     • Foundry project/hub region is East US 2 or Sweden Central.
     • Subscription billing region is supported for Anthropic offers.
     • Subscription is not CSP.
     • Required resource providers are registered and the marketplace agreement is active.
   • Then the remaining step is to contact Azure support with:
     • Subscription ID
     • Foundry project/hub region
     • Model offer/plan IDs
     • Deployment name and timestamp of failure
   • Marketplace or backend deployment issues (quota, internal errors) can then be checked and resolved by support.

References:

• Deploy and use Claude models in Microsoft Foundry (preview)
• Configure Claude Code for Microsoft Foundry
• Foundry Models from partners and community
• Region availability for models in standard deployments
• How to troubleshoot your deployments and monitors in Microsoft Foundry portal (classic)
• How to deploy and infer with a managed compute deployment (classic) (python-sdk)
• Region availability for models in serverless APIs (classic)
• Deployed Claude and getting API deployment resource is not ready even though it has been an hour - Microsoft Q&A
• Azure Deployment Takes 70 Minutes to Fail with Obscure Error - Microsoft Q&A