Find the AI tools nobody approved
Skip to content
Resources

How do I check MFA coverage across all my users?

Learn how to measure MFA coverage across every identity provider, find every account that can still be phished and fix admin and break-glass accounts first, with a prompt to build your own version.

Rob Jardine6 min read

To check MFA coverage across all your users, pull sign-in methods from every identity provider (IdP) into one view and match each account to a real person, their role and the systems they can reach. Then rank the gaps, so accounts with no MFA, phishable MFA or admin rights get fixed first.

In Dimension by ThreatAware, the MFA Coverage application (opens in a new tab) does this across whichever identity providers you run, such as Microsoft Entra ID, Okta and Google Workspace. It shows every account that can still be phished, puts admins first, and raises a ticket or sends an enrollment reminder once a person approves it.

You can run the application as it is, customize it in plain language, or build your own version from the prompt below.

Even basic MFA makes a large difference: Microsoft research found that MFA reduced the risk of account compromise by 99.22% across the population studied, and by 98.56% where credentials had leaked (Meyer et al., 2023, Azure Active Directory accounts showing suspicious activity). The gaps that remain are accounts with no MFA and accounts whose MFA can still be phished.

Why is MFA coverage hard to measure across identity providers?

MFA coverage is hard to measure across identity providers because each one reports MFA in its own format, so coverage gets checked one console at a time. If you run more than one identity provider, the totals rarely add up.

A flat export shows whether MFA is switched on, not whether it’s phishing-resistant or whether SMS still works behind a passkey. It also doesn’t show which gaps belong to someone with admin rights to production.

“MFA enabled tells you a method is registered. It doesn’t tell you whether SMS still works as a fallback, or whether the account with the gap belongs to a global admin. Protected means every path into that account is phishing-resistant.” — Rob Jardine, CMO, ThreatAware

How do you check MFA coverage without a dedicated tool?

You can check MFA coverage without a dedicated tool by exporting registered sign-in methods and admin roles from each identity provider, then combining them in a spreadsheet. It works, but it takes time to keep current.

  1. Export each user’s registered MFA methods from every identity provider, using its admin console, reports or API.
  2. Export admin role assignments from each provider.
  3. Combine the exports in a spreadsheet, match accounts that belong to the same person, and flag admins and weak methods.

The manual route has blind spots. Each provider reports in a different format, weaker fallback methods such as SMS are easy to miss, and the spreadsheet is out of date as soon as it’s finished.

What is the best way to measure MFA coverage?

MFA coverage is best measured as the share of people whose every sign-in account is protected by phishing-resistant MFA, across every identity provider. Count a person as protected only if all of their accounts are, and track service accounts that can’t use MFA separately.

Registered sign-in methods show what an account can use, not what it’s forced to use. Check that your sign-in policies, such as Conditional Access in Microsoft Entra ID, actually require phishing-resistant methods.

Which accounts without strong MFA should you fix first?

Fix MFA gaps on global admin and break-glass accounts first, then accounts that can reach production systems, finance or HR data.

  • Global and super admin accounts, including break-glass accounts.
  • Accounts that can reach production systems, finance or HR data.
  • Accounts with strong MFA but a weak fallback, where removing the weaker method and requiring phishing-resistant sign-in in your policies closes the gap.
  • Everyone else, working toward a coverage target with a date.

How do you check MFA coverage in Dimension?

To check MFA coverage in Dimension by ThreatAware, a governed workspace for security applications, connect each identity provider, start from the MFA Coverage application and work through the ranked list of gaps.

  1. Connect your identity providers. Add a feed from each identity provider you run. Dimension connects through each provider’s API and reads registered sign-in methods and roles without changing them.
  2. Start from the App Library. Open the MFA Coverage application (opens in a new tab) and point it at your data, or paste its prompt into AI Composer to build your own version.
  3. See coverage in one place. Get one figure for the share of accounts protected by phishing-resistant MFA across every provider, and a list of every account that isn’t.
  4. Prioritize by risk. Each gap shows the person, their role and their sign-in method, with the most dangerous first.
  5. Fix from the list. Raise a ticket in your ticketing tool or send an enrollment reminder. A person approves each action before it runs, and it’s written to the audit log.
  6. Track progress to a target. Set a coverage goal and date, then watch the gap close as accounts move to stronger methods.

Which systems does an MFA coverage check need?

An MFA coverage check needs data from every identity provider you run, plus a ticketing or IT service management tool if you want to raise fixes from the list.

Tool category Common examples Used for
Identity provider (IdP) Microsoft Entra ID, Okta, Google Workspace, Ping Identity Registered MFA methods, admin roles and application access for each account
Ticketing or IT service management (ITSM) Jira, ServiceNow, Freshservice Raising an MFA ticket once approved (action)

Dimension connects to your systems through their APIs, so you can point the application at the tools you already run. The tools named here are common examples, not requirements.

Which MFA gaps are the most dangerous?

The most dangerous MFA gaps are admin and break-glass accounts without strong MFA, then any account with no MFA, only phishable MFA, or strong MFA with a weak fallback.

  • No MFA at all: accounts that sign in with a password alone.
  • Phishable MFA only: text message codes, phone calls, push approvals or one-time codes, which attackers can intercept, relay or trick users into approving.
  • Strong MFA with a weak fallback: a passkey or security key is set up, but SMS still works as a way in.
  • Admin and break-glass accounts: global and super admin accounts without strong MFA, ranked as critical.

The MFA Coverage application also shows which systems weak accounts can reach, such as production cloud, code repositories, finance and HR systems, so you can see the impact of the gaps.

How do you start with the MFA Coverage application?

To start with the MFA Coverage application, open it in the App Library of Dimension by ThreatAware and run it on your own data with a 14-day free trial, with no credit card. Dimension is ThreatAware’s governed workspace for security applications, and nothing changes in a live system without a person’s approval.

To build your own version, paste this prompt into AI Composer, or into Claude Code or another AI coding agent over MCP. The prompt names example tools, so swap in the ones you use:

Show every account in Entra ID, Okta and Google Workspace that can still be phished: no MFA, phishable MFA, or a strong method with SMS still behind it. Put admins first, and raise a Jira ticket or send an enrollment reminder from the list.

Run this application free (opens in a new tab)

Related

Frequently asked questions

About the author

Rob Jardine is Chief Marketing Officer at ThreatAware (opens in a new tab), the cybersecurity software company that builds Dimension. ThreatAware was founded in 2018, is ISO/IEC 27001:2022 certified and provides security software to more than 100 enterprise organizations across Europe and North America.

Sources

Statistic or fact Source
MFA reduced the risk of compromise by 99.22% overall and 98.56% with leaked credentials Meyer et al., “How effective is multifactor authentication at deterring cyberattacks?”, Microsoft, May 2023: Azure Active Directory accounts showing suspicious activity
Methods in Entra ID’s built-in phishing-resistant MFA strength Microsoft Learn, “Conditional Access authentication strength”, last updated 24 October 2025
Finding users who aren’t MFA capable in Entra ID Microsoft Learn, “Authentication methods activity”, last updated 23 October 2025
MFA on cloud services is an automatic fail for Cyber Essentials IASME, “Important Update: Changes to Cyber Essentials for April 2026”, 12 February 2026
Emergency access account authentication Microsoft Learn, “Manage emergency access accounts in Microsoft Entra ID”, last updated 5 June 2026

Build it. Approve it. Run it.

Try Dimension free for 14 days on your own data, with no credit card. Plans start from $49 per month.