Azure for Students blocks Cosmos DB account creation with RequestDisallowedByAzure

Check the Allowed resource deployment regions policy assigned to your Azure for Students subscription, then create Cosmos DB by CLI in one of its listed standard regions rather than either EUAP region.

Find the regions assigned to your subscription

1. In the Azure portal, open Policy.
2. Select Authoring → Assignments.
3. Set the scope to your Azure for Students subscription.
4. Open Allowed resource deployment regions (it might instead appear as Allowed locations).
5. Under Parameters, inspect the Allowed locations value.

Azure for Students subscriptions commonly receive a subscription-specific list of permitted regions; therefore, there is no single region that works for every student subscription. This exact Cosmos DB symptom—only the two EUAP choices appearing while standard regions are blocked—has been resolved by checking that policy assignment first.^1^

Create the account in an allowed standard region

Choose a location that is both:

• Listed in the policy's Allowed locations parameter.
• Supported by the Cosmos DB creation experience.

Because the portal is presenting only EUAP locations, use Azure Cloud Shell or Azure CLI with the Azure region name from the policy. Replace <allowed-region> with its CLI name, such as westus, only if that exact region is in your policy:

resourceGroupName="cosmos-learning-rg"
location="<allowed-region>"
accountName="student-cosmos-$RANDOM"

az group create \
  --name "$resourceGroupName" \
  --location "$location"

az cosmosdb create \
  --resource-group "$resourceGroupName" \
  --name "$accountName" \
  --locations regionName="$location"

These are the documented commands for creating a resource group and an Azure Cosmos DB for NoSQL account.^2^

The resource group's location does not override the Cosmos DB account location—the Cosmos DB deployment itself must comply with the assigned policy.

If every allowed region still fails

Open the failed deployment and copy the policy assignment name/ID from its error details. A policy-denied deployment identifies the policy assignment and definition responsible for the block; those details distinguish the subscription policy from Cosmos DB regional availability.^3^

Then use Azure portal → Help + support → Create a support request and provide:

• Subscription: Azure for Students
• Resource type: Azure Cosmos DB for NoSQL
• Full RequestDisallowedByAzure error
• Policy assignment name/ID
• The allowed regions shown by the assignment
• The fact that none can provision a Cosmos DB account

If requesting access to a particular restricted region, select Service and subscription Limit (quotas) and follow the documented region-access request process.^4^ Approval depends on the subscription offer and regional capacity; it is not guaranteed.

You cannot solve a subscription-assigned location restriction merely by selecting another unlisted region or placing the resource group elsewhere. If no region is simultaneously allowed by the student policy and usable for Cosmos DB, Microsoft Support must adjust or clarify the subscription's permitted regions. This is the available path that does not require immediately converting to Pay-As-You-Go.

References

1. Azure for Students - Cosmos DB region restriction, only US regions available in portal - Microsoft Q&A
2. Create an Azure Cosmos DB for NoSQL account
3. Resolve errors for request disallowed by policy
4. Azure region access request process - Azure | Microsoft Learn