Subscription management | Region access

Azure for Students subscriptions are often restricted by region access policies, including “Allowed resource deployment regions.” When Foundry-supported regions are blocked by such a policy, there are only two supported paths:

1. Verify which regions are allowed for the subscription
   • Use the Azure portal or Azure Policy assignments to see which regions are permitted by the Allowed resource deployment regions policy.
   • Compare that list with the Foundry project regions list. Foundry projects can currently be created only in these regions:
     • Australia East
     • Brazil South
     • Canada Central
     • Canada East
     • Central India
     • Central US
     • East Asia
     • East US
     • East US 2
     • France Central
     • Germany West Central
     • Italy North
     • Japan East
     • Korea Central
     • North Central US
     • North Europe
     • Norway East
     • Qatar Central
     • South Africa North
     • South Central US
     • South India
     • Southeast Asia
     • Spain Central
     • Sweden Central
     • Switzerland North
     • UAE North
     • UK South
     • West Europe
     • West US
     • West US 3
     • US Gov Virginia
     • US Gov Arizona
   • If at least one of these regions is already allowed by the policy, create the Foundry project in that region.
2. If no Foundry region is allowed, request region access change
   • Because the subscription is constrained by a region policy, a support request is required to change region access.
   • In the Azure portal, go to Help + support → Create a new support request.
   • Use the region access/quota flow described in the region access articles:
     • For general region access issues, follow the Azure region access request process:
       • Issue type: Service and subscription limits (quotas).
       • Subscription: select the Azure for Students subscription.
       • Quota type: Compute-VM (core-vCPUs) subscription limit increases (or the region-access option shown for the subscription).
       • In the problem details, specify that the subscription is restricted by Allowed resource deployment regions and explicitly request enabling one or more Foundry-supported regions (for example, “Request access to East US 2 for Microsoft Foundry projects”).
     • If the portal shows a “location ineligible” or “you can create resources in the following regions only” message, use the remediation path in the location-ineligible guidance to open a region access support case and state the business/learning need for Foundry.
3. If support cannot change regions for Azure for Students
   • Some subscription types (including student/free/trial) can be limited in which regions or services are available.
   • If support confirms that region access cannot be changed for the Azure for Students subscription, the only supported workaround is to use a different subscription type (for example, a paid subscription) that is allowed to deploy to one of the Foundry project regions.
4. Before creating Foundry resources after region access is granted
   • Confirm that the chosen region is valid for Foundry projects using the Foundry region list.
   • For specific features or models (for example, partner models like Claude), also verify feature-specific region support and quota in the Foundry portal under Operate → Quota.

---

References:

• Azure region access request process
• Microsoft Foundry feature availability across cloud regions
• Region optimization for Microsoft Azure customers
• Resolve location ineligible errors
• Deploy and use Claude models in Microsoft Foundry (preview)

AI-generated content may be incorrect. Read our transparency notes for more information.