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.
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 2022 | Today |
|---|---|
| Azure Active Directory | Microsoft Entra ID, managed at entra.microsoft.com |
| Azure AD Connect | Entra Connect Sync, or the lighter Entra Cloud Sync |
| Security defaults in the Azure portal | Security 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 code | Passkeys 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 portals | One Microsoft Defender portal (Defender XDR) at security.microsoft.com |
| Cloud App Security at portal.cloudappsecurity.com | Defender for Cloud Apps inside the Defender portal (the classic portal redirects since June 2024) |
| Endpoint Manager | Microsoft Intune admin center at intune.microsoft.com |
| Threat & Vulnerability Management | Defender Vulnerability Management, part of Exposure Management |
| Office 365 E5 trial | Microsoft 365 E5 trial, or the Defender Suite add-on for Business Premium |
| DKIM and SPF | SPF + 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.
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:
- 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
- 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
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.
Revoke-MgUserSignInSession so users who are already signed in have to register for MFA right away.Route 2: Conditional Access. Microsoft now ships its own baseline for you:
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.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:
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.
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.
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.
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.
-all._dmarc.yourdomain.com. Start in monitoring mode, read the reports, fix the senders that fail, then tighten to p=quarantine and finally p=reject..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.
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:
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.
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:
✓ Your checklist
Tick items off as you go. Your progress is saved in this browser only; nothing is sent anywhere.
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.
- Security defaults in Microsoft Entra ID · Microsoft Learn
- Microsoft-managed Conditional Access policies · Microsoft Learn
- Azure mandatory multifactor authentication, phase 2 · Azure blog
- Passkeys are the default authentication method in Entra ID · Microsoft Security blog, 13 July 2026
- What's new in Microsoft Defender for Identity · Microsoft Learn
- Set up your Microsoft Defender XDR trial · Microsoft Learn
- Remediate vulnerabilities with Intune and Defender Vulnerability Management · Microsoft Learn
- Microsoft Security Exposure Management: what's new · Microsoft Learn
- Microsoft Defender for Business · Microsoft
- Defender for Office 365 deployment guide · Microsoft Learn
- Fix NDR error 550 5.7.515 in Outlook.com (high-volume sender requirements) · Microsoft Support
- Baseline Security Mode settings · Microsoft Learn
- Archive of past updates for Defender for Cloud Apps (classic portal redirect) · Microsoft Learn
- Entra Connect Sync 2.5.190.0 and the AAD Connector v1 API deprecation · DirTeam
❯ 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.