Skip to content

Leadership guide · for CIOs and IT directors

UAE PDPL compliance for IT teams: what changes in Microsoft 365 and your data setup

Federal Decree-Law No. 45 of 2021 is a legal obligation, but most of the work lands on IT: knowing where personal data lives, who can reach it, how long you keep it and what happens when something leaks. This guide turns the law into a Microsoft 365 and infrastructure work plan.

Reviewed by Abu Amir, CEO, Missan Global · Updated

What the law is, in one paragraph

The Personal Data Protection Law, Federal Decree-Law No. 45 of 2021, sets rules for processing personal data, gives individuals rights over their data and sets conditions for sending data outside the UAE. The UAE Data Office is the authority responsible for data protection policy, standards, complaints and guidance. Several areas sit outside the law, including free zones with their own data protection legislation: ADGM and DIFC (DIFC Law No. 5 of 2020). Detailed procedures are left to Executive Regulations, so check the current status of those regulations with your legal adviser before you fix timelines in policy.

Why this lands on IT

A lawyer can draft your privacy notice. They cannot tell you which SharePoint sites hold passport copies, which former employees still have mailbox access, or whether HR exports are sitting in someone's OneDrive. The obligations that need technical evidence are:

  • Security of processing: appropriate technical and organisational measures to protect personal data.
  • Data subject rights: finding, correcting, restricting or deleting one person's data on request, across every system.
  • Records of processing: what you hold, why, where and for how long.
  • Breach notification: spotting a breach, assessing it and notifying the Data Office (and in some cases the people affected) as the law requires.
  • Cross-border transfers: knowing which systems store or process data outside the UAE.

Step 1: build a data map you can defend

Start with systems, not policies. For each system that holds personal data, record:

  • What categories of personal data it holds (staff, customers, patients, students, visitors).
  • Whether any of it is sensitive: health, biometric, religious, criminal records and similar.
  • Where it is stored and processed, including the country of the SaaS provider's data centre.
  • Who has access, and how that access is granted and removed.
  • How long it is kept, and what deletes it.
  • Who the business owner is.

In most mid-sized companies the list includes Microsoft 365, the ERP, HR and payroll, CRM, a visitor or access control system, CCTV, file servers and a long tail of SaaS sign-ups paid on company cards. The tail is where the surprises are.

Step 2: Microsoft 365 changes that make the biggest difference

If you are on Microsoft 365, most of the controls you need are already in your licence. Microsoft Purview is the family of tools to look at first.

Know where your tenant data lives

Microsoft offers in-country data storage for core Microsoft 365 data in a number of countries, including the UAE, for tenants that qualify. Check your tenant's data location in the admin centre and read Microsoft's data residency overview for which workloads are covered. Older tenants are often still in Europe.

Label and protect sensitive content

  • Define a short set of sensitivity labels (for example Public, Internal, Confidential, Personal data) and publish them.
  • Use auto-labelling or sensitive information types to find Emirates ID numbers, passport numbers and bank details in files and mail.
  • Turn on data loss prevention policies that warn, then block, sending labelled personal data outside the organisation.

Retention and deletion

  • Set retention policies that match your records schedule, not "keep everything forever".
  • Agree with HR and finance how long leavers' mailboxes and OneDrives are kept, then enforce it.

Access and identity

  • Multi-factor authentication for every account, enforced with Conditional Access.
  • Review external sharing on SharePoint and OneDrive. "Anyone with the link" is the usual leak.
  • Quarterly access reviews for HR, finance and any site holding sensitive data.
  • A tested leaver process. Our onboarding and offboarding checklist covers it.

Audit and investigation

  • Confirm unified audit logging is on and that retention is long enough for an investigation.
  • Make sure you can run a content search for one person's data when a request arrives.

Step 3: the rest of the estate

  • File servers and NAS: scan for personal data, tighten share permissions, move what you can into labelled SharePoint libraries.
  • ERP, HR and CRM: role-based access, no shared admin accounts, export logging.
  • Endpoints: disk encryption, managed devices only for sensitive data, remote wipe for lost laptops and phones.
  • Backups: encrypted, access-controlled, and included in your retention rules. Deleted data that lives on in a backup forever is still held data.
  • CCTV and visitor systems: retention periods, who can export footage, where recordings are stored.
  • Vendors: data processing terms with every provider who touches personal data, including your IT provider.

Step 4: breach readiness

The PDPL requires you to notify the Data Office of a breach that affects the privacy, confidentiality or security of personal data, and in some cases to tell the people affected. You cannot do that well without the basics in place first:

  1. Detection: alerts from Microsoft Defender, your firewall and your endpoint protection go to someone who reads them.
  2. A one-page incident procedure: who assesses, who decides, who notifies, who talks to customers.
  3. Logs kept long enough to establish what was accessed.
  4. A tabletop exercise at least once a year.

If you have no one watching alerts out of hours, a managed detection and response service closes that gap.

Checklist: PDPL technical readiness

  • Data map for every system holding personal data, with an owner for each.
  • Microsoft 365 data location confirmed and documented.
  • MFA enforced for all users; legacy authentication blocked.
  • Sensitivity labels and DLP policies live for personal data.
  • Retention policies matching the records schedule.
  • External sharing reviewed and restricted.
  • Audit logging on, with tested search for data subject requests.
  • Encrypted, managed endpoints.
  • Data processing terms with all relevant vendors.
  • Incident procedure written and rehearsed.
  • A named owner (DPO or equivalent) for requests and breaches.

Where Missan helps

We help you meet PDPL requirements on the technical side. That means building the data map from your actual systems, configuring Microsoft 365 and Purview, tightening access, setting up logging and detection, and producing the evidence pack your lawyer or DPO needs. We do not give legal advice and we do not certify compliance. As a Microsoft Solutions Partner we work inside your tenant, and if you leave, your Microsoft tenant and accounts stay in your name. The PDPL compliance page sets out how an engagement runs.

Download the checklist (PDF)

PDPL technical readiness checklist, ready to print

The checklist from this guide on one or two A4 pages, with tick boxes, for your next planning meeting.

Our team may contact you about this topic. We reply within one business day if you ask us anything, and you can tell us to stop at any time. See ourprivacy policy.

Related Missan services

Frequently asked questions

Does the UAE PDPL apply to companies in DIFC or ADGM?

Generally not. DIFC and ADGM have their own data protection laws and regulators (DIFC Data Protection Law No. 5 of 2020 and the ADGM Data Protection Regulations). A group with entities both onshore and in those free zones may have to meet more than one regime, so map which entity holds which data.

Is Microsoft 365 PDPL compliant?

No product makes you compliant by itself. Microsoft provides the controls (data location options, labelling, data loss prevention, retention, audit) and contractual terms. Meeting PDPL requirements depends on how you configure and use them, and on your own policies and records.

Do we have to keep personal data inside the UAE?

The PDPL does not ban transfers outright. It allows cross-border transfers under conditions set in the law, such as adequate protection in the destination country or appropriate safeguards. Sector rules and contracts can be stricter. Knowing where your data actually sits, including in SaaS tools, is the first step.

Can Missan certify that we are PDPL compliant?

No, and you should be wary of anyone who offers that. We help you meet PDPL requirements on the technical side: data mapping in your IT estate, Microsoft 365 configuration, access control, logging, breach readiness and evidence. Legal interpretation belongs with your lawyer or data protection officer.

Do we need a Data Protection Officer?

The law requires one in certain cases, for example where processing involves large volumes of sensitive personal data or systematic monitoring. Many mid-sized firms appoint a named owner even when not strictly required, because someone has to own the register, requests and breaches.

How long does a PDPL technical readiness project take?

For a single-entity company on Microsoft 365 with a handful of line-of-business systems, a data map and the core configuration changes typically take six to ten weeks. Groups with several entities and legacy systems take longer. We give a fixed quote after scoping.

This guide is general information for planning, not legal or tax advice. Regulations and deadlines change; confirm the current position with the official source linked in the text and with your own advisers. Last reviewed 17/10/2026.

Tell us what you need

A short note is enough. We reply within one business day.

4.6★ from 200+ Google reviews We reply within one business day
Add country and company size (optional)

No newsletter and no sales sequence. We only use this to answer you. See our privacy policy. Prefer to talk? +971 6 562 6006 or WhatsApp us

Get a PDPL technical readiness scope

Tell us your entities, systems and Microsoft 365 licences. We scope the data map and configuration work and send a fixed quote. We reply within one business day.