No persistent Browser Sessions
This Conditional Access Policy prevents users from maintaining persistent browser sessions, requiring them to re-authenticate more frequently. It helps reduce the risk of unauthorized access from shared or unmanaged devices.
Settings this baseline controls
| Setting | What it does |
|---|---|
| Policy name | Specifies a display name for the Conditional Access Policy Learn more |
| Enable policy | Specifies the state of the conditional Access Policy. Possible values are: enabled, disabled, enabledForReportingButNotEnforced. Required. Learn more |
| Included users | User IDs in scope of policy Learn more |
| Included roles | Role IDs in scope of policy Learn more |
| Included groups | Group IDs in scope of policy Learn more |
| Included guest types | Guest or external user types in scope of policy Learn more |
| Excluded users | User IDs excluded from scope of policy Learn more |
| Excluded roles | Role IDs excluded from scope of policy Learn more |
3 more settings
| Setting | What it does |
|---|---|
| Excluded groups | Group IDs excluded from scope of policy Learn more |
| Excluded guest types | Guest or external user types excluded from scope of policy Learn more |
| Persistent browser session | Session control to define whether to persist cookies or not. All apps should be selected for this session control to work correctly. Learn more |
Configure it
Add this baseline when users shouldn’t stay signed in across browser restarts. It’s useful on shared or unmanaged machines, where a persistent session is the easiest way for the next person at the keyboard to inherit someone else’s access.
-
Add the baseline to the tenant directly (see Adding a baseline), or carry it in a scheme you deploy to every tenant you manage (see Deploying a scheme).
-
Leave Included users covering everyone, and use Excluded users or Excluded groups for your organisation’s break-glass accounts.
-
Leave Persistent browser session set to never persist. This session control only takes effect when the policy targets every resource. If you narrow the resources it applies to, some browser tabs stay persistent and others don’t, because all tabs in a session share one token.
-
Save.
Turn on Auto-remediation if you want Octiga to reapply the policy whenever it’s changed in Microsoft 365.
Check it worked
After the next sync, this baseline shows Passing once a policy with state set to enabled and persistent browser sessions set to never persist exists in Microsoft Entra. You can confirm it in the Microsoft Entra admin centre under Entra ID > Conditional Access > Policies. End users are asked to sign in again each time they close and reopen their browser, instead of being offered a “Stay signed in?” prompt.
Standards this addresses
Doing this for every tenant?
Step through the deploy wizard to apply a scheme to a tenant, groups or users, and see what Managed and Direct do at deploy time.