MFA is one of the most important identity controls in Microsoft Entra ID, but there is a problem with the question most teams ask:
“Do we have MFA enabled?”
That question is too broad.
A tenant can have Conditional Access policies that require MFA and still contain users who have never registered a usable MFA method. A user can also be registered for MFA but fall outside the policy that actually requires it. And a registered method can exist even though that method is no longer allowed by your current authentication methods policy.
If you want to assess MFA coverage correctly, you need to separate registration, capability, and enforcement.
This article shows several practical ways to find users without MFA in Microsoft Entra ID and explains what the results actually mean.
Quick Answer: The Fastest Way to Find Users Without MFA
For a quick tenant-wide check, use the Microsoft Entra authentication methods registration report or query the same data through Microsoft Graph.
The most direct Microsoft Graph PowerShell query is:
Connect-MgGraph -Scopes "AuditLog.Read.All"
Get-MgReportAuthenticationMethodUserRegistrationDetail -All -Filter "isMfaRegistered eq false" |
Select-Object UserDisplayName, UserPrincipalName, IsAdmin, IsMfaRegistered, IsMfaCapable, MethodsRegistered
This returns users in the authentication methods registration report whose isMfaRegistered property is false.
But do not stop there. For an operational security review, you should also look at isMfaCapable, privileged accounts, Conditional Access coverage, guest-user behavior, and recent sign-ins.
What “Without MFA” Actually Means in Entra ID
Microsoft Entra exposes several MFA-related states, and they answer different questions.
| Signal | What it tells you | Why it matters | | --- | --- | --- | | isMfaRegistered | The user has registered a strong authentication method | Useful for finding users who have not completed MFA registration | | isMfaCapable | The user has a strong authentication method that is allowed by the current authentication methods policy | Better indicator of whether the user is ready to satisfy MFA with an allowed method | | Conditional Access / Security Defaults | Whether policy requires MFA for a sign-in scenario | Registration alone does not prove MFA is enforced | | Sign-in logs | What actually happened during authentication | Best place to validate whether MFA was required or satisfied for real sign-ins |
This distinction matters because MFA registered is not the same as MFA protected.
A user can be registered but excluded from a Conditional Access policy. Another user can have a registered method that is no longer allowed by policy, making the account registered but not currently MFA-capable.
For that reason, I usually review both of these conditions:
isMfaRegistered = false— the user has not registered a strong authentication method.isMfaCapable = false— the user does not currently have an allowed strong authentication method that can satisfy MFA.
Method 1: Find Users Without MFA in the Microsoft Entra Admin Center
For a manual review, the Microsoft Entra admin center is the easiest place to start.
- Sign in to the Microsoft Entra admin center.
- Browse to Entra ID > Authentication methods > Activity.
- Open the Registration view or the User registration details report.
- Review the MFA-related status for each user.
- Filter or export the report so you can investigate users who are not MFA-capable.
The report includes useful fields such as:
- User principal name
- User display name
- MFA capability
- Passwordless capability
- SSPR registration and capability
- Authentication methods registered
- Last updated time
This view is useful when you want to quickly answer questions such as:
- Which users are not MFA-capable?
- Which privileged users are missing strong authentication?
- Which authentication methods are most commonly registered?
- Are users relying on weaker methods instead of phishing-resistant options?
Important Reporting Limitation
The authentication methods activity report is not real-time. Microsoft documents that the data can take up to approximately 36 hours to update for most users.
Microsoft also notes that disabled and recently deleted users are not listed in user registration details. That is normally reasonable for an MFA readiness report because disabled users cannot sign in, but it matters if you are trying to reconcile the report against a complete directory export.
Method 2: Find Users Without MFA with Microsoft Graph PowerShell
For recurring reviews, exports, automation, or larger tenants, Microsoft Graph PowerShell is more useful than manually filtering the portal.
Step 1: Connect with the Required Permission
The registration details API uses the AuditLog.Read.All permission for delegated and application access.
Connect-MgGraph -Scopes "AuditLog.Read.All"
A supported Entra role is also required for delegated access. Microsoft lists roles such as Reports Reader, Security Reader, Security Administrator, and Global Reader for this operation.
Step 2: Find Users Who Are Not Registered for MFA
$usersWithoutMfa = Get-MgReportAuthenticationMethodUserRegistrationDetail -All -Filter "isMfaRegistered eq false"
$usersWithoutMfa |
Select-Object UserDisplayName,
UserPrincipalName,
IsAdmin,
IsMfaRegistered,
IsMfaCapable,
MethodsRegistered |
Format-Table -AutoSize
This is the cleanest query when your question is specifically:
Which users have not registered an MFA method?
Step 3: Find Users Who Are Not MFA-Capable
For security operations, I also run this query:
$usersNotMfaCapable = Get-MgReportAuthenticationMethodUserRegistrationDetail -All -Filter "isMfaCapable eq false"
$usersNotMfaCapable |
Select-Object UserDisplayName,
UserPrincipalName,
IsAdmin,
IsMfaRegistered,
IsMfaCapable,
MethodsRegistered |
Format-Table -AutoSize
Why is this useful?
Because a user may have a method registered but still not be capable of satisfying MFA under the current authentication methods policy. isMfaCapable is therefore a useful second check when validating whether your identities are actually ready to meet an MFA requirement.
Step 4: Export the Results to CSV
Get-MgReportAuthenticationMethodUserRegistrationDetail -All -Filter "isMfaRegistered eq false" |
Select-Object UserDisplayName,
UserPrincipalName,
IsAdmin,
IsMfaRegistered,
IsMfaCapable,
MethodsRegistered |
Export-Csv -Path ".\Entra-Users-Without-MFA.csv" -NoTypeInformation
A CSV export makes it easier to assign remediation owners, track exceptions, and compare coverage from one review to the next.
Method 3: Use Microsoft Entra PowerShell
Microsoft's Entra PowerShell module also exposes the authentication method user registration report.
Connect-Entra -Scopes 'AuditLog.Read.All'
Get-EntraAuthenticationMethodUserRegistrationDetailReport -All -Filter "isMfaRegistered eq false" |
Format-Table -AutoSize
To focus on users who are not currently MFA-capable:
Get-EntraAuthenticationMethodUserRegistrationDetailReport -All -Filter "isMfaCapable eq false" |
Format-Table -AutoSize
If your organization is standardizing on the newer Microsoft Entra PowerShell module, this is a straightforward way to build the same MFA coverage check into operational scripts.
Method 4: Query Microsoft Graph Directly
You can retrieve the same registration data directly from Microsoft Graph.
Users Not Registered for MFA
GET https://graph.microsoft.com/v1.0/reports/authenticationMethods/userRegistrationDetails?$filter=isMfaRegistered eq false
Users Not MFA-Capable
GET https://graph.microsoft.com/v1.0/reports/authenticationMethods/userRegistrationDetails?$filter=isMfaCapable eq false
The userRegistrationDetails resource can return fields including:
userPrincipalNameuserDisplayNameisAdminisMfaRegisteredisMfaCapableisPasswordlessCapablemethodsRegisteredsystemPreferredAuthenticationMethodslastUpdatedDateTime
This is useful if you want to feed MFA coverage into a reporting process, automation job, internal dashboard, or security assessment workflow without relying on manual portal exports.
A Better MFA Review: Prioritize the Accounts That Matter Most
A flat list of users without MFA is useful, but it is not enough. I would prioritize the findings in this order.
1. Privileged Accounts Without MFA
Start with administrators and users who can elevate into privileged roles.
The registration details resource includes an isAdmin property, which makes it easy to identify users who are both privileged and missing MFA registration or capability.
Get-MgReportAuthenticationMethodUserRegistrationDetail -All |
Where-Object { $_.IsAdmin -eq $true -and $_.IsMfaCapable -eq $false } |
Select-Object UserDisplayName, UserPrincipalName, IsMfaRegistered, IsMfaCapable, MethodsRegistered
Any privileged interactive account that cannot satisfy MFA deserves immediate review.
2. Normal Member Accounts Without MFA
After privileged accounts, review active workforce users. These accounts often have access to email, collaboration tools, SaaS applications, Azure resources, and internal data.
The goal should not simply be to make the report green. The goal is to ensure the user has an approved strong authentication method and that policy actually requires MFA where appropriate.
3. Service or Shared User Accounts
Be careful here.
A legacy service account implemented as a normal Entra user may not be able to complete interactive MFA. That does not mean the correct fix is to create an MFA exception and leave the design alone.
Where possible, move non-human access to workload identities such as:
- Managed identities
- Service principals
- Certificate-based application authentication
If a user-based service account must remain temporarily, restrict it aggressively, document the exception, minimize permissions, and monitor its sign-in behavior.
4. Guest and External Users
Guest accounts require context.
Microsoft Entra cross-tenant access settings can be configured to trust MFA claims from another Microsoft Entra organization. In that design, an external user may satisfy your Conditional Access MFA requirement using MFA performed in the user's home tenant.
That means a local registration report should not be interpreted in isolation for B2B users. Review cross-tenant trust settings and actual sign-in results before deciding that an external identity is unprotected.
Do Not Confuse MFA Registration with MFA Enforcement
This is the most important takeaway in the entire article.
An MFA registration report answers:
Can this user perform MFA, and what methods are registered?
It does not prove:
Is this user required to perform MFA for the sign-ins that matter?
To validate enforcement, review your Conditional Access policies, Security Defaults configuration where applicable, exclusions, authentication strengths, and sign-in logs.
A strong MFA review therefore has three layers:
- Registration: Has the user registered a strong authentication method?
- Capability: Is the registered method currently allowed and usable for MFA?
- Enforcement: Do your access policies actually require MFA for the user's relevant sign-ins?
If you only measure the first layer, you can report 100% MFA registration while still having policy gaps.
Common Mistakes When Auditing MFA Coverage
Mistake 1: Looking Only at Per-User MFA State
Older MFA reporting workflows often focused on the per-user MFA states of Disabled, Enabled, and Enforced.
That model does not fully describe modern Entra protection because organizations commonly enforce MFA through Conditional Access, authentication strengths, or Security Defaults. Microsoft also notes that the newer registration/capability properties are not an exact equivalent of the legacy per-user MFA state.
Mistake 2: Treating Every Account the Same
Human users, emergency access accounts, guests, service accounts, and workload identities have different authentication requirements. Your report should classify them rather than applying the same remediation blindly.
Mistake 3: Ignoring Authentication Method Quality
“Has MFA” is not the end goal.
For higher-risk users, especially administrators, review whether the registered method meets your desired authentication strength. A tenant where every administrator uses phishing-resistant authentication has a very different risk profile from one that relies heavily on weaker factors.
Mistake 4: Never Rechecking After the Initial Rollout
MFA coverage drifts.
New hires appear. Contractors are invited. Break-glass accounts are changed. Authentication methods are replaced. Policy exclusions are added. Service accounts linger. Users register methods that later become disallowed.
MFA coverage should be measured continuously or at least on a regular schedule.
How I Would Operationalize This Check
For a practical monthly identity review, I would track at least these metrics:
- Total enabled workforce users
- Users not registered for MFA
- Users not MFA-capable
- Privileged users not MFA-capable
- Users by registered authentication method
- Guest users requiring separate review
- Conditional Access exclusions affecting MFA
- Recent sign-ins that were single-factor where MFA was expected
Then track the trend.
A tenant moving from 96% to 99.5% effective coverage is improving. A tenant that stays at 99.5% but repeatedly has different privileged exceptions is still carrying operational risk.
The percentage matters, but who is in the uncovered percentage matters more.
How AzureWise Helps Surface MFA Coverage
This is one of the reasons I built the AzureWise Identity Security Assessment.
The AzureWise toolkit is designed to turn Microsoft Entra ID security telemetry into a more practical assessment view inside Azure Monitor instead of forcing engineers to rebuild the same identity-security checks every time.
The workbook and included KQL query pack focus on areas such as:
- MFA coverage and users without MFA
- Risky and suspicious sign-ins
- Legacy authentication
- Privileged role changes and recent privileged activity
- Service principal sign-ins
- OAuth consent activity
- Guest-user activity
AzureWise is intentionally read-only. It does not change users, Conditional Access policies, applications, roles, or permissions. It is designed to help you identify and prioritize identity-security gaps using data already available in your Azure environment.
Want a faster way to review Microsoft Entra ID identity risk?
The AzureWise Identity Security Assessment is available as a one-time $99 license. Deploy the workbook in your own Azure environment and use the included assessment views and KQL query pack to reduce the amount of manual security review work.
>
View the AzureWise Identity Security Assessment | Pricing & Licensing
MFA Coverage Checklist
Use this as a quick review checklist:
- [ ] Identify users with
isMfaRegistered = false. - [ ] Identify users with
isMfaCapable = false. - [ ] Prioritize privileged users first.
- [ ] Review active member accounts separately from guests and service accounts.
- [ ] Validate Conditional Access and Security Defaults coverage.
- [ ] Review MFA-related policy exclusions.
- [ ] Check sign-in logs to confirm real-world MFA enforcement.
- [ ] Review the strength of registered authentication methods for administrators.
- [ ] Document legitimate exceptions and assign an owner and expiration date.
- [ ] Re-run the review regularly and track the trend.
FAQ: Finding Users Without MFA in Microsoft Entra ID
How do I find users who have not registered for MFA in Microsoft Entra ID?
Use the Microsoft Entra authentication methods registration report or query Microsoft Graph at /reports/authenticationMethods/userRegistrationDetails. Filter the results where isMfaRegistered equals false.
What is the difference between isMfaRegistered and isMfaCapable?
isMfaRegistered indicates that the user has registered a strong authentication method. isMfaCapable indicates that the user has a strong authentication method that is allowed by the current authentication methods policy. For security reviews, both are useful.
Does isMfaRegistered mean MFA is enforced?
No. Registration tells you that an authentication method exists. MFA enforcement depends on policies such as Conditional Access or Security Defaults and must be validated separately.
Why is a user missing from the authentication methods registration report?
Microsoft documents that disabled and recently deleted users are not included in user registration details. The report can also have update latency, so very recent changes may not appear immediately.
What permission is required to query MFA registration with Microsoft Graph?
For the userRegistrationDetails report, Microsoft documents AuditLog.Read.All as the least-privileged delegated and application permission. Delegated access also requires a supported Microsoft Entra role.
Should service accounts be excluded from MFA?
Do not treat an MFA exception as the default solution for service accounts. Where possible, replace user-based automation with managed identities or service principals and use non-interactive authentication designed for workloads. If a user-based service account must remain, minimize its permissions and tightly control its sign-in paths.
How often should I audit MFA coverage?
For most environments, MFA coverage should be monitored continuously where practical and reviewed on a regular operational cadence. At minimum, recheck after major onboarding, Conditional Access changes, authentication-method policy changes, mergers, or identity migrations.
Final Takeaway
Finding users without MFA in Microsoft Entra ID is not difficult. Interpreting the result correctly is where the real security work begins.
Start with isMfaRegistered = false to identify users who have not registered a strong authentication method. Then check isMfaCapable = false to find users who cannot currently satisfy MFA with an allowed method. Prioritize privileged accounts, separate human users from service identities and guests, and validate Conditional Access and sign-in behavior so you know MFA is actually being enforced.
The goal is not simply to reach a high MFA registration percentage.
The goal is to make sure every relevant identity has a strong method, can use it, and is required to use it when access risk demands it.
Learn more about the AzureWise Identity Security Assessment
Microsoft References
- Authentication Methods Activity
- List userRegistrationDetails - Microsoft Graph v1.0
- userRegistrationDetails resource type
- Get-MgReportAuthenticationMethodUserRegistrationDetail
- Get-EntraAuthenticationMethodUserRegistrationDetailReport
- Manage per-user MFA settings with Microsoft Entra PowerShell
- Cross-tenant access settings for B2B collaboration
Related AzureWise Resources
Want the Azure identity assessment already built?
AzureWise Identity Security Assessment turns Microsoft Entra ID telemetry into a weighted Security Rating, detailed findings, and prioritized remediation guidance inside Azure Monitor.
Get AzureWise — $99