Microsoft Secure Score is a percentage that shows how many of Microsoft's recommended security settings your Microsoft 365 organization has turned on. Your IT person or provider can read it in a few minutes at security.microsoft.com/securescore. The score is most useful as a to-do list: it ranks the changes that will close the most risk, and for most small offices the biggest ones are multifactor authentication (MFA), blocking old sign-in methods, and moving toward passwordless sign-in.
This guide explains what the number means, how to check yours, what to fix first, and how Windows Hello for Business and other passwordless options fit in. It is written for owners and office managers at dental practices, law firms, manufacturers, nonprofits and other small offices who want to understand the report without becoming a Microsoft administrator.
Key Takeaways
- Secure Score measures how closely your Microsoft 365 settings match Microsoft's recommendations. It does not predict whether you will be breached.
- Each recommended action is worth 10 points or less, and the Identity, Device, Apps and Data groups tell you where the points are.
- Completed actions can take 24 to 48 hours to show up, so do not expect an instant jump.
- Strong sign-in comes first: MFA for everyone, legacy sign-in blocked, then passwordless methods such as Windows Hello for Business or FIDO2 security keys.
- Use the score to set priorities and keep a record of decisions, not as a guarantee of safety.
Table of Contents
- What Microsoft Secure Score actually measures
- How to check your Microsoft Secure Score
- What is a good score?
- Which fixes to do first
- Why passwordless sign-in raises your score and your protection
- How to set up Windows Hello for Business
- How to enable passwordless sign-in for Microsoft 365
- Managing recommended actions without losing track
- Where we fit
- FAQ
- Sources
What Microsoft Secure Score actually measures
Per Microsoft's documentation, Secure Score is a numerical summary of your security posture. It is built from your system configurations, user behavior and other security-related measurements. A higher number means you have completed more of the recommended actions.
It is easy to read too much into it. The same Microsoft page frames the score as the extent to which you use security controls that can offset breach risk. It is not a measure of how likely a breach is, and no online service is immune. A score of 80% does not mean you are safe, and a score of 40% does not mean you are about to be hacked. It means a specific list of settings is on or off.
How points are earned
You earn points in three ways, all described in Microsoft's documentation:
- Configuring a recommended security feature.
- Doing a security-related task, such as reviewing something on a schedule.
- Addressing an action with a non-Microsoft tool, which you can mark as resolved through a third party or alternate mitigation.
Each action is worth 10 points or less. Most are scored as all or nothing, but some give partial credit by percentage. The example in Microsoft's documentation: if 50 of your 100 users are protected by MFA, you earn 5 of the 10 points for that action. The score updates in real time and syncs daily, and you can compare it with similar organizations.
The Entra side has its own number. The Identity Secure Score is shown as a percentage. It is recalculated every 24 hours by comparing your identity configuration with recommended practices, and partly met actions earn a portion of the points. It reflects sign-in and account settings, which are the settings attackers target first.
Two more details matter for a small office. The points available depend on the products you license, so two businesses with different Microsoft 365 plans will have different maximums. And the score can drop if a routine task is skipped or a setting changes, as Microsoft's security team describes. Someone loosening a policy to fix a printing problem can quietly cost you points.
What the score does not cover
Secure Score looks at your Microsoft 365 tenant, meaning your organization's account space in Microsoft's cloud. It does not test a custom website or a line-of-business web app. That is a separate discipline, and a guide to security testing for web applications explains how it differs. It also does not test whether your backups restore, whether your staff would spot a phishing email, or whether your office network is segmented. Those need their own checks.

How to check your Microsoft Secure Score
You need an administrator account for this. Regular users cannot see it.
- Sign in to the Microsoft Defender portal and go to security.microsoft.com/securescore. Microsoft's improvement actions page describes the layout.
- Read the headline. Your score appears as a percentage, with points achieved out of total possible. Optional views let you see a planned score, your score based on current licenses, and an achievable score.
- Open the Recommended actions tab. Actions are grouped into Identity, Device, Apps and Data. You can rank them by points remaining, difficulty, user impact and complexity.
- Open an action. Its flyout explains the setting, links to where you change it, and lets you add notes and a status: To address, Planned, Risk accepted, or Resolved through third party or alternate mitigation.
- Wait for the refresh. Completed actions take 24 to 48 hours to reflect in the score.
Where this goes wrong: owners often log in with an account that lacks the right role and see an empty page. Others mark something as "Risk accepted" to make a red item disappear, then forget the reason a year later. Write a note on every status change, including who decided and why. That note is the closest thing a small office has to a security decision log, and it is useful when an auditor, insurer or client asks questions.
What is a good score?
There is no single passing grade. Because the maximum depends on your licenses and the comparison depends on your size and industry, a better question is whether you have closed the high-value identity actions and whether the score is trending up. Microsoft's comparison against similar organizations gives context, but a number that matches your peers can still leave a hole in a place that matters to you, such as a shared mailbox in a law firm or a front-desk PC in a dental office.
The percentage also hides a trade-off. Some actions add friction for staff. A dental hygienist moving between operatories does not want to type a long password at every workstation. Microsoft's improvement actions page ranks items by user impact for this reason: start with high points and low user impact, then schedule the rest.

Which fixes to do first
Microsoft's training module on hardening a Microsoft 365 tenant with Secure Score lists the recommendations that come up most often. For a small business, an order that works in practice:
- Strong authentication for admins, then everyone. Admin accounts are the most valuable target. Our guide on starting MFA with Security Defaults walks through the first step.
- Block legacy authentication. Old mail protocols cannot prompt for a second factor, so they bypass MFA.
- Deal with risky sign-ins. Review and remediate sign-ins that Microsoft flags.
- Control app consent. Stop users from granting broad access to unknown apps without review.
- Replace broad standing admin roles with scoped, time-limited ones.
- Turn on self-service password reset, which cuts helpdesk calls and keeps people from reusing weak passwords.
- Tighten Teams settings such as lobby, presenter and anonymous access. Our article on Teams guest access security covers the MFA gaps guests can open.
If you want a calendar for all of this, our 30 to 90 day Microsoft 365 security checklist breaks the work into crawl, walk and run phases. If you are changing mail protection settings, read how to pilot Defender setup without breaking mail first, because a rushed policy can send legitimate email to quarantine.
Why passwordless sign-in raises your score and your protection
Passwords are the weak point that most of the identity actions try to reduce. Passwordless sign-in replaces the typed password with something tied to the device and the person.
Microsoft's passwordless strategy overview says Windows Hello for Business and FIDO2 security keys offer a strong, hardware-protected two-factor credential that enables single sign-on to Microsoft Entra ID and Active Directory. It adds that people are likely to use these features because they are convenient, especially with biometrics such as a fingerprint or face scan.
In plain terms:
- Windows Hello for Business lets someone sign in to their Windows PC with a PIN, fingerprint or face. The credential is tied to that device.
- A FIDO2 security key is a small hardware key, usually USB, that you plug in or tap to prove it is you. It is useful for shared computers and for staff who move between machines.
The benefit for a small office is not only the score. A phishing email cannot easily steal a credential that never gets typed. Our explainer on phishing-resistant MFA covers why this matters and how to phase it in.
How to set up Windows Hello for Business
The order matters. Setup does not begin on a device until the basics are in place.
Check the prerequisites
According to Microsoft's description of how Windows Hello for Business works, provisioning starts only when all of these are true:
- The device meets the Windows Hello hardware requirements.
- The device is joined to Active Directory or Microsoft Entra ID.
- The user signs in with an Active Directory or Entra ID account.
- Windows Hello for Business policy is enabled.
- The user is not connected through Remote Desktop.
That last item catches people. Someone testing from home through a remote session will never see the enrollment prompt, and the setup looks broken when it is not.
Roll it out in stages
- Inventory the devices. Find which PCs have the hardware needed for biometrics or a hardware-protected PIN. Older machines may need a FIDO2 key instead.
- Confirm everyone can sign in with MFA first. Passwordless builds on a working MFA setup. Fix any account that cannot complete a normal MFA sign-in before changing anything else.
- Enable the policy for a pilot group. Start with two or three people who will tell you what is confusing, not with the whole office.
- Let users enroll. On the next sign-in, they are prompted to create a PIN or register a fingerprint or face.
- Expand by department, and keep a documented fallback for a lost or broken device before you remove passwords from the picture.
If your office runs on-premises servers alongside Microsoft 365, hybrid setups add more requirements, including domain controller updates and extra configuration. That is where owners most often lose a day. A cloud-only office with Entra-joined laptops has a shorter list.
How to enable passwordless sign-in for Microsoft 365
For Microsoft 365 accounts, passwordless is something an administrator turns on and then each user registers for. The practical sequence is the same whichever method you choose:
- Pick the methods you will allow. For most small offices that means Windows Hello for Business on company laptops, plus security keys for shared or front-desk machines.
- Turn the method on for a pilot group in your Microsoft Entra authentication settings, rather than for the whole tenant.
- Have each pilot user register the new method while signed in with their current MFA.
- Test sign-in on every device type the user works from: office PC, laptop, phone.
- Set a recovery path so a lost key or reset laptop does not lock someone out on a Monday morning.
- Expand, then re-check Secure Score after the 24 to 48 hour refresh to see the change reflected.
The common failure is skipping the recovery path. A practice manager locked out of her own account an hour before patients arrive is the fastest way to lose staff support for a security project.
Managing recommended actions without losing track
Treat the Recommended actions list as a small project, not a one-time cleanup.
- Assign an owner to each action, even if it is you.
- Use the Planned status with a date for work you have scheduled.
- Use Risk accepted sparingly, and always with a note.
- Use Resolved through third party when another product genuinely covers the control, such as a separate MFA or email security tool.
- Review monthly. Settings drift, new recommendations appear, and the score drops when routine tasks are skipped.
If you handle regulated data, the score is a useful companion to compliance work, not a replacement for it. A dental practice dealing with HIPAA, a law firm protecting client files, or a defense supplier preparing for CMMC still needs documented policies, backups and training. Our guide to CMMC self-assessment for small DoD contractors shows how that documentation fits together.
Where we fit
A Secure Score review shows you the list. Working through it is the part that takes hours owners do not have, and the part where a wrong click can lock a user out or break mail flow.
Great Plains Networking provides managed IT support for small businesses in Norman, Moore and Oklahoma City, including Microsoft 365 setup and management and cybersecurity. We monitor 24/7, respond the same day, explain things in plain language, and do not require a long-term contract.

If you want a quick view of where you stand, the 10-minute readiness audit is free. Our Microsoft 365 Support and Cybersecurity pages explain what we take on for your team.
FAQ
How can I check my Microsoft Secure Score?
Sign in as an administrator and go to security.microsoft.com/securescore. Your score appears as a percentage with points achieved out of the total possible. The Recommended actions tab lists what to fix, grouped by Identity, Device, Apps and Data.
How long does it take for the score to update after I make a change?
Microsoft says completed actions take 24 to 48 hours to reflect in the score. The Entra Identity Secure Score is recalculated every 24 hours. Check the Recommended actions list the next day before assuming a change failed.
Is a higher Secure Score a guarantee that we are protected?
No. Microsoft describes the score as the extent to which you use controls that can offset breach risk, not a prediction of a breach. Use it to prioritize work, and pair it with tested backups, staff training and monitoring.
What do I need before turning on Windows Hello for Business?
The device must meet Windows Hello hardware requirements and be joined to Active Directory or Microsoft Entra ID. The user must sign in with an Active Directory or Entra ID account, the policy must be enabled, and the user cannot be in a Remote Desktop session during setup.
Sources
- Microsoft Secure Score - Microsoft Defender XDR
- Assess your security posture through Microsoft Secure Score
- What is the Identity Secure Score? - Microsoft Entra ID
- A quick wins approach to securing Azure Active Directory and Office 365
- Harden a Microsoft 365 Tenant with Microsoft Secure Score
- Passwordless strategy overview
- How Windows Hello for Business works
