What is MFA?
Multi-factor authentication (MFA) requires a user to prove their identity with two or more different kinds of evidence, such as a password plus a code from a phone app or a hardware security key, instead of a password alone. It matters because a stolen password then no longer opens the account by itself, which makes MFA one of the most effective single controls for a cloud tenant.
How it works
MFA combines factors from different groups: something you know (a password or PIN), something you have (a phone, an authenticator app, a security key) and something you are (a fingerprint or face). Two passwords are not MFA, because both are the same kind of factor. After the password is accepted, the service asks for the second proof before it issues a session.
What it looks like on each platform
- Microsoft 365: users register methods in Microsoft Entra ID, for example the Microsoft Authenticator app, a passkey or a FIDO2 security key. MFA is then required through Conditional Access policies or through security defaults. Authentication strengths let a policy demand a specific set of methods, for example phishing-resistant ones for administrators.
- Azure: administrators sign in with the same Entra identity, so the same policies apply to the portal and command-line tools.
- Google Cloud: people sign in with a Google account, where 2-Step Verification is the MFA feature. Google's documentation describes how an organization can enforce it for its users.
- AWS: IAM supports passkeys and security keys, virtual authenticator apps and hardware TOTP tokens. The root user and every IAM user with a console password should have one registered.
Not all second factors are equal
A code sent by text message or typed from an app can be phished: a fake sign-in page collects it and replays it. Passkeys and security keys based on FIDO standards are bound to the real website and resist this. AWS's documentation recommends phishing-resistant MFA whenever possible, and NIST's digital identity guidelines (SP 800-63B) describe phishing resistance as a property of the authenticator.
Why it matters
Most account takeovers start with a password that was reused, guessed or phished. With MFA in place, that password is not enough. The NSA and CISA advisory on common misconfigurations (AA23-278A) names weak or misconfigured MFA as a recurring finding, so the gap is rarely "no MFA exists" and more often "MFA exists but not for everyone".
The usual gaps are administrators who are exempt, service or shared accounts nobody enrolled, older sign-in protocols that skip the prompt, and users who simply never registered a method. A policy that says MFA is required does nothing for an account that has no method behind it.
How it compares
| Term | Meaning | Difference from MFA |
|---|---|---|
| 2FA | Exactly two factors | A special case of MFA |
| Passwordless | Sign-in without a password, for example with a passkey | Can still be multi-factor: the device you hold plus a PIN or fingerprint |
| SSO | One sign-in for many apps | Convenience, not extra proof; MFA is usually enforced at that single sign-in |
| Conditional Access | Policies that decide when to ask for MFA | The rule that enforces MFA, not the factor itself |
| Privileged access management | Controls on who may use administrator rights and when | Works alongside MFA for admin accounts |
Getting started
- Protect administrators first: every admin role in Microsoft 365, the Azure subscription owners, the Google Cloud organization admins and the AWS root user.
- Keep two emergency access accounts with their own strong, tested method, and document where they are stored.
- Find who has no method registered, and run a registration drive before you enforce MFA for everyone.
- Block legacy sign-in protocols, which cannot show an MFA prompt.
- Move administrators to phishing-resistant methods such as passkeys or security keys, then extend that to the rest of the staff over time.
How ConfigCobra fits
ConfigCobra's Inventory module on Microsoft 365 includes a built-in risk view for users with no MFA registered, next to views for inactive users and guests who never signed in. You can export the list as CSV. The relation graph shows how users connect to roles and Conditional Access scope.
The CIS Microsoft 365 Foundations Benchmark v7.0.0 (160 controls) includes controls on requiring MFA for administrators and for all users, and its Microsoft Entra section has 63 controls in total. ConfigCobra reads your tenant with read-only permissions and never changes it; for a failing control it gives a fix script or portal steps.
Go further
- Conditional AccessConditional Access is the policy engine in Microsoft Entra ID that decides at each…
- Zero TrustZero Trust is a security approach that grants access to each resource only after…
- Least privilegeLeast privilege is the principle that every user, application and service account gets…
- All academy termsCloud security concepts explained
See where your cloud stands
ConfigCobra checks Microsoft 365, Azure, Google Cloud and AWS against the CIS benchmarks, read-only, with evidence for every finding.