A pilot Entra SSO user locks the remote desktop. The client disconnects. On reconnection, an application with unsaved work is still running. No separate logoff policy has expired. How should this behavior be interpreted?

✓ Correct answer

• The default SSO lock behavior disconnected the client while the Windows session remained running.

The default Entra SSO lock behavior disconnects rather than displaying the remote lock screen. Disconnect is not logoff; a separate policy controls when the session ends, and reconnection can reevaluate authentication. Option explanations: A. Controlled Folder Access shut down Windows and restored the application.: Controlled Folder Access restricts file modification; it does not perform this session lifecycle action. B. The default SSO lock behavior disconnected the client while the Windows session remained running.: This matches the default SSO lock behavior and the observed continuing Windows session. C. Autoscale deleted the VM and recreated the application's memory.: Deleting and recreating a VM does not preserve the running application's unsaved memory state. D. Windows logged off the user and FSLogix restored the unsaved running process.: FSLogix persists supported profile data, not a logged-off process's unsaved memory. Sources: Configure single sign-on for Azure Virtual Desktop using Microsoft Entra ID — https://learn.microsoft.com/en-us/azure/virtual-desktop/configure-single-sign-on

Read the source reference