Leadership guide · for CIOs and IT directors
Microsoft 365 security baseline for UAE companies: Defender, Intune, Conditional Access and Copilot readiness
Most Microsoft 365 tenants we review have paid-for security features switched off. This is the baseline we put in place for UAE companies of 50 to 2,000 users, in the order we do it, with the licence each control needs.
Why a baseline, and why in this order
Attackers rarely break Microsoft 365 itself. They sign in as one of your users with a phished or reused password, then read mail, set up forwarding rules and send fake payment instructions to your customers. That is why identity comes first. Device and email controls reduce how often a user is tricked; data controls limit what leaks when they are. Copilot changes none of this, but it makes oversharing easier to find for anyone who goes looking.
UAE-specific pressure comes from three places. Customers and banks send security questionnaires. Cyber insurers ask about MFA and EDR before quoting. And the UAE PDPL expects appropriate technical measures for personal data. A documented baseline answers all three. The UAE Cybersecurity Council publishes national guidance worth reading alongside this.
Layer 1: identity (Microsoft Entra ID)
If you have no Entra ID P1 licences, turn on security defaults today. If you do, build Conditional Access policies instead:
- Require MFA for all users, all cloud apps. Prefer the Microsoft Authenticator app or passkeys over SMS (see Microsoft's authentication methods).
- Block legacy authentication protocols.
- Require phishing-resistant MFA for administrator roles.
- Require a compliant or hybrid-joined device for access to mail and files (once Intune is in place).
- Block or challenge sign-ins from countries you never operate in.
- Two break-glass admin accounts, excluded from policies, with long passwords stored offline and sign-in alerts.
Also: remove standing Global Administrator rights from day-to-day accounts, and review guest accounts every quarter.
Layer 2: devices (Microsoft Intune)
Intune lets you set rules for Windows, macOS, iOS and Android devices and check them before granting access.
- Enrol company laptops with Windows Autopilot so new devices arrive configured.
- Compliance policy: disk encryption on, supported OS version, firewall on, EDR running.
- Windows Update rings so patches land in a controlled order.
- App protection policies for personal phones: company data stays in managed apps and can be wiped without touching personal photos.
- Local admin rights removed from standard users.
Layer 3: email and endpoints (Microsoft Defender)
Microsoft Defender XDR brings email, endpoint and identity signals together. The baseline:
- Defender for Office 365: preset protection policies, Safe Links, Safe Attachments, impersonation protection for executives and finance staff.
- SPF, DKIM and DMARC published and monitored for every domain you send from. Our email security checker tests this.
- Block automatic forwarding to external addresses.
- Defender for Business or Defender for Endpoint on every laptop and server, with attack surface reduction rules on.
- Someone reading the alerts. Unread alerts are the most common failure we see. If nobody watches out of hours, look at managed detection and response.
Layer 4: data (Microsoft Purview)
- A short set of sensitivity labels, with default labelling on new documents in sensitive libraries.
- DLP policies for Emirates ID, passport, IBAN and card numbers.
- External sharing on SharePoint and OneDrive limited to named guests, with expiry on links.
- Retention policies that match your records schedule.
- Unified audit logging on.
Copilot readiness
Microsoft states that Copilot only accesses data the individual user has permission to see (see Copilot data, privacy and security). That is the right design, and it is also why readiness matters: years of "share with everyone" links and broad groups mean users can already open far more than they realise. Copilot just makes it quick to find.
- Report on sites and files shared with "Everyone" or via anonymous links. Fix the worst first: HR, finance, board, legal.
- Apply sensitivity labels to the sensitive libraries.
- Archive stale sites and Teams that nobody owns.
- Pilot Copilot with a group of 10 to 30 users with clear use cases, then expand.
Our Copilot rollout guide and Copilot licensing guide cover the rest.
Baseline checklist
- MFA enforced for 100% of users; legacy authentication blocked.
- Phishing-resistant MFA for admins; two break-glass accounts.
- No day-to-day accounts with Global Administrator rights.
- All company devices enrolled in Intune and compliant.
- Defender for Office 365 preset policies on; external forwarding blocked.
- SPF, DKIM and DMARC at enforcement on all sending domains.
- EDR on every endpoint and server; alerts monitored.
- Sensitivity labels and DLP for personal and financial data.
- External sharing restricted; oversharing report reviewed.
- Audit logging on; Secure Score reviewed monthly.
- Independent backup of Exchange, SharePoint, OneDrive and Teams data.
How to roll it out without locking people out
Every policy starts in report-only mode, then applies to IT, then a pilot department, then everyone. Users get a short notice before MFA registration and a help number on the day. Exceptions (a shared scanner mailbox, a legacy app) are documented with an owner and an end date rather than quietly excluded forever. We use staged migrations with a way back for device enrolment too, so a bad policy can be rolled back in minutes.
Where Missan helps
We have supported Microsoft environments in the UAE for 22+ years and are a Microsoft Solutions Partner for AI Business Solutions. We assess your tenant against this baseline, fix the gaps in priority order, deploy Intune and Defender, clean up oversharing before Copilot, and can watch the alerts afterwards. If you leave, your Microsoft tenant and accounts stay in your name. Start with the Microsoft 365, Copilot and Defender page or a free health check.
Download the checklist (PDF)
Microsoft 365 security baseline checklist, ready to print
The checklist from this guide on one or two A4 pages, with tick boxes, for your next planning meeting.
Related Missan services
- Microsoft 365, Copilot and Defender
- Managed cybersecurity and MDR
- Microsoft 365 licence optimiser
- Cybersecurity readiness scorecard
Frequently asked questions
Which Microsoft 365 licence do we need for this baseline?
Conditional Access needs Microsoft Entra ID P1, which is included in Microsoft 365 Business Premium, E3 and E5. Intune is in the same plans. Business Premium includes Defender for Business and is capped at 300 users; above that, E3 with Defender add-ons or E5 is the usual route. Check your current mix with our licence optimiser before buying more.
Are security defaults enough?
Security defaults are a sensible free starting point: they require MFA registration and block legacy authentication. They are all-or-nothing, so they do not handle exceptions, trusted devices or risk-based rules. Once you have Entra ID P1, Conditional Access policies replace them.
Will Copilot expose confidential files to the wrong people?
Copilot only uses content the signed-in user already has permission to access. The risk is that many users already have access to more than they should, through old sharing links and broad groups. Fixing oversharing before you roll Copilot out is the main readiness task.
How long does it take to put this baseline in place?
For 100 to 500 users, identity and email controls usually take two to four weeks, device enrolment four to eight weeks depending on how many devices are unmanaged, and data controls run alongside. We roll changes out in rings, starting with IT, so nobody is locked out on day one.
Do we still need a separate antivirus or EDR product?
If you are licensed for Defender for Business or Defender for Endpoint and it is properly deployed, many companies drop the separate product. Some keep a third-party EDR for operational reasons. Running two full agents on one device is rarely a good idea; decide which one leads.
What happens to our tenant if we stop working with Missan?
If you leave, your Microsoft tenant and accounts stay in your name. We document every policy we configure and hand over admin access in an orderly way.
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.
See how your tenant compares to this baseline
Our free IT health check includes a Microsoft 365 security review against these controls. You get a written list of gaps in priority order. We reply within one business day.