Users should not be able to remember multifactor authentication on trusted devices
This check looks at the Microsoft Entra multifactor authentication service setting that lets people skip the MFA prompt on devices they mark as trusted. The safe setting is to leave that option off, so MFA is asked for according to your Conditional Access rules instead of a per-device exception.
Why it matters
When the remember option is on, a person who passes MFA once can tick a box and skip the prompt on that browser or device for a number of days. Anyone who later gets hold of that browser session, a shared computer or a stolen laptop inherits the exemption, and the extra factor you rolled out no longer protects that sign-in path. Turning it off puts you in control of how often people are prompted, and Conditional Access sign-in frequency is the supported way to tune that.
Microsoft describes both approaches in Configure Microsoft Entra multifactor authentication settings and Configure authentication session management with Conditional Access.
How to check it yourself
Portal path: Microsoft Entra admin center, Protection, Multifactor authentication, Additional cloud-based multifactor authentication settings. Under Remember multifactor authentication on trusted device, the box Allow users to remember multifactor authentication on devices they trust should be cleared.
That legacy service setting is only exposed in the portal. A read-only way to see what your Conditional Access policies already enforce for sign-in frequency is:
az rest --method GET --url "https://graph.microsoft.com/v1.0/identity/conditionalAccess/policies?\$select=displayName,state,sessionControls"Look at sessionControls.signInFrequency in each policy. The command only reads policy definitions and needs a role that can read Conditional Access policies. Try it in a test tenant first if you are unsure.
How to fix it
Portal steps: open the same page as above, clear the box Allow users to remember multifactor authentication on devices they trust and select Save. Then decide how often people should be prompted and express that in a Conditional Access policy with a sign-in frequency session control.
Example with Microsoft Graph PowerShell, created in report-only mode so nothing is enforced until you review the results (replace the placeholder group id):
Connect-MgGraph -Scopes "Policy.ReadWrite.ConditionalAccess"
$params = @{
displayName = "Require MFA, prompt every 8 hours"
state = "enabledForReportingButNotEnforced"
conditions = @{ users = @{ includeGroups = @("<group-id>") }; applications = @{ includeApplications = @("All") } }
grantControls = @{ operator = "OR"; builtInControls = @("mfa") }
sessionControls = @{ signInFrequency = @{ isEnabled = $true; type = "hours"; value = 8; authenticationType = "primaryAndSecondaryAuthentication"; frequencyInterval = "timeBased" } }
}
New-MgIdentityConditionalAccessPolicy -BodyParameter $paramsConfigCobra itself only reads your tenant and shows the portal steps or script; it never applies the change for you.
What changes when you fix it
People who relied on the remember option will see MFA prompts more often, typically at each new sign-in session, until you set a sign-in frequency that suits them. Expect extra prompts for staff on shared or frequently cleaned browsers and for anyone who signs in from many devices. Service accounts and automation that cannot answer an MFA prompt are not helped or harmed by this setting, but review any that sign in interactively. Tell users before the change, keep help-desk guidance for registering an authenticator app, and use report-only mode on the Conditional Access policy to preview the effect.
ConfigCobra's remediation impact analysis lists the affected users and applications for a failing control before you apply the fix.
Included in
| Benchmark | CIS ID | Profile |
|---|---|---|
| CIS Microsoft Azure Foundations v6.0.0 | 5.1.4 | Level 1 |
More checks in Identity Services
Check this on your Microsoft Azure
ConfigCobra runs this check with every other control of the CIS Microsoft Azure Benchmarks, read-only.