Saudi cloud planning now involves several providers and different stages of availability. A region announcement, an operating location and an orderable service are distinct facts. The position below was checked on September 7, 2026; confirm it again before procurement or migration.
Established locations: verify the service you need
| Provider | Location evidence and qualification |
|---|---|
| Google Cloud | Dammam region launched in November 2023; check service availability and purchase arrangements. Google announcement |
| Oracle Cloud | Oracle identifies Jeddah and Riyadh regions, opened in 2020 and 2024 respectively. Oracle Saudi region information |
| Huawei Cloud | Huawei announced the Riyadh region launch in September 2023. Huawei announcement |
| SCCC / Alibaba Cloud | The Saudi launch was announced in 2022; check current services and contracting arrangements. Saudi Press Agency announcement |
| Tencent Cloud | Tencent's region documentation lists Riyadh for the documented service, with purchase restrictions. Confirm access and availability for each required product. Tencent region documentation |
These sources establish specific location or service information. They do not establish that every product, feature or capacity option is available in each location.
Announced launches are planning assumptions
Microsoft announced Saudi Arabia East availability for November 2026, with three availability zones. As of this review, that is an announced launch date, not a claim that customer workloads can already deploy there. Microsoft August 31 announcement.
Amazon says its Saudi AWS region is on track for December 2026. Treat that timing as a plan until availability is confirmed for your intended account and services. Amazon Saudi region announcement.
Keep a fallback for workloads that cannot wait. Recheck service catalogs, quotas, support arrangements and ordering access before committing a cutover date. An Azure region announcement also does not establish the data location of a separate Microsoft 365 service.
Map the complete data flow
Start with application data, then add backups, logs, diagnostics, identity systems, support access and integrations. Have the privacy and compliance owners assess the applicable requirements for those flows.
A local region is one part of that assessment. Review service-specific access controls and exceptions: for example, Azure Customer Lockbox documents scenarios outside its approval process. Microsoft Customer Lockbox documentation.
Document which controls are provided by the service, which require configuration and which remain your team's responsibility.
Compare workloads individually
Measure latency from the actual offices and carriers. A local region does not guarantee a particular response time; application design, network paths and dependencies affect the result.
Compare total costs including compute, storage, backup, data transfer, connectivity, licenses, support and operations. Test failure scenarios and recovery arrangements against your objectives. Do not assume that a second availability zone or local region automatically meets every recovery requirement.
BustanTech offers Microsoft Azure and IT infrastructure services. Discuss a workload placement assessment using your required services, data flows and operational constraints.