Not able to deploy resources in East US, west US and a few indian servers.

For an Azure for Students subscription, failures to deploy resources in specific regions (East US, West US, some India regions) with messages about the region or SKU not being available are typically due to:

• Region access restrictions for that subscription
• SKU (VM size or service SKU) not being available in that region for that subscription
• Regional quota set to 0 for certain resource families

Use the following steps to work around and diagnose the issue.

1. Try an alternative region
   • For each resource, select a different Azure region that is supported for that resource type and for the subscription.
   • For Function Apps and similar services, guidance is to use a geographically paired region when a region is blocked or has quota 0. For example, if one India region is blocked, try its paired region if available.
   • In many cases, simply switching to another region resolves the deployment failure.
2. Check whether the resource type is allowed in the region
   • Some resource types are not available in all regions or may be blocked for a given subscription.
   • With Azure CLI, check supported locations for the resource type, for example for Azure Batch accounts:

          az provider show \
            --namespace Microsoft.Batch \
            --query "resourceTypes[?resourceType=='batchAccounts'].locations | [0]" \
            --out table
     

   • With Azure PowerShell:

          ((Get-AzResourceProvider -ProviderNamespace Microsoft.Batch).ResourceTypes |
            Where-Object ResourceTypeName -eq batchAccounts).Locations
     

   • If the region you are trying to use is not listed, that resource type cannot be deployed there.
3. Check SKU/size availability in the region
   • For VM-based services, the error can be SkuNotAvailable when the chosen VM size is not available in that region or zone for the subscription.
   • Use PowerShell to list available compute SKUs in a region (example for centralus; replace with your target region):

          Get-AzComputeResourceSku |
            Where-Object {
              $_.Locations -contains "eastus" -and
              $_.LocationInfo.Zones -ne $null -and
              $_.ResourceType -eq "virtualmachines"
            }
     

   • In the Azure portal, start creating a VM in the target region and use the Size picker → See all sizes to see which VM sizes are actually available to the subscription in that region. Choose one of those sizes.
4. Handle region access / ineligible region errors
   • If the error code is RegionDoesNotAllowProvisioning or the message states that the subscription does not have access to create resources in that region, there are two options:
     • Select a different region and redeploy.
     • If there is a clear business requirement to use that region (for example, data residency), submit a Region access quota/support request:
       1. In the Azure portal, create a new support request.
       2. For the problem type, choose Service and subscription limits (quotas).
       3. For Quota type, choose the relevant "Unable to access <region> region" option (for example, West Europe in the documented example) and submit.
5. If the problem persists across many regions
   • For some subscriptions, especially offers like Azure for Students, there can be broader regional restrictions or transient platform issues.
   • If deployments fail in multiple normally supported regions and the error is about region or SKU availability, and after trying different regions and SKUs the issue persists, open a support request from the Azure portal under Service and subscription limits (quotas) and describe that the student subscription cannot deploy in multiple regions.

In practice, for the described scenario:

• First, try deploying the Batch or VM resources in another supported region (for example, a different US or Asia region) and choose a VM size that appears as available in the portal size picker.
• If specific regions must be used and they consistently fail with region access or SKU not available errors, submit a quota/support request for region access as described above.

References:

• Resolve errors for SKU not available
• Resolve issues when creating, deleting, or restoring Azure Function App
• Azure resource providers and types
• Resolve location ineligible errors
• Troubleshoot common Azure deployment errors