Forum Discussion

Daphne_Kallinderi's avatar
Jul 10, 2026

Windows App expands auto logoff support to managed Android devices (Public Preview)

We're excited to announce that Windows App auto logoff on Android is now in public preview, giving administrators a simple, Mobile Device Management (MDM)–configured way to keep shared devices clean between sessions. Already available on Windows, auto logoff now extends to MDM-enrolled Android devices, a key step toward enabling frontline and shared-device scenarios on Android hardware. 

What is auto logoff?

Windows App auto logoff on Android is an admin-configured setting that signs the user out of Windows App and removes locally stored app data when the app is closed, disconnected, or left inactive for a configured period. By removing locally stored app data, auto logoff helps ensure that every session starts with a clean state when users sign in with their own credentials.  

It's designed for operational convenience and device hygiene — not as a security boundary — and it does not interrupt active Azure Virtual Desktop or Windows 365 sessions. Only the local Windows App state is reset.

Why it matters for shared devices

Auto logoff is ideal for shared-device deployments where Windows App is the primary app users interact with to access Azure Virtual Desktop or Windows 365: 

  • Clean handoffs: when one worker finishes and closes the app, the next person signs in fresh
  • Local Windows App data is removed automatically: cached app data is cleared when configured logoff conditions occur (app close, disconnect, or inactivity)
  • Streamlined re-entry: an optional setting skips the onboarding and privacy screens after logoff, so shared agreements are accepted once per device rather than by every user
  • Flexible triggers: reset on app close, sign-out, remote-session disconnect, or after a defined period of inactivity 

How to configure it

Windows App auto logoff on Android is set from your MDM admin console (for example, Microsoft Intune) via a managed app configuration profile assigned to Windows App. Core settings include: 

  • Enable auto logoff: the master switch (off by default)
  • Inactivity timeout: minutes of idle time (with the screen locked) before Windows App signs out and resets; set to 0 to rely only on close/disconnect triggers
  • Skip first-run experience: recommended for shared devices so users aren't re-prompted through setup 

The setting names and value types are the same across MDM providers, only the admin UI differs. 

Prerequisites

  • Windows App version 11.0.0.113 or later on a supported Android device
  • The device enrolled in your MDM, with Windows App installed as a managed app
  • Admin access to a supported MDM provider that can deliver app configuration to Windows App 

Note: Inactivity-based auto logoff depends on the Android device’s screen lock setting. If a device is configured never to lock, the inactivity timer won't fire (close, sign-out, and disconnect triggers still work). 

Learn more 

For the full setup walkthrough, configuration examples, and known limitations, see Configure auto logoff for Windows App on Microsoft Learn. 

We'd love to hear how you're using auto logoff for your shared-device and frontline deployments, drop a comment below and let us know what scenarios you'd like to see us light up next.

1 Reply

  • This is a useful addition for frontline and shared-device scenarios. Extending auto logoff to managed Android devices should make user handovers much cleaner, especially where Windows App is used to access Azure Virtual Desktop or Windows 365.

    The option to clear local app data while leaving the remote session unaffected is particularly practical. The configurable triggers and ability to skip the first-run experience should also reduce friction for users on shared devices.

    It will be interesting to see how this develops after the public preview, especially around reporting, troubleshooting, and integration with Android shared-device mode.