Share via

Quota Request Escalation: Anthropic Claude 3.5 Sonnet / Opus in East US 2 - 9 Days No Response

Jeff Kovnick 0 Reputation points
2026-03-17T20:01:39.8133333+00:00

Hello, I am a forensic physician and I am requesting an escalation for a Claude 3.5 Sonnet and Opus quota request in the East US 2 region. It has been 9 days since my initial inquiry without a status update.I am using Microsoft Foundry for professional medical record analysis and forensic reporting. I require access to these models via Global Standard deployment.

Account Details:

Project Name: Forensic-analysis

Hub Name: Kovnick-MD-Lab

Subscription Type: Pay-As-You-Go (Active Credit Card)

Region: East US 2

Desired Models: Claude 3.5 Sonnet / Claude 3 Opus

My quota is currently locked at 0. Could a moderator please check if this request is stuck in a manual review or if there is a regional capacity constraint I should be aware of? Thank you.

Community Center | Not monitored

1 answer

Sort by: Most helpful
  1. Q&A Assist
    2026-03-17T20:02:07.5466667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    Quota for Anthropic Claude models in Microsoft Foundry is controlled per subscription, per region, and per model in Tokens-per-Minute (TPM). For Claude Opus and Sonnet in East US 2, Enterprise and MCA-E subscriptions are explicitly eligible; Pay-As-You-Go subscriptions are not listed as eligible for Claude usage in Foundry. When quota is 0 TPM for these models, deployments and inference through Global Standard can’t proceed until quota is granted.

    From the available information, the only supported actions are:

    1. Confirm subscription eligibility and region
      • Claude models in Foundry currently:
        • Require an Enterprise or MCA-E subscription for usage.
        • Are available only in East US 2 and Sweden Central.
      • With a Pay-As-You-Go subscription, quota for Claude models can remain at 0 and requests may not be approved because the subscription type is not in the eligible set.
    2. Verify that the request was submitted through the correct channel
      • Quota for Foundry Models (including Anthropic models) is managed via the quota increase request form: https://aka.ms/oai/stuquotarequest.
      • If the Quota page in the Foundry portal shows 0 TPM and no allocations, ensure the account has at least Cognitive Services Usages Reader at the subscription level and that the correct subscription is selected.
      • If the Request quota button is disabled, verify that the account has Owner or Contributor on the subscription.
    3. Understand likely reasons for delay or no change
      • For Claude models, a “Subscription eligibility error” occurs when the subscription is non‑Enterprise or non‑MCA‑E. In such cases, quota remains at 0 and deployments cannot be created, regardless of elapsed time.
      • There is no documented SLA for manual quota review in the provided material; however, if a request is pending for many days with no change and the subscription is Pay-As-You-Go, the most probable cause is ineligibility rather than a stuck review.
    4. Practical next steps
      • Confirm in the Foundry portal that the Claude models are visible for East US 2 and that the project/hub region is East US 2 (required for Claude standard deployments).
      • Verify roles:
        • Owner or Contributor on the subscription to request quota.
        • Cognitive Services Usages Reader to view quotas.
      • If the quota request was submitted correctly and the subscription is Pay-As-You-Go, consider:
        • Working with the organization’s Azure administrator or account team to move workloads to an eligible Enterprise or MCA‑E subscription if Claude access is required.
        • Using other models that are available and have non‑zero default quota in the current subscription and region, as listed in the Foundry Models quotas and limits documentation.
      • If the quota page remains empty or unchanged after confirming roles and region, and more than 24 hours have passed since any approved change, the documented path is to contact Azure support via the standard support options.

    Direct moderator or engineering escalation, and internal status of a specific quota request, are not exposed in the referenced material. The documented mechanisms are the quota request form, role/region verification, and Azure support for unresolved quota issues.


    References:

    0 comments No 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.