Hello @Winston Martinez
The important distinction here is that Global Standard quota is increasingly managed at the subscription/model level rather than by selecting an individual region. Models onboarded to subscription-level quota management use one Global Standard quota pool across regions.
So the rejection message telling you to “expand your regional choices” does appear confusing when the quota request form for that model/deployment type doesn't expose a region field.
However, Microsoft Q&A/community members cannot grant TPM quota. Quota increases depend on Microsoft's available capacity and subscription eligibility, and Microsoft notes that requests can be denied based on capacity and existing quota usage.
Since your subscription currently shows 0 TPM across multiple Azure OpenAI and Anthropic models, rather than just one constrained model, open an Azure Support request for Microsoft Foundry quota/subscription eligibility and ask them to review whether the subscription is eligible for an initial allocation. Include the rejected quota-request details and explain that the form provides no region selector despite the regional-capacity rejection.
Also check Foundry → Manage → Quota and verify the Scope shown for the affected models. Global indicates subscription-level Global Standard quota, while a named region indicates regional quota management.
Reference: Manage Foundry quota
Avoid resubmitting the same quota form repeatedly. Microsoft needs to review the underlying 0-quota subscription state, especially since the same rejection is occurring across multiple model families.
Help make this community better for everyone: if this answer resolved your issue, please accept it or upvote it. If not, share more details in a comment so we can continue the discussion and find the right solution.