A unified Azure platform for creating and managing AI models, agents, and applications with built‑in enterprise security, monitoring, and governance
Open an Azure Marketplace support request and explicitly request escalation to the Foundry Models/Anthropic Marketplace team and Human Intelligence Team (HIT) for subscription eligibility review and allowlisting; Microsoft Learn Q&A cannot access or modify subscription entitlements.
Submit the escalation
- In the Azure portal, open Help + Support → Create a support request.
- Select:
- Issue type: Billing or Subscription management
- Problem type: Marketplace
- Problem subtype: the closest option for a failed Marketplace subscription, purchase, or activation
- Use a title such as:
Anthropic Claude deployment blocked — MarketplaceSubscriptionCannotBeCompleted — HIT allowlisting required
- Include this request:
Deployments of
claude-sonnet-5andclaude-opus-5fail withMarketplaceSubscriptionCannotBeCompleted. The Activity Log explicitly directs us to contact HIT for Azure subscription allowlisting. Please verify this subscription’s eligibility for the Anthropic Claude Marketplace offers and escalate the case to the Foundry Models/Anthropic Marketplace team and Human Intelligence Team (HIT) for entitlement review and allowlisting.The associated quota-increase request was rejected because regional capacity was unavailable. Please treat that as a separate capacity outcome rather than closing this Marketplace eligibility case as a quota request.
- Provide these details privately in the support case:
- Azure subscription ID and tenant ID
-
claude-sonnet-5andclaude-opus-5 - Foundry resource/project name and deployment region
- Subscription offer/billing type and billing country/region
- Exact UTC timestamp of the latest failed attempt
- The correlation ID already captured
- Complete Activity Log JSON and error text
- Screenshot of the failed deployment, if available
- Confirmation of whether the Marketplace terms were accepted
A closely matching Claude Marketplace case instructs customers to request escalation to Marketplace/HIT and provide the subscription ID, region, correlation ID, and timestamp.^2^ Correlation IDs let support trace a request across Azure services.^3^
Eligibility that support must validate
Eligibility cannot be confirmed from the error or correlation ID alone. Claude requires:
- A paid Azure subscription with an active payment method.
- A billing account in a country or region where Anthropic offers the model.
- Azure Marketplace access.
- A supported subscription type.
Currently unsupported types include CSP subscriptions, Enterprise Accounts in South Korea, subscriptions without active pay-as-you-go billing such as student/free-trial/startup-credit accounts, and sponsored subscriptions using only Azure credits.^4^
If any unsupported condition applies, HIT allowlisting is not established as a way to override it; use an eligible paid subscription instead.
Conditional checks before support responds
These checks do not replace the HIT review, but they can prevent the case from being redirected:
- Permissions: Azure portal → Subscriptions → affected subscription → Access control (IAM) → Check access. Confirm Owner or Contributor at subscription scope. Partner-model subscription requires Marketplace agreement and SaaS resource actions; these built-in roles contain the documented permissions.^5^
- Marketplace controls: Have the billing or Marketplace administrator verify that paid Marketplace purchases are enabled and that Azure Policy does not deny
Microsoft.SaaSorMicrosoft.Marketplace. - Billing profile: For an MCA billing account, verify Cost Management + Billing → billing account/profile → Properties has complete legal organization and sold-to address information. The matching escalation case identifies incomplete billing metadata as a Marketplace rejection condition.^2^
Do not repeatedly recreate the deployment while the eligibility review is pending. A matching MarketplaceSubscriptionCannotBeCompleted case reports that project recreation does not clear a subscription/Marketplace restriction and recommends backend review instead.^6^
The rejected quota request remains a separate blocker: even after Marketplace eligibility is restored, deployment may still require available capacity in a supported scope. Anthropic quota increases are supported, but requests are capacity-dependent.^7^
References
- How to get support for Microsoft Marketplace
- Azure AI Foundry: Cannot Deploy Anthropic Claude Models — Marketplace ...
- Get operation correlation ID from Activity Log for Microsoft Discovery
- Deploy and use Claude models in Microsoft Foundry
- Foundry Models from partners and community
- Azure subscription blocked after failed Claude Opus 5 deployments
- Azure OpenAI in Microsoft Foundry Models quotas and limits