When will Microsoft Azure Saudi Arabia East be officially available?

Microsoft has confirmed that Azure Saudi Arabia East will become available during November 2026, but it has not published a specific calendar date for general customer access. ^1^

Current confirmed status

• Launch window: November 2026. This supersedes the earlier, broader Q4 2026 announcement. ^2^
• Exact launch date: No specific day has been announced publicly.
• Infrastructure: The region is in the Eastern Province and comprises three Azure Availability Zones.
• Launch scope: Microsoft states that customers will gain access to supported Microsoft cloud and AI services and will be able to host eligible workloads and data locally. That wording does not guarantee that every Azure service, feature, VM family, or SKU will be available on day one. ^1^

Windows and SQL availability

There is currently no published confirmation in the available service documentation that all of the following will be deployable immediately at launch:

• Windows Server Virtual Machines
• SQL Server on Azure Virtual Machines
• Azure SQL Database
• Every SQL Database tier, hardware generation, or zone-redundant configuration

Microsoft’s Product Availability by Region table is the authoritative service-by-service source. Its entries, release dates, features, and requirements can change before commercial release. ^3^

For Azure SQL Database specifically, Microsoft directs customers to that same regional product table to determine whether the service is offered in a region. The SQL feature matrix then identifies whether individual capabilities and hardware options are supported. Saudi Arabia East is not identified in the supplied SQL feature tables, so SQL Database—and especially specific tiers or zone-redundant features—should not yet be treated as confirmed for launch day. ^4^

When Portal deployment will become possible

Once the region is commercially enabled for a subscription, Saudi Arabia East should appear as an available location when creating supported resources in the Azure portal. Availability can still differ by:

• Resource provider and service
• Subscription
• VM size or SKU
• Availability Zone
• Capacity or access restrictions

For VMs, check the actual subscription-specific inventory after launch:

az login
az account set --subscription "<subscription-id>"

az vm list-skus \
  --location <saudi-region-code> \
  --resource-type virtualMachines \
  --zone --all --output table

Use the region code exposed by Azure after launch rather than assuming its value. The command reports SKU restrictions such as NotAvailableForSubscription; the portal’s Create a virtual machine → Size → See all sizes page provides the corresponding UI check. ^5^

Production planning for healthcare applications

Do not commit a production go-live for the first day of regional availability until all required components are shown as available for the target subscription. Validate:

1. The intended hosting service—VMs or another supported ASP.NET Core hosting option.
2. The required Windows Server image and VM sizes.
3. SQL Server marketplace images or the required Azure SQL Database tier.
4. Storage, networking, backup, monitoring, and disaster-recovery services.
5. Availability Zone support for each component.
6. Capacity/quota and successful nonproduction deployment.
7. Applicable healthcare, data-residency, security, and regulatory requirements.

The three-zone regional design provides an infrastructure basis for high availability, but it does not by itself confirm that each selected service supports zone redundancy at launch. Keep an existing supported Azure region as the deployment or recovery fallback until the complete application stack has passed testing in Saudi Arabia East.

References

1. Microsoft Announces That Saudi Arabia East Datacenter Region Will Be ...
2. Microsoft Confirms Saudi Arabia Datacenter Region Available for ...
3. Product Availability by Region - azure.microsoft.com
4. Feature availability by region - Azure SQL Database
5. Resolve errors for SKU not available