Most organisations aren't breached by anything exotic. One password gets phished, there is no phishing-resistant sign-in behind it, an unpatched laptop gives the attacker a second way in, and a spoofed email finishes the job. The steps below close those doors, in the order I would do them.

Updated October 2026. I first wrote this guide in 2022. Since then Azure AD became Microsoft Entra ID, Microsoft made MFA mandatory for its admin portals, passkeys started replacing SMS and voice codes, and the separate Defender portals merged into one. Every step below is rewritten for what you will actually see in your tenant today.

I focus on cloud security you can switch on quickly, because quick activation gives you instant insight and real numbers to base security decisions on. The threat is out there and it is automated. If you don't believe that, don't enforce anything yet: switch on the insights, use report-only mode, and just watch for a week. The dashboards make the case for you.

What changed since 2022

If you follow older tutorials (including my own earlier version of this one) you'll hit menus that no longer exist. This is the translation table:

In 2022Today
Azure Active DirectoryMicrosoft Entra ID, managed at entra.microsoft.com
Azure AD ConnectEntra Connect Sync, or the lighter Entra Cloud Sync
Security defaults in the Azure portalSecurity defaults in the Entra admin center, or Microsoft-managed Conditional Access policies if you have Entra ID P1 or higher
MFA with SMS, voice call or any codePasskeys and phishing-resistant MFA; Microsoft stops providing SMS and voice codes on 1 February 2027
Microsoft 365 Defender, Defender for Endpoint and Office 365 security portalsOne Microsoft Defender portal (Defender XDR) at security.microsoft.com
Cloud App Security at portal.cloudappsecurity.comDefender for Cloud Apps inside the Defender portal (the classic portal redirects since June 2024)
Endpoint ManagerMicrosoft Intune admin center at intune.microsoft.com
Threat & Vulnerability ManagementDefender Vulnerability Management, part of Exposure Management
Office 365 E5 trialMicrosoft 365 E5 trial, or the Defender Suite add-on for Business Premium
DKIM and SPFSPF + DKIM + DMARC, now expected by Outlook.com from high-volume senders

A How to decrease the risk of an attack on your users

Accounts protected by passwords are the biggest risk in most tenants. Switching on the policies below takes about 4 hours. Moving every user onto a passkey takes a few weeks of gentle nudging, so start that part early.

1. Sync your identities to Microsoft Entra ID ⏱ 1 h · hybrid only

If you still run on-premises Active Directory, you want those identities in Entra ID so that cloud signals such as risky sign-ins and Conditional Access apply to them. There are two tools. Entra Connect Sync is the full sync engine on a Windows Server, with custom rules and multi-forest support. Entra Cloud Sync uses lightweight agents with built-in failover. For a new, simple environment I'd evaluate Cloud Sync first, and keep Connect Sync when you depend on complex rules. Never let both tools manage the same set of objects.

Cloud-only tenant, or users already syncing? Skip to step 2.
Already running Entra Connect Sync? Keep it current. From version 2.5.190.0 the sync engine enforces the newer v2 connector API, and older builds are being retired through October 2026, so an old server can stop working with little warning. Treat the sync server like a domain controller: it can reset anything, so patch it, don't browse from it, and put Defender for Identity on it (step 4).

2. Make MFA non-negotiable: security defaults or Conditional Access ⏱ 1 h

First accept that every password in your organisation has leaked, or will. Microsoft's own numbers say that MFA plus blocking legacy authentication stops more than 99.9% of common identity attacks. Which route you take depends on your licences:

Security defaults
Free · on/off switch
  • MFA registration for all users, MFA for admins at every sign-in
  • Authenticator prompts with number matching
  • Blocks legacy authentication and device code flow
  • MFA for Azure management (portal, CLI, PowerShell)
  • No customisation at all
Best when you have no Entra ID P1/P2 licences.
Conditional Access
Entra ID P1 or higher
  • Included in Microsoft 365 Business Premium, E3 and E5
  • Microsoft-managed policies as a ready-made start
  • Report-only mode, exclusions, per-app and risk-based rules
  • Authentication strengths such as phishing-resistant MFA
Best when you have the licence. Microsoft doesn't recommend security defaults for P1/P2 tenants.

Route 1: security defaults. New tenants often have them on already, and Microsoft may switch them on for older tenants without Conditional Access policies, so check the status first.

1
Sign in to the Microsoft Entra admin center as at least a Conditional Access Administrator.
2
Browse to Entra ID → Overview → Properties and select Manage security defaults.
3
Set Security defaults to Enabled and select Save.
4
Revoke existing sessions with Revoke-MgUserSignInSession so users who are already signed in have to register for MFA right away.
Before you flip the switch: make sure no administrator relies on a legacy-authentication client, and keep every method under Methods available to users enabled in the MFA service settings. Disabling them can lock you out of your own tenant.

Route 2: Conditional Access. Microsoft now ships its own baseline for you:

1
Go to Entra ID → Conditional Access → Policies and look for policies whose names start with Microsoft-managed:. Microsoft adds them in report-only mode and turns them on at least 30 days later, with an email and Message center notice two weeks before.
2
Open each policy's Policy impact tab, then set it to On, Report-only or Off. You can't rename or delete them; duplicate one if you need a variant.
3
Make sure these are covered: block legacy authentication, block device code flow, MFA for admins on the Microsoft admin portals and MFA for all users. With Entra ID P2 add the risk-based ones: MFA and reauthentication for risky sign-ins, and blocking or remediation of high-risk users.
4
Still on security defaults? Disable them first, then immediately enable the managed policies that replace them, so there's no gap.
5
Exclude only your emergency accounts (see below). Nobody else.
Create two emergency (break-glass) accounts. Cloud-only, permanent Global Administrator, excluded from Conditional Access, protected by a long random password stored offline (plus a hardware security key if you can), and with an alert on every sign-in. You only notice you need them on the day everything else is locked.
Mandatory MFA is already here. Microsoft enforces MFA for sign-ins to the Azure portal, the Entra admin center and the Intune admin center; for the Azure portal that reached 100% of tenants in March 2025. Since 1 October 2025 it also covers resource management from the Azure CLI, PowerShell, the mobile app, REST APIs, SDKs and infrastructure-as-code tools. Workload identities such as service principals and managed identities aren't affected.

3. Move to passkeys: phishing-resistant MFA ⏱ half a day + weeks of adoption

A password plus an SMS code can still be phished: the user types both into a fake page and the attacker replays them within seconds. A passkey is bound to the real website through public-key cryptography, so there is nothing to replay. That matters more every year. Microsoft reports that AI-enabled phishing campaigns reach click-through rates of up to 54%, against roughly 12% for traditional ones.

Microsoft is also moving the default. From 1 September 2026 passkeys are the default sign-in experience in Entra ID. Users who are enabled for SMS or voice get passkeys enabled automatically and are prompted to register one at their next MFA sign-in (they can still skip it for now). Here is the calendar for public-cloud tenants:

1 JULY 2026All new Entra tenants block device code flow under security defaults.
1 SEPTEMBER 2026Passkeys become the default. Users with SMS or voice enabled are auto-enabled for passkeys and get the registration prompt. A temporary opt-out runs until February 2027.
LATE OCTOBER – NOVEMBER 2026Users can register a passkey as their very first MFA method, no SMS detour needed (rolling out in phases).
1 FEBRUARY 2027Microsoft-provided SMS and voice authentication ends for most users. Anyone relying only on those must register a passkey to sign in. Accounts aren't disabled and no data is lost.
1 JULY 2027The same retirement applies to Global Administrators and external users.
1
Find the SMS and voice users. In Entra ID → Authentication methods check which users and groups still have SMS or voice enabled, and who has registered nothing stronger.
2
Enable passkeys in the Authentication methods policy and pick the types. Device-bound passkeys (Authenticator passkey, Entra passkey on Windows, FIDO2 security keys) suit admins and high-risk roles. Synced passkeys (iCloud Keychain, Google Password Manager) suit everyone else because adoption is easier.
3
Run a registration campaign so users are prompted to register a passkey during MFA sign-in. Target it at groups, and announce it by mail first so the prompt doesn't look like phishing.
4
Onboard and recover with a Temporary Access Pass, not with a password and a text message.
5
Enforce it. In Conditional Access require the built-in Phishing-resistant MFA authentication strength for admins first, then for everyone once adoption is high.
6
Really need SMS or voice (regulation, shop-floor phones)? Document those user groups and configure a telecom provider well before 1 February 2027. Microsoft suggests finishing at least four weeks ahead.
Dates are for public-cloud tenants and roll out gradually, so your tenant may see changes a little earlier or later. Message center posts MC1426371 and MC1450133 carry the exact timing for your tenant. Passkeys are included in every Entra plan at no extra cost.

4. See user and credential risk: Defender for Identity and Entra ID Protection ⏱ 1–2 h

Once sign-ins are protected, you want to see the attacks that still happen. Defender for Identity watches your on-premises Active Directory (domain controllers, AD FS, AD CS and Entra Connect servers) for what attackers do after they get hold of one password: reconnaissance, Kerberoasting, pass-the-hash, lateral movement. Entra ID Protection (Entra ID P2) scores users and sign-ins for risk in the cloud. Both land in the same incident queue in the Defender portal.

The sensor has changed a lot. Version 3.x is built into the Defender for Endpoint sensor on the server, existing v2 sensors can be migrated from the Defender portal in about 20 minutes without downtime, and it needs Windows Server 2019 or later. Since September 2026 Microsoft is also rolling out automatic activation and automatic Windows auditing to existing customers after a 30-day notice banner (you can opt out), and from October 2026 you can activate v3.x on eligible servers without onboarding them to Defender for Endpoint first.

1
In the Defender portal open Settings → Identities and go to Sensor management.
2
Check that your domain controllers, plus the Entra Connect, AD FS and AD CS servers, run Windows Server 2019 or later.
3
Activate sensor v3.x on them, or migrate v2 sensors that show Ready for migration.
4
Open the identity security dashboard and work through the recommendations first: stale accounts, service accounts in privileged groups, accounts in the built-in Operator groups. They're free wins that shrink the attack surface before any alert fires.
5
In Entra ID → Protection review risky users and risky sign-ins. With P2, let the risk-based policies from step 2 act on them automatically.

5. Try the whole stack in a trial ⏱ 30 min

Defender XDR becomes powerful when the products share signals, and you can see that in your own tenant before you buy anything. A Microsoft 365 E5 trial gives you 25 user licences for one month. In the Microsoft 365 admin center go to Billing → Purchase services, choose Microsoft 365 E5 and select Start free trial, then assign the licence under Users → Active users.

On Microsoft 365 Business Premium (up to 300 users) you already have Defender for Business and Entra ID P1. The Defender Suite for Business Premium add-on adds Entra ID P2, Defender for Endpoint Plan 2, Defender for Office 365 Plan 2 and Defender for Cloud Apps. Check the current price before you commit.

Where did Cloud App Security go? The classic portal at portal.cloudappsecurity.com was retired in June 2024 and redirects to the Defender portal. Defender for Cloud Apps alerts now appear in Incidents & alerts, and app discovery lives under Cloud apps at security.microsoft.com.

B How to protect your organization from software exploits

Software can carry malware, and badly patched computers raise the risk of being attacked from the inside once someone has a foothold. Seeing the exposure takes a few hours. Working through it takes continuous attention, but start now and be pragmatic: the aim is a shorter list every week, not a perfect one on day one.

1
Enrol every device in Microsoft Intune at intune.microsoft.com. Hybrid-joined or cloud-joined doesn't matter for the sake of security (it matters for the future, I know). Phones and Macs count too.
2
Onboard them to Defender for Endpoint. In the Defender portal turn on the Microsoft Intune connection (Settings → Endpoints → Advanced features), then create an onboarding policy in Intune under Endpoint security → Endpoint detection and response. On Business Premium, Defender for Business includes the same endpoint protection, vulnerability management and a setup wizard.
3
Harden before you patch. Turn on tamper protection and cloud-delivered protection, and run attack surface reduction rules in audit mode first. Enforce the rules that stay quiet.
4
Work the recommendations. In the Defender portal open Exposure management → Vulnerability management, go to the recommendations and start with the most critical advice. Patch Windows, patch third-party apps.
5
Hand the work to Intune. Submit a remediation request from a recommendation. It creates a security task under Endpoint security → Security tasks in Intune. The Intune admin accepts it, deploys the update or the setting, and completes the task, which updates the status in both portals.
6
Zoom out once a week. Exposure Management shows your Secure Score, security initiatives and attack paths: the routes an attacker could take from an exposed device or account to your critical assets. Fixing one node on a path often closes several risks at once.
My rule of thumb: Windows quality updates within a week through update rings, third-party apps weekly, and anything exploited in the wild the same day. A short written cadence beats a perfect tool nobody follows.
security.microsoft.com›Exposure management›Vulnerability management›Recommendations

C Protect your organization from targeted phishing attacks

Phishing is still the number one attempt to get control of your organisational infrastructure. Don't let an actor in through a stupid e-mail, and don't let anyone send one in your name.

1
Publish SPF. For a domain that only sends through Exchange Online the record is a single TXT entry. Add every other legitimate sender (newsletter tool, CRM) before you set -all.
DNS · TXT on yourdomain.comv=spf1 include:spf.protection.outlook.com -all
2
Activate DKIM for every custom domain. In the Defender portal go to Email & collaboration → Policies & rules → Threat policies → Email authentication settings → DKIM, select the domain, create the keys, publish the two CNAME records it shows (selector1 and selector2), then switch signing on.
3
Add DMARC as a TXT record on _dmarc.yourdomain.com. Start in monitoring mode, read the reports, fix the senders that fail, then tighten to p=quarantine and finally p=reject.
DNS · TXT on _dmarc.yourdomain.comv=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com
Do this for every domain you own, including parked domains and subdomains that never send mail. For your .onmicrosoft.com domain SPF and DKIM are preconfigured, but the DMARC record is still on you. And it is no longer optional for mail you send to consumers: Outlook.com rejects mail from high-volume senders (5,000 or more messages) that lack SPF, DKIM and DMARC, with error 550 5.7.515.
4
Turn on the Standard preset security policy for all recipients (Threat policies → Preset security policies). Microsoft keeps tuning it as the threat landscape changes. Built-in protection is on by default but only basic; Standard adds full Safe Links, Safe Attachments and anti-phishing. Use Strict for admins, finance and executives.
5
Add impersonation protection entries (your executives and your own domains) and tag up to 250 priority accounts, who get extra heuristics. Check the result later with the configuration analyzer.
6
Make reporting easy. Enable the built-in Outlook Report button and send reports to a reporting mailbox, to Microsoft, or both. When in doubt use block entries rather than allow entries: allow entries can't override malware or high-confidence phishing verdicts anyway.
7
Train, don't just filter. With Defender for Office 365 Plan 2 run attack simulation training: one simulation a quarter, followed by short training for whoever clicked.
8
Close the consent-phishing door. Restrict end-user consent so users can't hand a malicious app access to their mailbox. The setting is in Baseline Security Mode (chapter D).
Licensing in one line: Exchange Online Protection comes with every Microsoft 365 subscription that has cloud mailboxes. Defender for Office 365 Plan 1 is part of Business Premium; Plan 2 comes with E5 and the Defender Suite and adds attack simulation training, user tags and deeper investigation.

D Don't make exceptions and take insights seriously

In 2022 this chapter told you to watch two portals. Today there is one place for security work and three for configuration:

security.microsoft.com
Microsoft Defender (XDR)
Look here daily. Incidents & alerts, Identities, Cloud apps, Email & collaboration, Exposure management and Secure Score.
entra.microsoft.com
Microsoft Entra
Conditional Access, authentication methods, Identity Protection and the sign-in logs.
intune.microsoft.com
Microsoft Intune
Devices, update rings, endpoint security policies and the security tasks coming from Defender.
admin.microsoft.com
Microsoft 365 admin center
Licences, trials and Baseline Security Mode.

Baseline Security Mode: the shortcut I wish we had in 2022

Baseline Security Mode bundles the hardening settings that used to need PowerShell and a long reading list. It covers Microsoft 365 apps, SharePoint and OneDrive, Teams, Exchange Online and Entra, and it is available on all Microsoft 365 subscriptions.

admin.microsoft.com›Settings›Org settings›Security & privacy›Baseline Security Mode

Every setting has an impact report. Enable a setting when the report shows zero impact; when it shows dependencies, fix those first. The ones I'd look at first are phishing-resistant MFA for privileged admins, blocking legacy authentication flows, blocking new password credentials on apps, and restricting end-user consent. Be careful with disabling organisation-wide Exchange Web Services (EWS): it can break Power Query connectors, cross-tenant calendar sharing, MailTips and some add-ins, so read that impact report twice.

No exceptions

Every exclusion is a hole the attacker finds first. Exclude your two emergency accounts and nobody else. When an application breaks under a policy, fix the application: move it to OAuth and modern authentication, give it a managed identity, or send its mail through a connector locked to its IP address. Put an expiry date on every "temporary" exception, and review the list once a quarter.

The weekly 30-minute review

Protection that nobody looks at slowly stops working. Put these five steps in the calendar, same time every week:

1
Incidents: triage the new incidents in the Defender portal. Close the noise, escalate the rest.
2
Exposure: pick the top three Secure Score and vulnerability recommendations and assign an owner to each.
3
Identity: look at risky users, risky sign-ins, new authentication-method registrations, and any Conditional Access policy that is still report-only.
4
Devices: check the open security tasks in Intune and the patch status of the oldest devices.
5
Mail: go through the user-reported messages and the spoof intelligence insight.

✓ Your checklist

Tick items off as you go. Your progress is saved in this browser only; nothing is sent anywhere.

Progress
0 / 14

Take care and stay safe.

i Sources

I checked the facts and dates in this guide against Microsoft's own documentation in October 2026. Features, names and dates keep moving, so verify anything with a date on it in your own Message center.

❯ Frequently Asked Questions

Frequently Asked Questions

Is Azure AD the same thing as Microsoft Entra ID?

Yes. Azure Active Directory was renamed Microsoft Entra ID in 2023. It is the same service and you manage it at entra.microsoft.com. Older documentation, scripts and videos that say "Azure AD" mean Entra ID.

Should I use security defaults or Conditional Access?

If you have no Entra ID P1 or P2 licence, use security defaults: they are free and switch on MFA, block legacy authentication and protect admins. If you have Entra ID P1 or higher (it is included in Microsoft 365 Business Premium, E3 and E5), use Conditional Access, starting with the Microsoft-managed policies. Microsoft doesn't recommend security defaults for P1/P2 tenants because they can't be customised.

How do I enable security defaults today?

Sign in to the Microsoft Entra admin center as at least a Conditional Access Administrator, go to Entra ID → Overview → Properties, select Manage security defaults, set it to Enabled and save. Revoke existing sessions afterwards so signed-in users have to register for MFA, and first check that no admin depends on a legacy-authentication client.

What are Microsoft-managed Conditional Access policies and do I have to do anything?

They are baseline policies Microsoft adds to your tenant, for example blocking legacy authentication, blocking device code flow, and requiring MFA for admins and for all users. Each one starts in report-only mode and Microsoft turns it on at least 30 days later, with notice two weeks before. You can set each to On, Report-only or Off and exclude your emergency accounts, but you can't rename or delete them. Review the Policy impact tab and decide before Microsoft does.

Is MFA mandatory for Microsoft admin portals?

Yes. Microsoft enforces MFA for sign-ins to the Azure portal, the Microsoft Entra admin center and the Intune admin center (the Azure portal reached 100% of tenants in March 2025). Since 1 October 2025 it also applies to resource management from the Azure CLI, PowerShell, REST APIs, SDKs and infrastructure-as-code tools. Workload identities such as service principals and managed identities are not affected.

What happens to SMS and voice MFA?

From 1 September 2026 passkeys are the default sign-in method in Entra ID, and users with SMS or voice enabled are prompted to register a passkey. On 1 February 2027 Microsoft stops providing SMS and voice authentication for most users, and on 1 July 2027 for Global Administrators and external users. Organisations that still need telephony can configure a paid telecom provider through the Microsoft Security Store. Users who rely only on SMS or voice must register a passkey to keep signing in; accounts are not disabled. These dates apply to public-cloud tenants.

Do I still need Entra Connect if I'm already a Microsoft 365 customer?

Only if you have on-premises Active Directory that you want to keep in sync. Cloud-only tenants need no sync tool. If you do sync, evaluate Entra Cloud Sync for simple new setups, and keep Entra Connect Sync for complex rules, updated to version 2.5.190.0 or later because older builds are being retired through October 2026.

What does Microsoft Defender for Identity monitor, and what changed?

It watches on-premises Active Directory (domain controllers, AD FS, AD CS and Entra Connect servers) for attack techniques such as reconnaissance, Kerberoasting, pass-the-hash and lateral movement, and shows them next to your cloud identity alerts in the Defender portal. The current sensor is version 3.x, built into the Defender for Endpoint sensor, needs Windows Server 2019 or later, and v2 sensors can be migrated from the portal without downtime.

Do I need to buy Microsoft 365 E5 to try Defender XDR?

No. A Microsoft 365 E5 trial gives you 25 user licences for one month, which is enough to switch on Defender for Identity, Defender for Endpoint, Defender for Office 365 and Defender for Cloud Apps. Business Premium customers already have Defender for Business and can add the Defender Suite for Business Premium to get Entra ID P2, Defender for Endpoint Plan 2, Defender for Office 365 Plan 2 and Defender for Cloud Apps.

What's the difference between Defender for Identity, Endpoint, Office 365 and Cloud Apps?

Defender for Identity watches on-premises Active Directory and identity signals, Defender for Endpoint watches devices (malware, vulnerabilities, attacks in progress), Defender for Office 365 watches email and collaboration tools for phishing and malicious links or attachments, and Defender for Cloud Apps watches SaaS usage and anomalies. Defender XDR correlates all four into single incidents in one portal.

How do I reduce the risk from unpatched software?

Enrol your devices in Microsoft Intune, onboard them to Defender for Endpoint, then open Exposure management → Vulnerability management in the Defender portal and work through the most critical recommendations. Submit a remediation request from a recommendation to create a security task for the Intune admin, who deploys the update or setting and completes the task.

Do I really need SPF, DKIM and DMARC, or is one enough?

Set up all three, in that order, on every domain you own, including parked domains. SPF and DKIM prove who may send for your domain, and DMARC tells receivers what to do when they fail and sends you reports. Outlook.com now rejects mail from high-volume senders (5,000 or more messages) without SPF, DKIM and DMARC, using error 550 5.7.515. Start DMARC at p=none, then move to quarantine and reject.

Where do I monitor everything after switching it on?

In one place: the Microsoft Defender portal at security.microsoft.com, which holds incidents, identity, cloud apps, email and exposure management. Configure identity in the Entra admin center, devices in Intune, and Baseline Security Mode in the Microsoft 365 admin center. The old portal.cloudappsecurity.com was retired in June 2024 and redirects to the Defender portal.

How long does it take to implement all this?

The identity policies (sync, MFA, Conditional Access, Defender for Identity) take about four hours to switch on. Device onboarding and the first round of patching takes a few days. DMARC takes weeks because you want to read the reports before you enforce it, and moving every user to a passkey takes a few weeks of campaigns. After that, plan 30 minutes a week for review.

If I can only do one thing today, what should it be?

Require MFA for every account and block legacy authentication, through security defaults or the Microsoft-managed Conditional Access policies. Then register a passkey or hardware security key for every administrator.