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
Open an Azure support request for a subscription-specific Marketplace/HIT allowlisting review, because MarketplaceSubscriptionCannotBeCompleted with an explicit allowlisting message has no documented self-service allowlist operation. The matching Opus 5.5 case identifies Microsoft support review as the required escalation path.^1^
Submit the support request
In Azure portal → Help + support → Create a support request, select the affected subscription and use:
- Service: Microsoft Foundry or Cognitive Services
- Problem type: Deployment and setup / Model deployments
- Summary:
Claude Opus 5.5 MarketplaceSubscriptionCannotBeCompleted — subscription allowlisting requested - Ask support to:
- Review the subscription’s Marketplace purchase eligibility for the specific
claude-opus-5-5offer/SKU. - Perform the requested HIT/allowlisting review.
- Confirm whether the offer is enabled for the subscription’s billing market.
- Review the subscription’s Marketplace purchase eligibility for the specific
Attach:
- Full error text and
MarketplaceSubscriptionCannotBeCompleted. - Subscription ID, tenant ID, Foundry resource name, resource group, and deployment region/scope.
- Deployment name and model/version: Claude Opus 5.5, Hosted on Azure.
- Failure timestamp in UTC.
- The failed deployment’s operation/correlation ID from Azure portal → Monitor → Activity log.
- Screenshot or exported JSON of the failed operation.
- Note that Claude Opus 4.8 and Opus 5 deploy successfully on the same resource.
Do not repeatedly recreate the deployment while the review is pending. Azure Marketplace can reject model-subscription creation after repeated or simultaneous subscription attempts; Microsoft’s guidance for that condition is to contact support and include the subscription ID.^2^
Check eligibility before submitting
Opus 5.5 Hosted on Azure is documented as GA and supports Global Standard; Data Zone Standard (US) is also supported for this model.^3^ However, visibility and successful deployment of older Claude SKUs do not establish Marketplace eligibility for every newer SKU.
Record the results of these checks in the ticket:
- The subscription has an active pay-as-you-go payment method.
- Its billing country/region is supported by Anthropic.
- It is not:
- A CSP subscription
- A credit-only sponsored subscription
- A student, free-trial, or startup credit-based subscription
- An Enterprise Account located in South Korea
- Azure Marketplace purchases are permitted by the billing account and tenant.
- If Private Marketplace is enabled, the Opus 5.5 offer/plan is approved.
These are documented Claude prerequisites.^4^ Marketplace validation can also fail when the offer is unavailable in the billing market, there is no valid payment instrument, EA Marketplace purchasing is disabled, Private Marketplace blocks the offer, or a private/preview offer has not allowlisted the subscription.^5^
If one of those checks fails, correct that condition instead of requesting allowlisting—for example, have the Marketplace administrator approve the plan or use an eligible subscription associated with a supported billing market. Marketplace purchase requirements and corresponding remedies are listed in the SaaS purchase troubleshooting table.^6^
If all checks pass, the explicit allowlisting message plus the fact that only Opus 5.5 fails makes the support review the appropriate next action; changing SDK parameters, permissions, or repeatedly retrying the same deployment is unlikely to resolve a subscription-level Marketplace entitlement decision.
References