Template family: Conditional Access
Applies to: Microsoft Entra ID
Where to find it: Secure → Conditional Access → Templates → Augmentt Default

What this template is for

Requiring administrators to re-authenticate every 4 hours and preventing persistent browser sessions limits the window of opportunity for session token theft and drive-by attacks. Without this control, a stolen admin session cookie could provide indefinite access. Non-persistent sessions ensure no session cookies are saved after the browser is closed. This policy satisfies CIS Microsoft 365 Foundations Benchmark v6.0.0 section 5.2.2.4 (L1).

What it actually does

Who it covers. Users holding any of 15 administrative roles, when they sign in to all cloud apps.

Who is excluded. Service-provider (GDAP) guest accounts are excluded automatically, so your own technicians keep access if the policy misfires.

Session controls. For sessions allowed through, it forces reauthentication every 4 hours and prevents the browser session persisting, so closing the browser signs the user out.

Deployment state. Report-only.

Augmentt deploys this template in report-only mode. Entra ID evaluates every sign-in and records what would have happened in the sign-in logs, but nothing is blocked or challenged until you switch the policy to On. Review the report-only results before enforcing.

<details> <summary><strong>The 15 administrative roles in scope</strong></summary>

  • Global Administrator

  • Exchange Administrator

  • Conditional Access Administrator

  • Cloud Application Administrator

  • Authentication Administrator

  • Billing Administrator

  • Helpdesk Administrator

  • Password Administrator

  • Privileged Authentication Administrator

  • Privileged Role Administrator

  • Security Administrator

  • SharePoint Administrator

  • User Administrator

  • Global Reader

  • Application Administrator

</details>

Compliance mapping

  • CIS Microsoft 365 Foundations Benchmark v6.0.0 — section 5.2.2.4 (L1)


This is an Augmentt Default template, shipped with the product and shared across all customers. Deploying it creates a new policy in the customer tenant; edit the deployed policy rather than the template.