Web apps should sign out idle users on unmanaged devices within three hours
This check looks at the idle session timeout setting that signs users out of Microsoft 365 web apps after a period of inactivity. The safe setting is a timeout of three hours or less for sessions on unmanaged devices.
Why it matters
People leave browsers open on personal computers, shared machines and kiosks. If the session stays signed in, whoever sits down next has the user's mail, files and chats. An idle timeout closes that window by signing the user out after a period with no activity.
Microsoft describes the feature in Idle session timeout for Microsoft 365. It applies to web apps such as Outlook on the web, SharePoint and OneDrive. Limiting the policy to unmanaged devices keeps managed company devices free of extra prompts.
How to check it yourself
In the Microsoft 365 admin center go to Settings, Org settings, Security & privacy, Idle session timeout. The page shows whether the setting is on and the chosen time.
The SharePoint side can be read with PowerShell, which does not change anything:
Connect-SPOService -Url https://CONTOSO-admin.sharepoint.com
Get-SPOBrowserIdleSignOutThe output shows Enabled, WarnAfter and SignOutAfter. To see which sessions the timeout applies to, list your Conditional Access policies in Microsoft Entra admin center, Protection, Conditional Access, and look for a policy that targets unmanaged devices with the app enforced restrictions session control.
How to fix it
In the admin center open Idle session timeout, turn it on and choose a period of three hours or less. If you want it to apply to unmanaged devices only, follow the Microsoft Learn article above: create a Conditional Access policy for the Office 365 apps with the device filter or compliance condition for unmanaged devices and the app enforced restrictions session control.
The SharePoint timeout can also be set from PowerShell; replace the example times with your own:
Set-SPOBrowserIdleSignOut -Enabled $true `
-WarnAfter (New-TimeSpan -Minutes 150) `
-SignOutAfter (New-TimeSpan -Hours 3)Test with a pilot group first. ConfigCobra only reads this setting; it never changes your tenant.
What changes when you fix it
Users on unmanaged devices, such as personal laptops and shared computers, are warned and then signed out of Microsoft 365 web apps after the idle period, and have to sign in again. Unsaved work in a web document can be lost if they ignore the warning, so tell people before the change.
Users on managed devices are not affected when the policy is scoped to unmanaged devices. Helpdesk may see more sign-in questions in the first week.
Included in
| Benchmark | CIS ID | Profile |
|---|---|---|
| CIS Microsoft 365 Foundations v7.0.0 | 1.3.2 | E3 Level 2 |
More checks in Microsoft 365 admin center
- The password expiration policy should be set to never expireCIS 1.3.1
- Administrative accounts should be cloud-only, not synced from on-premisesCIS 1.1.1
- Two emergency access accounts have been definedCIS 1.1.2
- The number of Global Administrators should be between two and fourCIS 1.1.3
- Administrative accounts should use a license with a reduced application footprintCIS 1.1.4
Go further
- Microsoft 365 admin center15 controls in this section
- CIS Microsoft 365 Foundations v7.0.0160 controls
- CIS Microsoft 365 Foundations checklistEvery control in one list, as CSV
- RemediationSee what a fix changes in your tenant before you apply it, then use the generated script
- Monitoring & DriftScheduled scans, drift detection and email alerts when a control regresses
Check this on your Microsoft 365
ConfigCobra runs this check with every other control of the CIS Microsoft 365 Foundations Benchmark, read-only.