Incomplete 'ModelProviderData' input fields in Azure AI Foundry UI for Anthropic Claude Deployment

Question

claude fail.pdf

Unfortunately, the same issue persists even after following the exact steps you provided below.

• Issue: Claude model deployment fails in the Microsoft AI Foundry portal --> As a result, the Claude model provisioning cannot be completed.

The steps previously provided:

1. Open Azure Portal --> Search for "AI Foundry"

Create/select a Foundry project (supported regions: East US2 or Sweden Central)

1. Go to Model catalog --> Search for "Claude"
2. Select your model (e.g., claude-sonnet-4-8) --> Click Deploy
3. Choose Global Standard deployment --> Confirm

I have attached the screenshots capturing each step in chronological order:

step 1.jpg: Searching and accessing Microsoft Foundry in the Azure Portal.

step 2.jpg: Verifying the resource (dev-1141-resource) and region (eastus2).

step 3.png: Viewing the Deployments page in the Foundry portal where other models have successfully deployed.

step 4.jpg: Configuring the deployment settings for claude-opus-4-8 using the 'Global Standard' deployment type.

step 5.png: The final Deployments list showing that while other models (like GPT-5.5) succeeded, the claude-opus-4-8 deployment status explicitly shows "Failed".

Since this needs to be integrated into our company's shared internal automation pipeline, we cannot utilize localized or alternative standalone workarounds. Successful model provisioning is our highest priority right now, but we are completely blocked at the initial provisioning stage.

Please review this deployment failure and advise on a solution as soon as possible.

Answer 1

The deployment failure for claude-opus-4-8 in Azure AI Foundry aligns with a general class of provisioning issues where the API deployment for the resource never reaches a Succeeded state.

From similar issues, there are two practical, supported actions:

1. Delete and recreate the Claude deployment
   • In the Foundry portal, go to the Deployments page for the dev-1141-resource project.
   • Delete the failed claude-opus-4-8 deployment.
   • Wait a short period, then redeploy the same model (claude-opus-4-8) again using Global Standard in a supported region (East US2 or Sweden Central).
   • This pattern has resolved stuck/failed provisioning states for Claude and other managed resources where the portal reports that the deployment is not ready.
2. If repeated failures persist, switch to a fresh deployment instance
   • If the same deployment name continues to fail after recreation, create a new deployment with a different name for the same model in the same Foundry project and region.
   • Ensure the subscription and region meet the Claude requirements (Enterprise or MCA‑E subscription and supported region). If other models (like GPT‑5.5) deploy successfully in the same project, this isolates the issue to the specific Claude deployment instance.

If the deployment repeatedly fails even after delete/recreate, the next step is to open a support ticket with Azure, referencing the failed deployment ID and time window, so the platform team can inspect the backend provisioning logs for that specific Claude deployment.

---

References:

• Deploy and use Claude models in Microsoft Foundry (preview)
• How to deploy and infer with a managed compute deployment (classic) (ai-foundry-portal)
• Deployed Claude and getting API deployment resource is not ready even though it has been an hour - Microsoft Q&A ERR_BAD_REQUEST
• Stuck in Creating / Failed provisioning Redis Cache - Microsoft Q&A
• Azure Deployment Takes 70 Minutes to Fail with Obscure Error - Microsoft Q&A