Claude Opus 4.7 MaaS deployment in Foundry fails provisioning after quota is reserved

Hello @Josh H,

Thank you for reaching out. I understand how frustrating it can be when the deployment reserves quota successfully, only to fail during provisioning with a generic error.

Based on the details you provided, your Azure AI Foundry configuration appears to be largely correct. Since quota is successfully reserved and the deployment process starts, this confirms that:

• Your subscription has been granted access to Claude Opus 4.7
• Quota is correctly allocated
• Required resource providers (Microsoft.SaaS and Microsoft.Marketplace) are registered
• Your permissions are sufficient to initiate deployment

However, the fact that provisioning fails after several minutes and no Microsoft.SaaS resource is created strongly suggests the issue is occurring during the Azure Marketplace SaaS fulfillment process.

Root Cause

Anthropic MaaS models, including Claude Opus 4.7, require a successful Azure Marketplace subscription handshake before the deployment can complete.

In some cases:

• Quota is visible and can be reserved
• Deployment creation is allowed
• Provisioning begins

but the deployment ultimately fails if the Marketplace offer has not been fully subscribed to, accepted, or fulfilled for your subscription.

This is why you may see quota reserved, yet no underlying SaaS resource gets created.

Recommended Steps

1. Confirm Marketplace Subscription to the Anthropic Offer

Please verify that you have explicitly subscribed to the Anthropic Marketplace offer.

In the Azure portal:

• Go to Azure Marketplace
• Search for Anthropic Claude Opus 4.7
• Select the offer
• Click Subscribe
• Review and accept the legal terms

This step is required before Azure AI Foundry can provision the underlying Microsoft.SaaS resource.

2. Verify Subscription Eligibility

Anthropic MaaS models are supported only on eligible subscription types, including:

• Pay-As-You-Go
• Enterprise Agreement (EA)
• Microsoft Customer Agreement (MCA-E)

They are generally not supported on:

• Free Trial subscriptions
• Azure for Students
• Credit-only subscriptions
• Some CSP-managed subscriptions

Please also ensure that:

• A valid payment method is associated with the subscription
• Your billing profile is active
• Marketplace purchases are enabled

You can verify Marketplace purchase settings under:

Subscriptions → Your Subscription → Policies

3. Re-register Required Resource Providers

Although both providers are already registered, refreshing the registrations can sometimes resolve Marketplace fulfillment issues.

Using Azure CLI:

az provider unregister --namespace Microsoft.SaaS

After re-registering, allow approximately 5–10 minutes for the changes to propagate.

4. Review Activity Logs for Detailed Errors

In the Azure portal:

• Navigate to the resource group used for the deployment
• Open Activity Log
• Filter by Status = Failed

Look specifically for failed operations related to:

• Microsoft.SaaS
• Marketplace fulfillment
• Purchase authorization
• Billing validation

These logs often contain more detailed error codes than the deployment blade.

5. Verify Deployment Configuration

Please confirm:

• The deployment region is East US 2
• Your Azure AI Foundry project is associated with the same subscription and resource group
• Your account has Owner or Contributor access at both:
  • Subscription/resource group scope
    • Azure AI Foundry project scope

A Microsoft.SaaS resource is created automatically during successful provisioning.

No manual creation of this resource is required.

Since no SaaS resource appears, the failure is almost certainly occurring before Marketplace fulfillment completes.

Please refer this

Deploy and use Claude models in Microsoft Foundry (preview): https://learn.microsoft.com/azure/foundry/foundry-models/how-to/use-foundry-models-claude

Subscription types & region support: https://learn.microsoft.com/azure/foundry/foundry-models/how-to/use-foundry-models-claude#prerequisites

Common Marketplace SaaS purchase errors: https://learn.microsoft.com/en-us/marketplace/purchase-saas-offer-in-azure-portal#common-error-messages-and-solutions

I Hope this helps. Do let me know if you have any further queries.

If this answers your query, please do click Accept Answer and Yes for was this answer helpful.

Thank you!

Claude Opus 4.7 is a Claude model from a partner (Anthropic) and is subject to the same Marketplace and regional/eligibility constraints as other partner models in Foundry.

From the available information, the behavior described (quota visible and reserved, deployment allowed to start, then failing with a generic provisioning error) is consistent with underlying Marketplace or regional eligibility issues that are not surfaced clearly in the error message.

Based on the documented patterns for partner models and Foundry deployments, the following checks and steps are supported:

1. Confirm subscription eligibility and model/region availability
   • Partner models can fail deployment if the offer or SKU is not available for the subscription’s billing country/region or the selected Azure region.
   • For partner models, errors such as:
     • “Offer not available in your country/region”
     • “Marketplace purchase eligibility check failed”
     • “Unable to create a model deployment”
     • “CSP subscription not supported” indicate Marketplace or regional eligibility problems.
   • Even if quota is visible, the Marketplace offer for a specific SKU (such as a MaaS variant) may not be available for the subscription or region.
   • Action: Verify that the specific Claude Opus 4.7 MaaS SKU is available for the subscription’s billing country/region and for the East US 2 region. If not, use a subscription with billing in a supported country/region or a supported region for that SKU.
2. Check for Marketplace subscription/permissions issues
   • Partner model deployments can fail if Azure Marketplace rejects the model subscription request, including cases where:
     • The model offering has been subscribed to too often or from multiple subscriptions at the same time.
     • The subscription type is not supported (for example, CSP subscriptions cannot purchase third‑party model offerings).
   • For Foundry Models, Marketplace-related issues are explicitly called out as:
     • “Marketplace subscription error” when required permissions or Marketplace configuration are missing.
   • Action:
     • Ensure the subscription is not a CSP subscription if using a third‑party MaaS model.
     • Verify Marketplace access and permissions as described in the Foundry Models documentation (Owner/Contributor on the subscription and Marketplace enabled for the tenant/subscription).
3. Validate quota and region from the Foundry side
   • Quota being visible and reserved indicates that Foundry quota is configured, but deployments can still fail if:
     • The model is not actually available in the selected region for that deployment type.
     • Provisioned capacity or deployment type constraints exist behind the scenes.
   • The documented guidance for deployment failures includes:
     • “Deployment status shows Failed – Confirm that the model is available in your selected region and that you have sufficient quota.”
     • “Region unavailable – Model not deployed in selected region – Select a region from the model’s availability list.”
   • Action:
     • Re‑check the model’s regional availability list for the specific Claude Opus 4.7 MaaS SKU and confirm East US 2 is supported for that SKU and deployment type (GlobalStandard).
     • If possible, attempt deployment in the other supported Claude region (for Claude models generally, East US 2 and Sweden Central are the supported regions) to see if the failure is region‑specific.
4. Handle stuck/failed deployments and quota
   • For other Foundry/partner scenarios, users have resolved similar “deployment failed” or “resource not ready” issues by:
     • Deleting the failed deployment and recreating it later.
     • Switching to a different region where the model is known to be available.
   • Action:
     • Delete the failed deployment so that reserved quota is released.
     • Recreate the deployment, optionally in the alternate supported region, after confirming Marketplace and regional eligibility.
5. When to contact support
   • If Marketplace eligibility and region support are confirmed and the deployment still fails with only a generic InternalServerError, the documented guidance for partner models is to contact support and include the subscription ID when Azure Marketplace rejects the request to create a model subscription.
   • Action:
     • Open an Azure support request, reference that this is a partner model (Anthropic Claude Opus 4.7 MaaS) deployment in Foundry, and include the subscription ID and region details so Marketplace/Foundry can check backend eligibility and offer configuration.

There is no additional user‑visible “manual” Marketplace purchase step documented beyond having Marketplace enabled, correct permissions, and a supported subscription/region. When those conditions are met, the Foundry deployment flow should automatically create the necessary Marketplace subscription; if it cannot, it surfaces as the kind of generic failure described and must be resolved via eligibility/region checks or Azure support.

References:

• Foundry Models from partners and community
• Deploy Microsoft Foundry Models in the Foundry portal
• Deployment types for Microsoft Foundry Models
• Manage and increase quotas for resources with Microsoft Foundry (Foundry projects)
• Configure Claude Code for Microsoft Foundry
• Deploy and use Claude models in Microsoft Foundry (preview)