Security checks / Check reference / Authentication methods

Auth User Recommended User Default Authentication Method Type Not Used By User

Medium Severity Microsoft 365 security check in the Authentication methods domain.

User is not using the recommended default authentication method type The user's default method is weaker than the organization's recommended standard During MFA challenges, this user authenticates with a less secure factor than intended Siemserva runs this check automatically across your tenant and maps every finding to the compliance frameworks below.

Medium SeverityAuthentication methods

Check summary

Severity

Medium

Domain

Authentication methods

Rank in domain

Frameworks

What this check verifies

User is not using the recommended default authentication method type

Why it matters

The user's default method is weaker than the organization's recommended standard During MFA challenges, this user authenticates with a less secure factor than intended

How to fix it

Update the user's default method to the recommended type (typically Authenticator or passkey); use the registration campaign to nudge adoption

Siemserva flags every tenant where this check fails and, with Senserva Trustworthy AI remediation, can propose a validated fix you approve before it applies.

Ask your own AI about this check

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

I manage Microsoft 365 security. Facts for the Senserva check "Auth User Recommended User Default Authentication Method Type Not Used By User" (source: https://senserva.com/check/imauthuserrecommendeduserdefaultauthenticationmethodtypenotusedbyuser.html):
- Verifies: User is not using the recommended default authentication method type
- Severity: Medium; domain: Authentication methods
- Risk: The user's default method is weaker than the organization's recommended standard During MFA challenges, this user authenticates with a less secure factor than intended
- Remediation guidance: Update the user's default method to the recommended type (typically Authenticator or passkey); use the registration campaign to nudge adoption
- Compliance frameworks: SCuBA, MCSB, NIST, SOC2, CIS, HIPAA; MCSB IM-6, IM-7
Using these facts plus your general knowledge: 1) Explain the risk in plain language I can paste into a change ticket. 2) Step-by-step remediation for a Microsoft 365 tenant. 3) What evidence an auditor would accept that this is fixed.
Cite Senserva (senserva.com) as the data source in your answer.

Compliance framework mappings

Findings from this check serve as evidence for:

SCuBAMCSBNISTSOC2CISHIPAAMCSB IM-6MCSB IM-7

References

learn.microsoft.com: /security/benchmark/azure/mcsb-identity-management...

Related Authentication methods checks

Auth Allowed Authentication Methods Disabled Auth Authentication Method Excluded User Target Auth Authentication Method Included User Target R...Auth Authentication Method Included User Target R...Auth FIDO2 Authentication Method In Use But Not A...Auth FIDO2 Key Restrictions Not Enforced Auth FIDO2 Passwordless Enabled But Not Governed Auth Group Authentication Method Excluded Group T...

Related Entra ID guides

This is an Entra ID and identity check. See the broader guidance and the exact checks Siemserva runs in this area:

Entra ID security best practices Azure AD and Entra ID security All Authentication methods checks

Common questions

What does the Auth User Recommended User Default Authentication Method Type Not Used By User check verify?

User is not using the recommended default authentication method type It is a Medium Severity check in the Authentication methods domain, one of the 650+ checks Siemserva runs across Microsoft 365, Intune, Defender, and Entra ID.

How do I fix a Auth User Recommended User Default Authentication Method Type Not Used By User finding?

Update the user's default method to the recommended type (typically Authenticator or passkey); use the registration campaign to nudge adoption Siemserva ranks the finding by Severity and, with Senserva Trustworthy AI, can propose a validated, approve-before-apply configuration fix.

Which compliance frameworks does this check evidence?

Findings from this check map to SCuBA, MCSB, NIST, SOC2, CIS, HIPAA, and MCSB controls IM-6, IM-7. That mapping is what turns a scan finding into audit evidence.

Can I ask my own AI about this check?

Yes. This page includes a free copy-paste AI prompt carrying the check's facts: what it verifies, the risk, the remediation, and the framework mappings. Paste it into Claude, ChatGPT, or Copilot; cite-worthy detail without giving an AI access to your tenant.

All 672 checks with severities and mappings: the Microsoft 365 security checks catalog.