Today’s release of Idle session timeout will allow IT admins to configure a tenant-wide timeout policy to automatically sign out users after a period of inactivity on Microsoft 365 web apps. This will help protect sensitive company data from unauthorized access while providing peace of mind for end users while working on unmanaged and/or shared devices. This feature is an improvement over, and will eventually replace, current app-specific idle timeout settings in Outlook Web App (OWA) and SharePoint Online (SPO). This message is associated with Microsoft 365 Roadmap ID 55183.
Idle session timeout feature allows IT admins to configure a tenant-wide timeout value based on which users get automatically signed out after a period of inactivity on Microsoft 365 web apps. This feature is an improvement over, and will eventually replace, current idle timeout settings in Outlook Web App (OWA) and SharePoint Online (SPO).
- Microsoft 365 suite
When this will happen
- Preview: Began rolling out today and is expected to be complete in late March.
- Standard: Microsoft will begin rolling this out in late June and expect to complete rollout late August.
How this will affect your organization
With this update, admins will have the ability to control how long a user can remain inactive on a Microsoft 365 web app before they get signed out automatically. By default, Idle session timeout feature is turned off for an organization. You can opt in via UX in Microsoft 365 Admin Center using the steps described here.
Once this feature is turned on for your organization, users who access Microsoft 365 web apps from an unmanaged device and do not select ‘Stay signed in?’ option at the time of sign-in might start seeing more sign-in prompts. Other users will not get impacted by this change.
Idle Session Timeout Setting
Idle Session Timeout Prompt
What you need to do to prepare
As you try out the Idle session timeout feature, you might want to notify your users about this change and update your training and documentation as appropriate.
- Please note that Microsoft are not yet retiring the existing functionalities in OWA and SPO. But in order to better prepare your organization for this change, Microsoft recommend you trying out the new feature now and migrate to it once it becomes generally available.
Microsoft always value feedback and questions from our customers. Please feel free to submit either feedback or questions here.
Message ID: MC343441
Published: 16 March 2022
Updated: 16 March 2022
Major change: False
#NewFeature #UserImpact #AdminImpact #Office #365Apps #Microsoft365