Azure subscription blocked after failed Claude Opus 5 deployments

Yurii Kuzin 0 Reputation points
2026-09-14T23:29:13.3166667+00:00

I am unable to deploy claude-opus-5 to Microsoft Foundry. The subscription appears to have entered a blocked state after several failed deployment attempts.

The sequence of events was:

I initially attempted to deploy claude-opus-5 using Terraform with azurerm. The deployment failed with:
InvalidModelProviderData

I then corrected the deployment configuration to provide the required Anthropic model provider data.

I attempted the deployment using Terraform/AzAPI. At that point, the deployment failed with:
InsufficientQuota

The quota was already being used because a colleague had previously deployed a Claude model manually through the Azure portal for research.

I deleted the sandbox resource group containing the previous model deployment and Foundry project in order to clean up the quota/resource state.

After cleanup, I attempted to deploy claude-opus-5 again. The deployment then failed with:
MarketplaceSubscriptionCannotBeCompleted

The error message specifically states:
"Unable to create a model deployment for model claude-opus-5. If the error persists, please contact HIT (Human Intelligence Team) ... and request to allowlist the Azure subscription."

I recreated the Foundry project using AzAPI and attempted the deployment again, but received the same MarketplaceSubscriptionCannotBeCompleted error.

Some subsequent attempts to delete/recreate the deployment resulted in:
RequestConflict: Another operation is in progress on the resource 'claude-opus-5'.

After several further attempts to recreate the project/deployment, deployment requests started failing with:
715-123420: Our system has detected this request as unusual activity for your account.

The current situation is that I cannot deploy claude-opus-5 even manually through the Azure portal.

I have already purged the previously deleted Azure AI/Foundry resources. I also verified that:

  • Microsoft.MarketplaceOrdering is registered.
  • Microsoft.SaaS is registered.
  • The Anthropic Marketplace agreement for azure-claude-offer is active.
  • Claude quota in the target region currently shows 0 usage.
  • The problem occurs through both Terraform/AzAPI and the Azure portal, so it does not appear to be specific to Terraform.

The current Activity Log errors are consistently:

MarketplaceSubscriptionCannotBeCompleted

and:

715-123420 - Our system has detected this request as unusual activity for your account.

Could someone please check whether the Azure subscription has been blocked, flagged, or otherwise restricted for Anthropic/Claude deployments and restore the subscription's eligibility?

Specifically, I would like to know what needs to be done to clear the 715-123420 / Marketplace restriction so that I can at least create a Claude deployment manually through the Azure portal again.

I am not looking for help with the Terraform configuration at this point. The same deployment fails through the Azure portal, CLI, AzAPI, and Terraform, so I believe the issue is now at the subscription/Marketplace/backend level.

Thank you.

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

0 comments

4 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Taz 9,531 Reputation points MVP Volunteer Moderator
    2026-09-15T07:04:50.77+00:00

    Hi Yurii,

    Since the same MarketplaceSubscriptionCannotBeCompleted error occurs from the portal, CLI, AzAPI, and Terraform, I would stop retrying the deployment for now. The later 715-123420 error also points away from Terraform and toward a Marketplace/account-level restriction.

    The key items for Azure Support to check are:

    • Whether the subscription is currently blocked or flagged for Anthropic Marketplace access.
    • Whether the azure-claude-offer SaaS/Marketplace subscription is in a healthy state.
    • Whether the subscription needs to be allowlisted for claude-opus-5.
    • Whether there is a stale Marketplace subscription or failed SaaS order associated with the deleted deployment.

    The InsufficientQuota issue should be separate from the later Marketplace errors. Also, deleting the resource group does not necessarily clear Marketplace/SaaS provisioning state immediately.

    I would open an Azure Support case under Azure AI Foundry / Marketplace and provide the exact Activity Log timestamps, correlation IDs, subscription ID, and the 715-123420 error. Ask them specifically to check and clear the Anthropic Marketplace subscription/provisioning state and any allowlist restriction.

    There isn't a customer-side command documented for removing a 715-123420 restriction, so recreating the project or repeatedly retrying the deployment is unlikely to resolve it.

    Was this answer helpful?

    0 comments
  2. Alex Burlachenko 25,285 Reputation points MVP Volunteer Moderator
    2026-09-15T07:06:58.75+00:00

    Hi Yurii Kuzin & thx for join me at Q&A platform,

    no longer looks like a Terraform, quota, or Foundry project configuration problem. The sequence of errors suggests the initial failures were separate issues, but the current failure is at the Marketplace/subscription eligibility layer.

    MarketplaceSubscriptionCannotBeCompleted is particularly important because the service itself tells you to contact the Human Intelligence Team and request subscription allowlisting. The later 715-123420 - unusual activity error is also consistent with an automated risk/abuse restriction being applied after the repeated provisioning attempts. Having an active Marketplace agreement, registered resource providers, and zero current Claude quota usage doesn't clear that type of restriction. Deleting or purging Foundry resources won't reset a Marketplace/risk flag associated with the subscription. I would also stop repeatedly creating and deleting the deployment for now. The RequestConflict errors are probably secondary pending-operation conflicts and additional retries won't resolve the eligibility restriction.

    At this point Microsoft needs to inspect the subscription's Anthropic/Claude eligibility and the 715-123420 risk decision. Ask the existing support case to be escalated specifically to the Foundry Models/Anthropic Marketplace team and the HIT team referenced in the error. Provide the subscription ID, exact UTC timestamps, correlation/request IDs and the complete MarketplaceSubscriptionCannotBeCompleted and 715-123420 responses privately.

    If the same deployment now fails through the portal as well as AzAPI/Terraform, there isn't a Terraform-side change that can restore it. The backend restriction or allowlist state has to be reviewed by Microsoft before Claude deployments can work again.

    rgds,

    Alex

    Was this answer helpful?

    0 comments
  3. Yurii Kuzin 0 Reputation points
    2026-09-17T14:43:32.17+00:00

    Existing support tickets are being closed and ignored without resolving the issue. After 48 hours I tried creating another Anthropic-based family of models, but got the same result.

    Was this answer helpful?

    0 comments
  4. Yurii Kuzin 0 Reputation points
    2026-09-17T14:43:54.8066667+00:00

    Existing support tickets are being closed and ignored without resolving the issue. After 48 hours I tried creating another Anthropic-based family of models, but got the same result.

    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.