Azure migration · field note
Saudi Arabia East isn't in your Azure portal yet. Here's what to check.
Microsoft said November. If the region still isn't in your subscription, five read-only checks tell you what's actually blocking you, and most of the fixes don't need Microsoft.
On November 13, 2026, I opened the region list in our own Azure subscription and looked for Saudi Arabia East. It wasn't there.
Microsoft said in August that the region would be available to customers this month, and plenty of teams in the Kingdom have budgets, contracts and migration dates resting on that one sentence. If you've been refreshing the portal and seeing nothing, you aren't doing anything wrong.
When it does arrive, check what "available" means for your own subscription. The portal listing a region and your team deploying a production workload there are two different events, sometimes weeks apart. This note covers how to check where you stand, the blocker many organizations have already built for themselves, and what to do with the time in between.
01 / The facts
What has Microsoft actually confirmed about Saudi Arabia East?
The month, not the day. On August 31, 2026, Microsoft said Saudi Arabia East would be available to customers in November 2026, with three availability zones in the Eastern Province. That replaced the Q4 2026 window it gave in February.
On November 14, Saudi Arabia East still doesn't appear in the Azure regions list on Microsoft Learn. That's the page that gives each region's programmatic name, its availability zones and whether access is restricted. Microsoft hasn't published a day-one service list either. The announcement talks about supported services and eligible workloads without naming them.
So treat November as confirmed for the region and unconfirmed for your application. What Microsoft has confirmed about the launch date covers the timeline in more detail.
02 / Five checks
How do you check whether your subscription can use the region?
Run these checks in order. Each answers a different question, and a yes on one tells you nothing about the next. They're all read-only, so Reader access on the subscription is enough.
Check 1: can your subscription see the region at all? az account list-locations lists the regions available to the current subscription. Microsoft hasn't published the programmatic name yet, so search on the display name instead of guessing it:
az account list-locations \
--query "[?contains(displayName, 'Saudi')].{name:name, displayName:displayName}" \
--output table An empty result means this subscription can't see the region yet. Run it for every subscription you plan to use, because access is granted per subscription. In PowerShell, Get-AzLocation | Where-Object DisplayName -like '*Saudi*' does the same job.
Check 2: does the service you need support it? Each resource provider keeps its own list of supported locations, so the region can be live while App Service or Azure SQL isn't there yet. For App Service:
az provider show --namespace Microsoft.Web \
--query "resourceTypes[?resourceType=='sites'].locations | [0]" \
--output tsv | grep -i saudi Swap the namespace and resource type for each part of your stack, for example Microsoft.Sql with servers, Microsoft.ContainerService with managedClusters, or Microsoft.Storage with storageAccounts. No output means that service doesn't list the region for you yet.
Check 3: are the VM sizes you need open to you? az vm list-skus takes subscription-level restrictions into account. Add --all to include sizes you can't use, then read the Restrictions column. NotAvailableForSubscription means that size is blocked for you in that region.
az vm list-skus --location <region-name> --size Standard_D --all --output table Use the programmatic name from check 1 for <region-name>. Check the exact sizes your pilot needs, because restrictions apply size by size.
Check 4: how much quota do you have there? Quota is per subscription and per region. Whatever limits you've raised in UAE North or West Europe don't come with you.
az vm list-usage --location <region-name> --output table Azure SQL keeps its own region access and quota. If you see "Your subscription does not have access to create a server in the selected region", that's a region access request for SQL, not a bug in your template.
Check 5: will your own policy allow it? This one deserves its own section.
Put the five checks in a script and save the result with the date. The day the region appears, run it again and you'll see in minutes which lines moved from no to yes. That file is also your evidence when someone asks why the migration date isn't fixed yet.
03 / The blocker you built
Will your own Azure Policy block Saudi Arabia East?
If you have a landing zone, there's a good chance it will. Governed estates usually restrict where resources can be created, often with the built-in Allowed locations policy. That policy only knows the regions somebody listed when it was assigned. When Saudi Arabia East opens, a deployment there fails with RequestDisallowedByPolicy until the list changes.
Find the assignments that apply to your subscription, including ones inherited from management groups:
az policy assignment list --disable-scope-strict-match \
--query "[?contains(policyDefinitionId, 'e56962a6-4747-49cd-b67b-bf8b01975c4c')].{name:name, scope:scope}" \
--output table That ID belongs to the built-in Allowed locations definition. Resource group locations are governed by a separate built-in policy, so check for that too. If your restriction lives inside an initiative or a custom policy, this query won't find it. Open Policy, then Assignments, in the portal and look for anything about location.
Check your templates while you're there. A Bicep parameter with an @allowed list of regions, or a Terraform validation rule, rejects the new region the same way.
What could break. Policy is cumulative. A more generous assignment on the pilot subscription won't override a deny inherited from the management group. You either update the inherited assignment's list, which opens the region to every subscription under that management group, or you exempt the pilot subscription and record who approved it. I'd take the exemption for a pilot and widen the list only once the region has passed your own tests. The landing zone guide for Saudi Arabia covers the rest of the guardrails worth settling first.
04 / Access, quota and capacity
What if the region shows up but deployments still fail?
Then it's usually region access, quota or capacity, and the error message tells you which.
Region access. Some Azure regions need a support request before a subscription can use them, and the regions list marks those as restricted. Microsoft hasn't said whether Saudi Arabia East will open to every subscription at once or start that way. If it is restricted, the region access request goes through Help + support with the issue type Service and subscription limits (quotas). Put every subscription ID and every service you need in one request; Microsoft's own guidance suggests exactly that to avoid a chain of tickets.
Quota. If check 4 shows limits below what your pilot needs, raise them before the cutover window, not during it.
Capacity. Quota is permission. Capacity is whether Azure has the hardware free, and Microsoft's documentation is plain that a deployment can fail on capacity even with enough quota. In a region's first weeks I'd expect that more often for the less common VM sizes. Deploy your exact sizes in a test first, and look at on-demand capacity reservation for anything that can't fail on the night.
Hold off on reservations. In Microsoft's region access process, enabling Reserved Instances for a region is a separate item in the request, so don't assume you can buy them the day the region appears. Buy once the workload has run there on sizes you've tested. What happens to your existing reservations and savings plans when you move covers the commitments you already hold.
05 / Using the wait
What should you do until the region appears?
Most of the work that decides whether a move goes well doesn't need the region at all.
- Map each workload. Owner, current region, monthly cost, dependencies, and which data actually has to sit in the Kingdom.
- Start a service register. One line per dependency, with today's answer from checks 2 and 3 and the date you checked. When the region appears, you update lines instead of starting over.
- Fix the landing zone now. Policy, templates, naming and address space for the new region. Nobody wants to discover a policy conflict during a cutover window.
- Pick one pilot. Small enough to roll back, real enough to prove identity, networking, backup and monitoring together.
- Keep your fallback. Your current region stays the deployment and recovery target until the whole stack has passed testing in Saudi Arabia East.
Not every workload should move early. If nothing forces the move (no data residency requirement, no latency complaint, a reservation running into next year), there's no prize for being first. Waiting a quarter is often the cheaper decision; move at launch or wait walks through how to decide. The Saudi readiness checklist has the full list of what to prepare. Until then, don't promise anyone a cutover date; promise the date you'll have the evidence to set one.
06 / This week
What should you check this week?
- Run checks 1 to 4 for every subscription you'd use, and save the output with the date.
- Find your Allowed locations assignments and decide now who approves adding Saudi Arabia East.
- Search your Bicep and Terraform for hardcoded lists of regions.
- Write down the exact VM sizes, SQL tiers and other services your pilot needs, so check 3 takes minutes when the region arrives.
- Set a weekly reminder to rerun the script until the region shows up, then once more before any production change.
If you'd rather have someone run this across your estate, the Saudi Arabia East Readiness Sprint does it as part of a fixed ten-day assessment.
Primary references
Sources and further reading
- Microsoft: Saudi Arabia East available to customers in November 2026 (August 31, 2026)
- Microsoft: Azure regions list
- Microsoft: Azure region access request process
- Microsoft: az account list-locations
- Microsoft: Azure resource providers and types
- Microsoft: Resolve errors for SKU not available
- Microsoft: Check vCPU quotas
- Microsoft: Resolve capacity errors with Azure SQL Database or Azure SQL Managed Instance
- Microsoft: Resolve errors for request disallowed by policy
- Microsoft: Azure Policy built-in definitions (Allowed locations)
- Microsoft: Azure products available by region
Questions teams ask
Frequently asked questions
Why isn't Azure Saudi Arabia East showing in my portal?
Either the region hasn't been opened to your subscription yet, or something on your side hides or blocks it. Run az account list-locations to see whether the subscription can see the region, then check service support, VM size restrictions, quota and your Allowed locations policy, because each one decides separately what you can deploy.
When exactly will Saudi Arabia East be available?
Microsoft has said November 2026 and hasn't given a day. Check your own subscription with az account list-locations rather than relying on news coverage, because what one subscription can see doesn't tell you what another can.
Why can a colleague see a region that I can't?
Region access, quota and policy are all set per subscription. Two subscriptions in the same tenant can see different regions, and an Allowed locations policy on one management group doesn't apply to subscriptions under another.
Will Saudi Arabia East need a region access request?
Microsoft hasn't said. Once the region is added to the Azure regions list, a restricted region carries an icon there. If it's marked, use the region access request process through Help + support and include every subscription you need in one ticket.
Do I need to raise quota before I deploy?
For anything production sized, probably yes. Quota is per subscription and per region, so limits raised in UAE North or West Europe don't carry over. Check with az vm list-usage and request increases through Help + support.
Can I buy reservations for Saudi Arabia East now?
Not until the region and the VM size are available to your subscription. Even then, wait until the workload has run there on the sizes you've tested, so the commitment matches what you actually use.
What should I tell leadership about the move date?
That the region date is Microsoft's and the cutover date is yours. Set the cutover after a pilot has passed in the new region, not on the day the region appears.