Azure AI Foundry: Unable to Provision Anthropic Models Due to Marketplace Failure — Region and Subscription Eligibility Checks

Artem-2045 5 Reputation points
2026-10-27T07:56:18.3733333+00:00

Problem description

I am experiencing issues when trying to provision any Anthropic model in my Azure AI Foundry environment. The deployment fails during the create/update of the model deployment resource, and the error message suggests I contact support to be added to an allow list. This failure occurs across multiple Anthropic models and seems related to a marketplace provisioning failure.

Environment

Azure AI Foundry with Anthropic model deployments, in West US 3 region, using Terraform for deployment, with separate development and production environments/subscriptions. The deployment was attempted in the West US 3 region, with the latest API version 2025-10-01-preview.

What I've already tried

I have attempted deployment with multiple Anthropic models, and the failure persists. I verified that the same Terraform deployment works in my development environment, but fails in production. I confirmed that my quota is sufficient for the models tested, and I have made sure that the deployment was attempted from both West US 3 and East US 2 regions to rule out regional issues. Additionally, I confirmed that the Terraform/Bicep deployment path is not currently supported for Anthropic models in Azure AI Foundry, and I have manually deployed in the portal without success.

Current status

Currently, the deployment continues to fail with the same marketplace/allow-list style provisioning error in production, while similar deployments succeed in development. I seek assistance to verify whether my account or subscription is blocked or not eligible for Anthropic deployment in the current region, and to understand the region and subscription eligibility requirements to resolve this provisioning failure.

Foundry Models
Foundry Models

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

3 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  2. Hemant Bharadwaj 340 Reputation points Microsoft Employee
    2026-10-28T06:08:05.35+00:00

    Likely cause: this dev-vs-prod difference usually points to subscription entitlement/policy or region capacity constraints for that model family, not just Terraform/Bicep syntax.

    1. Validate model availability in the target region.
    2. Confirm the specific Anthropic model is deployable in West US 3 (and your fallback region) for your subscription.
    3. Validate region-scoped quota for production subscription.
    4. Check the exact model-family quota/TPM in the production subscription (not only dev), and verify requested capacity matches available quota.
    5. Confirm subscription authorization prerequisites.
    6. Ensure marketplace purchasing/terms and required permissions are enabled for the production subscription/tenant.
    7. Re-test with a minimal deployment.
    8. Try one minimal model deployment (single model, baseline capacity) to separate entitlement/policy issues from IaC orchestration complexity.
    9. Escalate with full correlation data if still blocked.
    10. Include operation IDs, timestamp, subscription ID, model name, region, and deployment mode so support can verify backend allow-list/entitlement checks.

    Validation checks

    Was this answer helpful?

    0 comments
  3. Sai Kiran Mudavath 345 Reputation points Microsoft External Staff Moderator
    2026-10-28T13:57:28.85+00:00

    Hi @Artem-2045 ,

    Thank you for your patience while we investigated this issue.

    The associated Microsoft support case confirmed that the MarketplaceSubscriptionCannotBeCompleted error was caused by an account-level security restriction affecting the Azure subscription. The deployment activity was incorrectly identified as suspicious, which prevented the Azure Marketplace transaction required to deploy Anthropic models.

    The relevant team reviewed and reinstated the subscription, and the restriction has now been removed. This issue was therefore not caused by Terraform, the selected region, available quota, DNS configuration, or a specific Anthropic model.

    Please retry the Anthropic model deployment. If you continue to experience the issue, please share the latest error details and UTC timestamp so that we can investigate further.

    If this answers your query, please click Accept Answer and select Yes for Was this answer helpful? This can help other community members who encounter a similar issue.

    If you have any further questions, please let us know.

    Thank you!

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.