1Every time strict (preview)
In the portal it’s under Session > Sign-in frequency.
What it is
- It’s a third option in Sign-in frequency, next to Periodic reauthentication and Every time.
- When an app asks for a new token, Entra checks the time since the user’s last sign-in. At 10 seconds or more, it asks them to sign in again.
- The app decides when to ask for a new token. If it keeps using the existing session, the control alone isn’t enough.
- For comparison, plain Every time requires a full sign-in when the session is evaluated, but not more than once every five minutes.
Where it fits
- The usual examples are systems where a doctor issues a digital prescription, and banking apps. Apps like these ask for a new sign-in before a sensitive action.
- The main use today is Entra Private Access. There the plain Every time option doesn’t apply at all, so you must pick strict.
- You need the Global Secure Access client for Windows, version 2.34.222 or later, an Entra Private Access licence, and at least the Conditional Access Administrator role.
Example: an admin jump box
This is an illustration, not a customer story.
- A system administrator connects over SSH to a jump box through Private Access. More than five minutes have passed since the last sign-in, so Entra asks for one. They finish at 09:01:15.
- At 09:03:45 they connect again. Less than five minutes have passed, so there’s no new prompt.
- At 09:10:34 they connect again. More than five minutes have passed, so they must sign in again.
- Note that it triggers when a new network connection to the app opens. It doesn’t mean a new prompt for every command or transaction.
From the field
- Use it only on sensitive private apps you can agree on with their owners, like a jump box.
- Start with a pilot on a small group and one app.
- Keep Microsoft 365 on time-based sign-in frequency.
- Keep break-glass accounts out of the policy.
Does Every time strict replace Every time?
No. It’s an extra option with a 10-second window, for apps built for it. In Private Access it’s the only one that applies.
2Require identity verification (preview)
In the portal it’s under Grant > Require identity verification.
What it is
- It’s a new Grant control. The user proves who they are with Microsoft Entra Verified ID, usually with Face Check, which compares the photo on a government ID with a biometric check to show the person is present.
- It’s not a sign-in method. Verified ID can’t satisfy sign-in, MFA or self-service password reset. It’s an identity-proofing layer for the moments when you need to establish again who the person is.
Three scenarios
- Resource access: requires identity verification after the first sign-in, and before any extra MFA or authentication-strength requirement.
- Onboarding and recovery: protects the moment a user sets up or restores their first sign-in method, through the user action Account onboarding and recovery.
- Risk remediation: used with User risk or Sign-in risk. Successful verification clears that risk; a failed one doesn’t. Each risk condition needs its own policy, and this is separate from Require risk remediation.
Example: a new hire
This is an illustration, not a customer story.
- Before day one: a Lifecycle Workflows process sends the new hire a link to their otherMails address, and they receive a Verified ID in Microsoft Authenticator.
- On day one: they present the Verified ID with Face Check and register a passkey in the same flow.
- Alternative: issue a Temporary Access Pass (TAP) and add a policy on the Register security information action that requires the Verified ID with Face Check before registration. A TAP alone doesn’t mark the user as verified.
- Outcome: the user is marked verified, a verification event is logged, and the new passkey gets High credential assurance. An existing passkey used with identity verification gets Medium, and if the verification expires the level drops to Low. During preview this is recorded only for passkeys.
What you need
- An identity verification profile, and at least Entra ID P1. Conditional Access for resource access also needs at least P1.
- Risk-based verification needs P2. Integrated onboarding with Lifecycle Workflows needs ID Governance or the Entra Suite.
- Face Check is a paid add-on, included in the Entra Suite. Identity verification provider services are bought separately.
- During preview it’s available only in the public cloud.
From the field
- Start at the weakest moment: a new hire’s first sign-in method, and account recovery.
- Check licensing cost first, including Face Check and the identity provider.
- Start with a pilot on a small group, and keep break-glass accounts out of the policy.
Is Require identity verification the same as MFA?
No. It can’t satisfy sign-in, MFA or self-service password reset. It proves identity; it doesn’t replace authentication.
What we haven’t tested
Both controls are in preview. This post is based on Microsoft’s documentation (read on 20 November 2026), not on a test in our own tenant. Behavior and support may change.
Want to know how your Entra identity security looks? Griffin31 checks your Microsoft 365 tenant’s security settings and shows you what to fix first.
Sources
- Microsoft Learn: Conditional Access adaptive session lifetime policies (Every time strict)
- Microsoft Learn: Configure sign-in every time for Microsoft Entra Private Access (preview)
- Microsoft Learn: Require identity verification with Conditional Access
- Microsoft Learn: Verified ID identity verification overview
- Microsoft Learn: Onboard users with identity verification (preview)
- Microsoft Learn: Microsoft Entra licensing, identity verification