A catalog of AI models in Microsoft Foundry that you can discover, compare, and deploy using Azure’s built‑in tools for evaluation, fine‑tuning, and inference
The error indicates a portal-side or backend issue with Anthropic model deployment metadata rather than a configuration problem in the project/hub itself.
For Anthropic Claude deployments in Microsoft Foundry / Foundry Models, the required provider metadata (ModelProviderData such as industry, organizationName, countryCode) is part of the marketplace/partner model wiring. When this data is missing or not correctly surfaced, deployments can fail even before provisioning. The context documents show that partner/marketplace issues are handled as platform-side problems rather than something that can be fixed from the project configuration:
- Partner/marketplace models can fail deployment due to offer/region/marketplace wiring issues, and the guidance is to contact support when the platform rejects the deployment request (for example, "Unable to create a model deployment" where Azure Marketplace rejects the request and support must intervene).
- Claude models in Foundry are treated as partner models and have specific deployment constraints (for example, region limitations and marketplace access requirements).
Given that:
- The portal UI for the Anthropic deployment blade is not exposing the required
ModelProviderDatafields. - The error is thrown immediately at validation time, before any quota, compute, or environment provisioning steps.
- The missing fields are part of the marketplace/provider metadata, not something configurable elsewhere in the project.
The issue cannot be resolved from the Foundry project/hub side. It requires platform-side remediation.
Recommended actions based on the available guidance for partner models and Claude in Foundry:
- Treat this as a partner/marketplace deployment failure
- The behavior matches the class of errors described for partner models where Azure Marketplace rejects or cannot complete the subscription/fulfillment for the model offering.
- In similar partner-model cases, the documented resolution is to open a support request and include the subscription details so the backend configuration can be corrected.
- Open an Azure support ticket for the affected subscription(s)
- In the ticket, include:
- Subscription ID(s) and Foundry resource name(s) where
claude-opus-4-8is being deployed. - Project/hub names (for example,
cedex-test-0334,dev-1141). - Exact error text:
ModelProviderData is required for Anthropic model deployments but was not provided. Please provide all required fields: industry, organizationName, and countryCode. - Screenshots or description showing that the deployment blade for
claude-opus-4-8(Global Standard) does not exposeorganizationNameandcountryCodefields.
- Subscription ID(s) and Foundry resource name(s) where
- Ask support explicitly to:
- Verify the marketplace subscription/fulfillment status for the Anthropic offer on the subscription.
- Confirm that the
ModelProviderDataschema for Anthropic on the backend is correctly configured for your tenant/region. - Escalate to the Foundry/AI Foundry and Marketplace engineering teams as a UI + backend validation bug for Anthropic Claude Global Standard deployments.
- In the ticket, include:
- Validate other known Anthropic/partner prerequisites while waiting on support
- Confirm the deployment region is supported for Claude models (for example, Claude models are only available in specific regions such as East US 2 and Sweden Central). If the Foundry resource is in an unsupported region, deployments can fail in non-obvious ways.
- Ensure Azure Marketplace access is enabled for the subscription and that partner model offers are allowed. For partner models, marketplace access and regional availability are prerequisites.
- If support confirms a backend/UI bug
- The likely remediation will be either:
- A portal fix to surface the missing
ModelProviderDatafields, or - A backend change to default or pre-populate the required metadata based on marketplace subscription data for the Anthropic offer.
- A portal fix to surface the missing
- After the fix is applied, retry the
claude-opus-4-8Global Standard deployment from the portal and verify that either:- The missing fields now appear and can be filled, or
- The deployment proceeds without the previous validation error.
- The likely remediation will be either:
Because the missing ModelProviderData fields are not exposed anywhere else in the Foundry UI and are required by the Anthropic provider integration, this scenario must be handled by Azure support and engineering as a platform defect rather than a configuration issue in the project.
References: