CIS Microsoft Azure Foundations Benchmark v1.4.0/Identity and Access Management/4 of 115
1.4Ensure that 'Restore multi-factor authentication on all remembered devices' is Enabled
Control family: Identity and Access Management
Control description
Do not allow users to remember multi-factor authentication on devices.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
Letting users skip MFA on a device they marked as trusted means anyone who gets hold of that device, or its browser session, can sign in without a second factor for weeks. The remember-MFA option is turned off and any trust already granted is revoked, so MFA is asked for as your sign-in policies intend.
Before you start
The same on every cloud, before the steps in the tabs.
- Decide that users may not skip MFA on devices they mark as trusted, and how often people re-authenticate instead (a Conditional Access sign-in frequency).
- Tell users before the change, since they will be asked for MFA more often.
Evidence
- The directory settings standard, with the decision recorded and its approver
On Azure the tasks turn off remembered MFA in the per-user MFA service settings of Microsoft Entra ID, then revoke the trust already granted.
Task 1Turn off remembered MFA
- Sign in to the Azure portal at portal.azure.com and open Microsoft Entra ID > Users.
- Select Per-user MFA, then service settings.
- Under remember multifactor authentication, clear Allow users to remember multifactor authentication on devices they trust.
- Select Save.
- Check it: on a test sign-in, the "Don't ask again" option is no longer offered. Control how often people re-authenticate with a Conditional Access sign-in frequency instead.
Task 2Revoke the trust already given to devices
- In Microsoft Entra ID > Users, open a user who may have remembered devices.
- Select Revoke sessions and confirm, which also clears remembered MFA.
- Do this for administrators first, then everyone, or ask the help desk to do it as part of the change.
- Check it: the user is asked for MFA at their next sign-in.
Evidence
- The per-user MFA service settings, with remember multifactor authentication cleared
- The record of sessions revoked when the change was made
Not applicable. This benchmark covers Azure only.
Not applicable. This benchmark covers Azure only.
Console steps as of 5 November 2026. Not every step has been confirmed in a live console yet, and menus and labels can move between releases, so look for the nearest match if one has changed.