InvalidModelProviderData when deploying Claude Sonnet 4.5 on Azure AI Foundry - UI missing required fields

Question

Hi Support Team,

TWO separate issues.

ISSUE 1 - PORTAL UI BUG:

When deploying claude-sonnet-4-5 via Azure AI Foundry portal

(ai.azure.com), the deployment form is MISSING required fields.

• Only the "Industry" dropdown is visible
• "organizationName" and "countryCode" fields are completely absent from the UI
• As a result, the "Agree and Proceed" button remains permanently DISABLED and cannot be clicked
• This appears to be a portal/UI bug where the form is incomplete

Steps to reproduce:

1. Go to ai.azure.com
2. Navigate to Models + endpoints
3. Click Deploy model → select claude-sonnet-4-5
4. Click "Agree and Proceed" tab
5. Only "Industry" field is shown — other required fields are missing
6. Button remains disabled regardless of industry selection

ISSUE 2 - REST API BACKEND ERROR:

When attempting deployment via REST API, the request is accepted but

fails on your backend:

Error:

{

"code": "AnthropicOrganizationCreationFailed",

"message": "Internal Server Error"

}

Resource: StemmaHealthdevAIFoundry

Region: East US 2

Model: claude-sonnet-4-5 (version 20250929)

Marketplace agreement: ACTIVE (signed 2026-04-29)

Quota: 2/450 (well within limits)

Billing: Active MCA with valid credit card

VERIFIED: -

• Active billing (Microsoft Customer Agreement)
• Valid credit card on file - eastus2 region (supported)
• Billing Account Owner role
• Tried api-versions 2024-10-01 and 2025-04-01-preview
• Tried inline JSON and @file approach

Thank you,

Muskan Vohra

Answer 1

We have tried ALL recommended approaches. Here is the complete summary:

APPROACH 1 - Portal UI (FAILED):

• Deployment form only shows "Industry" dropdown
• "organizationName" and "countryCode" fields are missing from UI
• "Agree and Proceed" button permanently disabled
• Cannot deploy via portal at all

APPROACH 2 - REST API with api-version 2025-04-01-preview (FAILED):

As per your team's recommendation, we tried api-version 2025-04-01-preview

with the following payload:

{

"sku": {"name": "GlobalStandard", "capacity": 1},

"properties": {

"model": {

  "format": "Anthropic",

  "name": "claude-sonnet-4-5",

  "version": "20250929"

},

"modelProviderData": {

  "industry": "Healthcare",

  "organizationName": "<org-name>",

  "countryCode": "US"

}

}

}

Error: InvalidModelProviderData - "ModelProviderData is required but

was not provided" — even though it IS in the request body.

This API version does not recognize the modelProviderData field at all.

APPROACH 3 - REST API with payload format suggested by your team (FAILED):

Tried the exact payload format your support team recommended:

{

"location": "eastus2",

"skuName": "claude-sonnet-4-5",

"properties": {

"modelId": "claude-sonnet-4-5",

"organizationName": "<org-name>",

"countryCode": "US"

}

}

Error: InvalidRequestContent - "The request content was invalid and

could not be deserialized."

This payload format is incorrect and not accepted by the API.

APPROACH 4 - REST API with api-version 2025-12-01 (PARTIALLY WORKED):

Using api-version 2025-12-01, the request was accepted and deployment

was created. However it then transitioned to provisioningState: Failed.

GET response confirming the failure:

{

"name": "claude-sonnet-4-5",

"properties": {

"deploymentState": "Running",

"provisioningState": "Failed",

"model": {

  "format": "Anthropic",

  "name": "claude-sonnet-4-5",

  "version": "20250929"

},

"modelProviderData": {

  "countryCode": "US",

  "industry": "Healthcare",

  "organizationName": "<org-name>"

}

}

}

RESOURCE DETAILS:

• Subscription:
• Resource Group: stemma-dev-rg
• Account: stemma-dev-aif
• Region: East US 2
• Deployment created: 2026-05-07T11:54:11Z

EVERYTHING VERIFIED ON OUR SIDE:

• Marketplace agreement: ACTIVE (signed 2026-04-29)
• Billing: Active MCA with valid credit card
• Region: East US 2 (supported)
• Quota: 2/450 (well within limits)
• modelProviderData: correctly formatted and accepted by 2025-12-01
• Permissions: Billing Account Owner role

CONCLUSION:

This is NOT a client-side issue. We have exhausted all options.

The failure is happening on the backend during Anthropic organization

registration (AnthropicOrganizationCreationFailed).

Note: The recommended api-version 2025-04-01-preview does NOT support

modelProviderData. Only 2025-12-01 accepts it correctly, but backend

provisioning still fails.

REQUEST - PLEASE ESCALATE:

1. Escalate to Azure AI Foundry + Anthropic engineering team
2. Manually complete Anthropic organization registration for our tenant/subscription
3. Fix the Portal UI missing fields bug
4. Provide an ETA for resolution

This is critically blocking our Healthcare AI application development.

We have been troubleshooting this for multiple days.