In-country cloud stopped being a theoretical option in the UAE some time ago. Microsoft has run UAE North in Dubai and UAE Central in Abu Dhabi since June 2019. AWS opened the Middle East (UAE) Region, me-central-1, in August 2022. Both hold Dubai Electronic Security Centre certification. For most UAE businesses the question is no longer whether data can stay in the country, it is which platform to put it on and what the disaster recovery story looks like once you have.

Here is how the two actually compare on the things that change an architecture.

Two providers, three UAE regions

Azure. UAE North sits in Dubai, UAE Central in Abu Dhabi. Both went live on 19 June 2019, Microsoft’s first cloud regions in the Middle East.

AWS. me-central-1 launched on 29 August 2022 with three availability zones, backed by a multi billion dollar commitment over fifteen years. It is AWS’s second Middle East region after Bahrain.

One practical detail that catches teams out on day one: me-central-1 is an opt-in region. It is disabled by default on a new AWS account and has to be explicitly enabled before you can deploy into it or even see it in the console.

Availability zones are where the platforms diverge

This is the difference that shapes the design, and it is not symmetrical.

Azure UAE North supports availability zones. Microsoft does not publish a per region zone count, but states that zone enabled regions comprise a minimum of three, typically several kilometres apart and within about 100 kilometres of each other.
Azure UAE Central does not support availability zones, and it is a restricted access region. Microsoft flags it as available to support specific customer scenarios such as disaster recovery within a geographic area, rather than as a general purpose region.
AWS me-central-1 has three availability zones, published as mec1-az1, mec1-az2 and mec1-az3.

Read that back and the consequence is clear. You can build a zone redundant production estate in Dubai on Azure, or in the UAE on AWS. You cannot build a zone redundant production estate in Abu Dhabi on Azure. UAE Central is a destination for replication, not a second home for your workloads.

In country does not mean every service

Both UAE regions carry a subset of their provider’s catalogue, and the gap moves every quarter. Two examples of how uneven it can be:

On AWS, Amazon Bedrock has been generally available in me-central-1 since 29 September 2025. Since February 2026, Anthropic’s Claude models are reachable from the Middle East regions through Bedrock global cross-Region inference. The residency nuance matters and is worth reading properly: inference compute may execute outside the UAE, while AWS states that customer data is not stored in a destination region, and customer managed logs, knowledge bases and stored configurations remain in the source region.
On Azure, UAE North is listed as a supported region for Microsoft Foundry projects, but it is absent from the supported region table for the classic Foundry Agent Service. UAE Central does not appear in the Foundry region tables at all.

The rule we give clients is simple. Before you commit to a platform, list the specific services the first two phases need, then check them against the official region tables rather than a sales deck, and check again before each phase starts. AWS made this easier in November 2025 with Capabilities by Region, which shows services, features and APIs per region side by side and, usefully, a forward looking roadmap status. Azure’s equivalent is the products by region table.

Residency, and the certifications that actually get asked for

Microsoft’s commitment is that it will not store or process customer data outside the customer specified Geo without authorisation. The UAE is its own Azure Geography containing both UAE regions, so in Geo means in country. AWS’s model is that customer content stays in the region you choose unless you move it.

The certification that comes up in Dubai government and semi government tenders is the DESC Cloud Service Provider Security Standard. Both providers hold it. Microsoft’s certification covers UAE Central and UAE North across Azure, Dynamics 365 and Office 365 core services. AWS completed its 2026 DESC audit on 5 March 2026, with 108 services in scope for the Middle East (UAE) Region, audited by BSI and valid to 22 January 2027. If a tender asks for evidence, AWS currently publishes a dated scope and expiry; Microsoft’s compliance page has not carried a refresh date since 2023, so ask for the current certificate rather than citing the page.

Underneath all of that sit three parallel data protection regimes, and which one applies depends on where your entity is registered, not where the server is:

Federal PDPL, Federal Decree-Law No. 45 of 2021, in force since 2 January 2022, with the UAE Data Office as regulator. It applies to processing inside or outside the country and sets consent, correction, restriction and cross border transfer requirements.
DIFC, Data Protection Law No. 5 of 2020.
ADGM, Data Protection Regulations 2021, effective 14 February 2021, with its own Office of Data Protection.

A DIFC entity on Azure UAE North is still a DIFC entity. Hosting in country satisfies a residency clause; it does not satisfy the law on its own.

What it costs

Neither provider publishes a headline UAE premium, so treat any single number with suspicion. Independent price trackers that scrape the official pricing APIs put like for like general purpose compute in the UAE roughly 20 to 25 percent above the cheapest United States regions and a few percent above Western Europe, on both platforms. That is the right order of magnitude to plan with, and the wrong number to sign a budget against. Price your actual SKUs in each provider’s calculator.

In practice the region premium is rarely the biggest line. Right sizing, reserved instances or savings plans, storage tiering and switching off what nobody uses move the invoice further than the choice of region does. We typically take 20 to 30 percent out of a cloud bill in the first quarter after migration without changing region.

How the decision usually goes

Neither platform is the right answer in the abstract. The pattern we see repeat:

An existing Microsoft estate, Active Directory, Microsoft 365, SQL Server and Windows licensing with Software Assurance, normally lands on Azure UAE North with UAE Central as the replication target. Azure Hybrid Benefit alone often decides it.
A Linux, container or data native team, or an organisation already running AWS elsewhere, normally lands on me-central-1. Remember to enable the region on the account before the first sprint.
Regulated workloads come down to which provider can evidence the exact control set the regulator or the client’s audit asks for, on paper, in the current year.

The part most UAE migrations get wrong

Multiple availability zones inside one region protect you from a rack, a room or a building. They do not protect you from losing the region. Those are different risks and they need different answers.

On Azure, the in country cross region option is UAE North to UAE Central, and UAE Central has no availability zones and restricted access, so it is a recovery destination rather than a second production site. On AWS there is no second UAE region; the nearest pair is me-central-1 to Bahrain me-south-1, which is out of country and therefore a data residency decision as much as a technical one.

So the question to settle in writing, before the first workload moves, is this: if the region is unavailable for a day, what happens? Which systems must come back, in what order, how long can each one be down, how much data can you afford to lose, and where does the recovery copy live? Then test it, on a schedule, with the answer written down. A recovery plan that has never been executed is a hypothesis.

Where to start

Lunet assesses each workload against cost, latency, licensing and regulation, builds the landing zone before anything moves, then migrates in waves with overnight cutovers and a rollback position at every step. See how we handle cloud migration, or talk to a Dubai engineer about which region fits your estate.

Sources

Written by the Lunet Computers cloud team in Dubai. Region service availability changes constantly; verify against the official tables before you design against it.

Azure UAE North vs AWS me-central-1: choosing a UAE cloud region