B12 Magazine

Daily from the four markets B12 Group works in

Technology

Cloud and data residency in the UAE: a guide for businesses

The PDPL, sector rules for finance and health, free-zone regimes, local cloud regions and sovereign options: how UAE businesses can decide where their data lives, and migrate safely.

GuideB12 Group10 min read

Every business that moves to the cloud eventually faces a simple question with a complicated answer: where does our data actually live, and does that matter? In the UAE, cloud and data residency decisions sit at the intersection of a federal data protection law, sector-specific rules for regulated industries, separate regimes in the financial free zones and a fast-growing set of local cloud regions. This guide sets out the landscape for UAE businesses: the Personal Data Protection Law, the rules for finance and health, the in-country regions of the major providers, what sovereign cloud means in practice, and how to plan a migration that is secure and defensible.

It is a practical overview, not legal advice. Laws, executive regulations and regulator guidance evolve, and the obligations that apply to a specific business depend on its sector, licence and data. Confirm the current rules with your regulator and qualified counsel before making decisions.

Why data residency matters

Data residency refers to the physical and legal location where data is stored and processed. It matters for three reasons. The first is legal: some laws restrict transfers of certain data outside the country or require approvals and safeguards. The second is contractual: clients, especially governments and large enterprises, increasingly require suppliers to keep their data in-country. The third is practical: data held close to users reduces latency, and data held under a familiar jurisdiction simplifies questions of access, audit and dispute.

Residency is not the same as security. Data can sit in a local data centre and still be poorly protected, or sit abroad under strong controls. A sound strategy treats location as one control among many, alongside encryption, access management, monitoring and contractual protections.

The UAE Personal Data Protection Law

The cornerstone of the federal framework is Federal Decree-Law No. 45 of 2021 Regarding the Protection of Personal Data, commonly called the PDPL. According to the UAE Government portal, it came into force on 2 January 2022 and applies to the processing of personal data, wholly or partly through electronic systems, inside or outside the UAE.

The law's central principle is that processing generally requires the data subject's consent, with defined exceptions such as protecting the public interest or carrying out legal procedures. Individuals have rights to request correction of inaccurate data and to restrict or stop processing. The government portal also notes that the law sets out requirements for the cross-border transfer and sharing of personal data.

Alongside it, Federal Decree-Law No. 44 of 2021 established the UAE Data Office, a federal regulator affiliated with the Cabinet. According to the government portal, the Data Office is responsible for preparing data protection policies and legislation, proposing standards for monitoring the PDPL, establishing complaint systems and issuing guidance on implementation.

For cloud decisions, the transfer provisions are the part to study most carefully. In broad terms, the PDPL distinguishes between transfers to jurisdictions considered to offer adequate protection and transfers that rely on specific alternative grounds. The detail of how those grounds apply, and the status of implementing regulations and Data Office guidance, should be confirmed with counsel at the time of your decision, because this is an area where the rules continue to develop.

The PDPL is not the only data law in the country. The government portal also lists the Dubai Data Law of 2015, consumer protection rules that restrict the use of consumer data for marketing, and the federal cybercrime law. And, importantly, the PDPL sits alongside separate regimes for particular sectors and for the financial free zones.

The financial free zones: DIFC and ADGM

Two of the UAE's financial free zones operate their own data protection regimes, modelled closely on international practice. Businesses licensed there must follow those rules rather than, or in addition to, the federal framework, depending on their activities.

In the Dubai International Financial Centre, the governing law is the DIFC Data Protection Law, originally enacted as DIFC Law No. 5 of 2020 and amended since. The DIFC publishes the law, its accompanying regulations and later amendments in its legal database, and companies should work from the current consolidated text.

In Abu Dhabi Global Market, the framework is the ADGM Data Protection Regulations 2021, overseen by an independent Office of Data Protection. According to ADGM, entities processing personal data must register as data controllers, must give individuals access to their data on request and have specific obligations when a breach occurs. ADGM states that its regime follows the European Commission's approach of designating jurisdictions as adequate.

For cloud planning, the practical consequence is that a group with entities onshore, in the DIFC and in ADGM may face three sets of transfer rules. Mapping which entity owns which data is the first step in any migration.

Health data: the strictest localisation rule

Healthcare is the sector where residency rules are most explicit. Federal Law No. 2 of 2019 concerning the use of information and communication technology in health fields regulates how health information is handled across the UAE, including its free zones. Article 13 of the law, in the official text published by Emirates Health Services, sets the default that health information and data relating to health services provided in the UAE may be stored, processed, generated or transferred outside the country only in cases defined by a decision of the health authority in coordination with the ministry.

Ministerial decisions since then have defined a set of permitted exceptions, often accompanied by conditions such as keeping a copy of the data in the UAE. Hospitals, clinics, insurers, health technology companies and any supplier processing patient data should therefore assume that in-country hosting is the starting point, and confirm any exception with the relevant emirate-level health authority before placing data abroad.

Financial services: outsourcing and the Central Bank

Banks and other financial institutions licensed by the Central Bank of the UAE face a further layer: outsourcing regulation. The Central Bank issued its Outsourcing Regulation for Banks in 2021, with accompanying standards. Cloud services are, in regulatory terms, a form of outsourcing, so a bank's move to the cloud falls within its scope.

The regulation places responsibility firmly on the bank. Institutions must assess and manage the risks of outsourcing, ensure that providers maintain appropriate information security and service delivery, and control subcontracting where confidential data is involved. Material outsourcing requires engagement with the Central Bank before it proceeds, and outsourcing outside the UAE carries additional considerations. Insurance companies, exchange houses and other licensed entities may be subject to their own rules from their regulators, and entities in the DIFC and ADGM answer to their own financial regulators.

For a financial institution, the cloud question is therefore not only where the data sits, but whether the regulator has been consulted, whether the contract gives the institution and the regulator the audit and access rights they require, and whether there is a credible exit plan.

The local cloud regions of the major providers

The good news for UAE businesses is that the major hyperscale providers now operate infrastructure inside the country, which makes in-country hosting a mainstream option rather than a compromise.

Microsoft Azure lists two UAE regions: UAE North, located in Dubai, with three availability zones, and UAE Central, located in Abu Dhabi, which serves as its paired region and is restricted to specific scenarios such as disaster recovery within the same geography.

Amazon Web Services operates the Middle East (UAE) region, with the code me-central-1 and three availability zones, according to AWS documentation. Like other newer AWS regions, it must be enabled in an account before use. AWS also operates a region in Bahrain.

Oracle Cloud Infrastructure lists two commercial UAE regions: UAE Central in Abu Dhabi and UAE East in Dubai, each with a single availability domain.

Google Cloud lists regions across the Middle East and offers data residency controls for specified services; businesses considering it should check its current locations page for the regions available closest to their users and whether a given service supports in-country storage.

Two cautions apply. First, not every service is available in every region, and a workload may depend on a service, such as a specific AI or analytics tool, that is only offered elsewhere. Second, a local region does not automatically mean every copy of the data stays local; backups, logs, support access and global services can involve other locations. Read the provider's data residency documentation, not only its region map.

Sovereign cloud: what it means in practice

Sovereign cloud has become one of the most used, and least precise, terms in the industry. In practice it describes a set of guarantees that go beyond simple data residency. A sovereign arrangement typically aims to ensure that data stays in-country, that operational control and support are performed by locally vetted personnel, that encryption keys are held by the customer or a local entity, and that the platform is subject to local law and oversight rather than foreign jurisdiction.

Offerings range from dedicated regions operated for government and regulated customers, to partnerships between global providers and national operators, to private and on-premises platforms that bring cloud tooling into the customer's own data centre. Each balances control against cost, features and pace of innovation.

For most private businesses, full sovereignty is unnecessary. A well-configured local region with customer-managed encryption keys, strict access controls and appropriate contracts meets the large majority of requirements. Sovereign arrangements become relevant for government work, critical infrastructure, defence-adjacent suppliers and the most sensitive financial and health data.

Planning a migration: a practical sequence

Begin with a data inventory. Identify what data you hold, where it sits today, which entity owns it and which laws apply to it. Classify it: public, internal, confidential, personal, sensitive personal, health, financial. Without this map, residency decisions are guesswork.

Next, establish the regulatory requirements for each category. Health data points towards in-country hosting; regulated financial data requires engagement with the regulator; personal data under the PDPL or a free-zone regime requires a lawful basis for any transfer. Record your conclusions and the advice behind them.

Then choose the architecture. Decide which workloads can run in a UAE region, which can run elsewhere, and whether a hybrid model is needed. Check service availability in the chosen region, plan for resilience across availability zones, and decide where backups and disaster recovery copies will live.

Review the contracts. Ensure the provider's terms address data location, subprocessors, breach notification, audit rights, regulator access where needed and exit assistance. For regulated entities, check that the contract meets the regulator's expectations before signing.

Migrate in waves. Start with a lower-risk workload, validate controls, monitoring and costs, and then move more sensitive systems. Keep a rollback plan for each wave. Finally, document everything: data flows, decisions, configurations and approvals. When an auditor, client or regulator asks where the data lives and why, a clear record is the best answer.

Many organisations bring in specialist help for the inventory, architecture and security stages. B12 IT Solutions is one of the firms in Dubai that advises businesses on cloud and cyber security, and whichever partner you choose, insist on a written data map and a clear allocation of responsibilities.

Security in the cloud: the shared responsibility

Every major provider operates a shared responsibility model: the provider secures the underlying infrastructure, while the customer is responsible for how it configures and uses the services. Most cloud incidents arise not from a failure of the provider's data centre but from misconfiguration, weak identity controls or exposed credentials on the customer side.

The essentials are well established. Enforce multi-factor authentication and least-privilege access, and review permissions regularly. Encrypt data at rest and in transit, and consider customer-managed keys for sensitive data. Turn on logging and monitoring, and make sure someone actually reviews the alerts. Patch and harden workloads, segment networks, and test backups by restoring them. Prepare an incident response plan that includes the notification duties under your applicable data protection regime.

Local standards can also guide the work. The Dubai Electronic Security Center, for example, lists a Cloud Service Provider Security Standard among its published documents, and government entities and their suppliers in Dubai should check which DESC requirements apply to them. Sector regulators and the free-zone authorities publish their own expectations, and international frameworks provide a common language with auditors.

What it means

Data residency in the UAE is no longer a barrier to cloud adoption. The major providers operate in-country regions, the federal and free-zone laws give a clear if still evolving framework, and the sector rules for health and finance are explicit enough to plan around. The businesses that move most smoothly are those that start with a precise map of their data, take regulatory advice early, choose architecture that matches the sensitivity of each workload and treat security configuration as an ongoing discipline rather than a one-off project. Location matters, but discipline matters more.

More from Technology

Call us free