Why does my Claude deployment fail after Azure approved the quota?

November 16, 2026 3 answers
Asked by m.826+ferrycog

My Claude Opus 5.5 quota was approved in Azure Foundry, but deployment fails with MarketplaceSubscriptionCannotBeCompleted. The activity log says to contact Microsoft's HIT team and request subscription allowlisting.

Billing support directed me to technical support, but the Basic plan appears to block that request without an upgrade. What should I check, and is there a way to request allowlisting without paying for support?

Answers

d.482~mendrel

Quota approval and Marketplace purchasing are separate checks. Anthropic is a third party provider, and the deployment uses Azure Marketplace behind the scenes. Check that Marketplace purchases are enabled for the subscription and that the account creating the deployment has permission to make the purchase.

Also check the Foundry prerequisites for the model. If those are satisfied and the activity log still specifically requests allowlisting, include that error and the subscription details when asking Microsoft to investigate. The quota approval alone doesn't establish that the Marketplace step can complete.

v.527+canvasspool:

A subscription being enabled isn't quite the same thing as being authorized for Marketplace purchases, so that setting is worth checking separately.

Reply to this answer
_h49+drainwicket.6

The log points to an allowlisting request, but it doesn't establish whether the purchase setting is the only blocker or whether Microsoft needs to make a separate change. I'd send billing support the exact activity log error and ask them to route the subscription allowlisting request to the team named in it.

If you have an account team, try asking them to help route it too. There isn't a confirmed free path to HIT in the information here, so I wouldn't assume that either billing support or an account team can resolve it directly.

Reply to this answer
q.936!copperfob

If Azure hosting isn't a requirement, consider using Claude directly instead. That avoids this particular Marketplace provisioning step, though you'd need to check whether the direct service meets your billing and integration needs.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions