Microsoft Secure Score: What It Tells You and How to Raise It

Microsoft 365 and CopilotPublished Last reviewed November 20269 min read

Short answer

Microsoft Secure Score shows how many of Microsoft’s recommended security settings your tenant has turned on, not how likely you are to be breached. Small and midsize firms should raise it in a risk based order: secure admin accounts, require MFA for everyone, block legacy authentication, move admins to phishing resistant MFA, apply Defender for Office 365 preset policies, then enforce Intune device compliance.

Check where you stand: take the Microsoft 365 security check. About two minutes, no email needed.

Update, November 2026

Microsoft has since made passkeys the default sign in method starting September 1, 2026 and will retire Microsoft provided SMS and voice MFA on February 1, 2027 (July 1, 2027 for Global Administrators and external users), so the move to phishing resistant MFA described here now has a deadline. Security defaults in Microsoft Entra tenants created on or after July 1, 2026 also block device code flow. Ethereum Tech has since taken one tenant’s Microsoft Secure Score from 28% to 68% in six weeks; your starting point and timing will differ.

Microsoft Secure Score is a useful checklist and a poor scoreboard. It tells you which recommended settings your tenant has turned on, not how close you are to a breach. For a small or midsize firm, the better plan is to fix the few controls attackers actually test, in a deliberate order, and let the score follow.

What does Microsoft Secure Score actually measure?

Secure Score measures how many recommended security actions you have completed across Microsoft 365, shown as points and a percentage. Microsoft states plainly that it is not an absolute measure of how likely your systems or data are to be breached.

You find it in the Microsoft Defender portal, with recommendations grouped into identity, device, apps and data. Each action is worth 10 points or less. Most are binary, so you get all the points or none, but some pay out in proportion: if half your users are covered by multifactor authentication, you get half the points for that action. Completed changes usually take 24 to 48 hours to show up.

The part that misleads people is the denominator. Secure Score lists the full set of recommendations for a product regardless of the license you own, so a firm on Microsoft 365 Business Standard is scored against Defender for Office 365 settings it cannot turn on. Open the Include options on the score tile and add the Current license score and Achievable score views. Those show what is within reach with the licenses you pay for and the risks you have accepted, a more honest target than the headline percentage.

Why can a higher Secure Score still leave a small firm exposed?

Because the points are spread across hundreds of settings, while most small business compromises come through a few doors. A tenant can collect plenty of points in Exchange, SharePoint and Teams and still fall to a stolen password and a relayed MFA prompt.

Microsoft ranks recommended actions by points remaining, implementation difficulty, user impact and complexity. That ranking favors what is convenient to change, which suits a dashboard but not a risk plan. In the tenants we review, the incidents that hurt start with identity: a stolen session, an old protocol that skips MFA, or a Global Administrator account that doubles as somebody’s daily mailbox.

In what order should you raise your Secure Score?

Secure the administrator accounts, require MFA for everyone, block legacy authentication, move admins to phishing resistant MFA, tighten email protection, then bring devices under management. That sequence closes the paths attackers use before it chases points.

  1. Get admin accounts in order before you lock anything down. Create two cloud only emergency access accounts and exclude them from Conditional Access, keep Global Administrator to fewer than five people as Microsoft recommends, give admins accounts that are separate from their everyday mailbox, and use narrower roles such as Exchange Administrator where that is enough. If you have Microsoft Entra ID P2, put those roles behind Privileged Identity Management.
  2. Require MFA for every user. If your plan does not include Entra ID P1 (Business Basic and Business Standard do not), turn on security defaults, which also earns full points for three recommendations worth 26 points between them. If you have P1, which Microsoft 365 Business Premium includes, use Conditional Access instead, start from the Microsoft managed policies or templates, and run each new policy in report only mode before you enforce it. The two cannot run together, so turn security defaults off when Conditional Access replaces it.
  3. Block legacy authentication. IMAP, POP3 and SMTP AUTH with basic authentication cannot do MFA, which is exactly why attackers use them. Check the Entra sign in logs for legacy clients first. Scanners and apps that send mail through SMTP AUTH are the usual holdouts, and Microsoft’s January 2026 timeline keeps basic authentication for SMTP AUTH working through December 2026 before turning it off by default for existing tenants. Plan those fixes now.
  4. Move admins to phishing resistant MFA. Push approvals and codes do not stop adversary in the middle (AiTM) kits that relay the sign in and steal the session token, and we have run a full Microsoft 365 incident response for exactly that kind of token theft. Have admins register passkeys on FIDO2 security keys or in Microsoft Authenticator, or set up Windows Hello for Business, then add a Conditional Access policy for admin roles that requires the built in phishing resistant MFA authentication strength, excluding the emergency access accounts.
  5. Tighten Defender for Office 365, which Business Premium includes at Plan 1. Apply the Standard or Strict preset security policies instead of tuning each policy by hand, and stop automatic forwarding to outside addresses, which Secure Score lists as “Ensure all forms of mail forwarding are blocked and/or disabled”.
  6. Bring devices under Intune. Build compliance policies for disk encryption, minimum operating system version and Microsoft Defender for Business onboarding, set Intune to treat devices without an assigned compliance policy as failing, then require a device that passes compliance in Conditional Access, starting with admins.

Which Secure Score recommendations can you skip or accept as risk?

You can skip some, as long as the decision is written down, owned by a named person and reviewed on a schedule. Secure Score supports this through recommendation statuses.

Mark an action Risk accepted when you have decided not to do it; it earns no points. Mark it Resolved through third party or Resolved through alternate mitigation when another tool or control genuinely covers it; those statuses do earn the points, and Microsoft notes it has no visibility into whether that mitigation is complete. Use Planned only when a real date is attached. Candidates we often see:

  • Sign in risk and user risk policies in a tenant that runs security defaults. Microsoft itself recommends marking these as resolved through alternate mitigation instead of layering them on top.
  • Wiping a phone after repeated failed sign in attempts when employees own the phones. Intune app protection policies usually do that job with less friction.
  • Blocking users from consenting to any third party app, when you already run the admin consent workflow and someone reviews the requests. Record the workflow as the mitigation.
  • Items a separate email filter or endpoint product handles, but only where that product enforces the same control and you can show it.

What you should not do is mark items as mitigated to reach a target number. An auditor who asks for the evidence behind a status will find the gap, and so will an attacker.

How does Secure Score map to what insurers and auditors ask for?

Loosely. Neither a cyber insurance underwriter nor an auditor accepts a percentage as evidence, but the recommendations behind the score line up well with the questions they do ask.

Insurance applications keep asking about MFA, legacy protocols, admin accounts, email filtering and endpoint protection, and the frameworks state the identity part formally. CMMC Level 2 practice IA.L2-3.5.3 requires multifactor authentication for local and network access to privileged accounts and for network access to nonprivileged accounts. The HIPAA Security Rule standard for person or entity authentication, 45 CFR 164.312(d), requires procedures to verify the identity of anyone seeking access to electronic protected health information. SOC 2 auditors test logical access controls across the whole report period, not on the day you take a screenshot.

What they askSecure Score actions that helpEvidence that settles it
Is MFA enforced for email, remote access and admins?MFA for all users, MFA for admin roles, phishing resistant strength for adminsConditional Access policy export, MFA registration report, sign in logs
Is legacy authentication blocked?Block legacy authenticationThe blocking policy plus a sign in log query showing no legacy clients
Are privileged accounts limited and separate?Admin account and role recommendationsRole assignment export and the emergency access account procedure
Is email filtered for phishing and malware?Safe Links, Safe Attachments, phishing protection, forwarding blockPreset security policy assignments and configuration analyzer results
Are endpoints managed and running EDR?Intune and Defender device recommendationsIntune compliance report and the Defender device inventory

Keep Secure Score history as supporting evidence that posture improved over time, and keep the real proof in configuration exports and logs. When an insurer asks about MFA, answer the exact question asked, because an inaccurate application answer can cost you more at claim time than a low score. Our cyber insurance evidence work and CMMC compliance work both start from that evidence rather than the dashboard.

For an outside view of which recommendations matter in your tenant, a Microsoft 365 security assessment covers it, or you can begin with the short readiness check.

You can also book a 30 minute call and we will walk through your Secure Score and the order of work with you.

Frequently asked questions

What is a good Microsoft Secure Score for a small business?

There is no passing grade. Compare your score with your own achievable score, which reflects the licenses you own and the risks you have accepted, and track the trend. A tenant with MFA everywhere, legacy authentication blocked and phishing resistant admin sign in is in better shape than one with a higher number built on low impact settings.

Why did my Secure Score drop when nobody changed anything?

Microsoft adds new recommendations over time, which can enlarge the total available points. Partial credit actions also move with your user and device counts, so new hires who have not registered for MFA or new devices that are not onboarded lower the points for those actions. License changes can shift the score as well.

Who can change recommendation statuses in Secure Score?

Security Administrator, Exchange Administrator and SharePoint Administrator roles can edit statuses and notes. Global Reader, Security Reader and several helpdesk roles have read only access. You can also grant narrower access with a Microsoft Defender unified role based access control custom role that includes the Exposure Management read or manage permission.

Does Secure Score cover tools outside Microsoft 365?

Partly. Through Microsoft Defender for Cloud Apps it includes recommendations for products such as Okta, Salesforce, ServiceNow, Zoom, GitHub and Docusign. For anything else, you can mark a Microsoft recommendation as resolved through a third party when another product truly enforces the control, which keeps the score closer to your real posture.

Keep reading

Related guides

Have a question this raised?

Bring it to a 30 minute call and leave knowing where you stand and what comes next.

Book a 30 minute call

(786) 577-9743sales@ethereumtech.ai

Or take the two minute starting point check