microsoft-365-docs
microsoft-365-docs copied to clipboard
Idle session timeout on unmanaged devices policy doesn't seem to be needed
For idle session timeout to get triggered on unmanaged devices, you'll need to add a Conditional Access policy in the Azure AD admin center
There must be something else you intended to say there, some other condition, because I can confirm that idle session timeout triggers for unmanaged devices without the policy. I didn't even notice the part in the article about the policy until today, so accordingly the policy does not exist in my tenant. I've had idle session timeout, however, enabled and working for a month.
None of our devices are managed/compliant.
Yet idle session timeout works for Windows 10/11 at least. With Edge or Chrome (and in Chrome's case, not even using the Windows Accounts extension). These devices are not even listed at all in Azure AD/All Devices (you can't get any more unmanaged than that). We also have some listed there as Azure AD Registered (also typically considered "unmanaged," or at least not compliant), and they work too.
So, clearly, there's something more to what you meant to say or I have a major misunderstanding about what an unmanaged device is.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
- ID: ccb07d88-8193-95d8-0e19-aa96f2d1668c
- Version Independent ID: ccb07d88-8193-95d8-0e19-aa96f2d1668c
- Content: Idle session timeout for Microsoft 365 - Microsoft 365 admin
- Content Source: microsoft-365/admin/manage/idle-session-timeout-web-apps.md
- Service: o365-administration
- GitHub Login: @KwekuA
- Microsoft Alias: kwekua
@kwekuako Please help us in resolving this issue. Thanks
@yogkumgit The answer is a typo in the article:
"The intent of that statement is to limit the policy trigger only on unmanaged devices. By default, the policy triggers for all device types (managed or unmanaged), but if you want to restrict it only to unmanaged devices, then you need to configure the CA policy as well. "
@rpodric Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/9480
Once the author approves, the changes will be live.
Thanks Sri
@msbemba Thank you very much for the contribution and updating the documentation with PR. @rpodric Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.
@yogkumgit Yes, very good. Thanks.