Microsoft 365 tenant security baseline: security defaults vs Conditional Access
A new or inherited Microsoft 365 tenant is not "done" when users can sign in. Before you customize policies, establish a baseline: multifactor authentication, a block on legacy authentication, protected admin access, emergency accounts, email authentication, and working audit logs. The first decision is whether that identity baseline comes from security defaults or from Conditional Access.
What "baseline" means here
This is not a replacement for a full quarterly audit. It is the first-pass set of controls to turn on (or confirm) so the tenant is not left open while you do deeper work. Microsoft documents two official starting points for identity:
- Security defaults in Microsoft Entra ID, which are included at no extra cost.
- Conditional Access, which needs Microsoft Entra ID P1 (included in plans such as Microsoft 365 Business Premium and Microsoft 365 E3) and is the path Microsoft recommends if you already have those licenses.
You can use security defaults or Conditional Access, but not both at the same time. Microsoft's Conditional Access planning guidance and its multifactor authentication for Microsoft 365 article both state that enabling Conditional Access policies prevents you from using security defaults, so you must recreate the same protections in Conditional Access before you turn security defaults off.
Start with security defaults if you do not have Entra ID P1
Security defaults are a preconfigured, all-or-nothing baseline. According to Microsoft's security defaults documentation, they:
- Require all users to register for multifactor authentication.
- Require administrators to do multifactor authentication.
- Require users to do multifactor authentication when Microsoft determines it is necessary (for example, a new device or unusual sign-in).
- Block legacy authentication protocols that cannot perform MFA.
- Block device code flow.
- Protect privileged activities such as access to the Azure portal.
Microsoft states that, based on its learnings, more than 99.9% of common identity-related attacks of this type are stopped by using multifactor authentication and blocking legacy authentication. That figure is Microsoft's published claim; treat it as a reason to enable the controls, not as a guarantee for your tenant.
Tenants created on or after 22 October 2019 may already have security defaults enabled. Microsoft also describes a 24-hour grace period on new tenants before the protections are enforced, so a brand-new tenant is not an excuse to leave MFA off.
Security defaults are the right baseline when you are on the free tier of Microsoft Entra ID, or when the organization is not ready to design and maintain Conditional Access policies. You cannot carve out exceptions, require phishing-resistant MFA only for admins, or stage a rollout by group. If you need those, you need Conditional Access.
Move to Conditional Access when you have Entra ID P1 or P2
Microsoft's security defaults article is direct: if you have Microsoft Entra ID P1 or P2 licenses, security defaults are probably not right for you. Conditional Access lets you write if-then policies (user, app, device, location, risk) and test them in report-only mode before enforcement.
Do the switch in this order, not the reverse:
- Confirm at least two emergency access (break-glass) accounts exist, are cloud-only, and will be excluded from policies that could block sign-in. See Microsoft Learn, Manage emergency access accounts in Microsoft Entra ID.
- Create the Conditional Access policies that replace security defaults, starting from Microsoft's Secure foundation templates. Leave them in report-only mode.
- Review sign-in logs and, if you use Azure Monitor, the Conditional Access insights workbook, until you understand who would be prompted or blocked.
- Turn the policies on, then disable security defaults. Do not disable security defaults first and "add policies later."
Our separate guide walks through a practical starter policy set for a small tenant.
Identity items the baseline should also include
Security defaults and Conditional Access cover the sign-in path. A first-pass tenant baseline still needs a short list of related identity checks:
- Emergency access accounts. At least two, on the
*.onmicrosoft.comdomain, with phishing-resistant authentication, permanent active Global Administrator, and alerts on every sign-in. - Few Global Administrators. Microsoft recommends fewer than five. Use role-specific roles for daily work.
- Restricted user consent. Limit user consent to verified publishers and low-risk permissions, and turn on the admin consent request workflow. Consent phishing is a common way a mailbox is emptied without a password being stolen.
- Guest and partner access inventoried. Especially on a tenant you just inherited from another provider. See our previous-MSP handover checklist.
Email, sharing and logs belong in the same first pass
Identity policies will not stop a spoofed invoice if the domain has no DMARC record, and they will not tell you what happened if audit logging was never confirmed.
- Publish SPF for every sending domain, enable DKIM for each custom domain, and publish a DMARC record with a plan to move from
p=nonetoquarantineorreject. Our free DMARC record generator builds the TXT record. - Apply Exchange Online preset security policies (Standard or Strict) or an equivalent set of anti-phishing, anti-spam and anti-malware policies. Some protections need Defender for Office 365, which is included in Microsoft 365 Business Premium.
- Block automatic external forwarding in the outbound anti-spam policy, and document any exceptions. See Microsoft's guidance on outbound spam policies and external forwarding.
- Set SharePoint and OneDrive external sharing to the most restrictive level the business accepts, and make "Specific people" the default link type.
- Confirm the unified audit log is actually ingesting events by running a search for the last 24 hours. Microsoft Secure Score in the Microsoft Defender portal is a useful progress view, but a score is not evidence that a control works — verify the setting. See Microsoft Secure Score.
Make the baseline repeatable
Write down where you checked, what you saw, and the date. Then schedule a quarterly pass so settings do not drift. Our quarterly Microsoft 365 security audit checklist covers the deeper control set, and the Tenant Security Audit Kit packages 50 controls with where-to-verify paths, licensing notes and scoring in one Excel workbook.