Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions articles/desktop-flows/run-desktop-flows-pip.md
Original file line number Diff line number Diff line change
Expand Up @@ -147,7 +147,9 @@ When set to **Custom**, you can enter a custom user data folder to be used by th
- Certain Windows policies and configurations might not let picture-in-picture automatically connect without asking for credentials. To work around this issue, don't close the picture-in-picture session after every flow run. Use the same session for consecutive flow runs to avoid entering credentials every time. Asking for credentials is expected behavior for picture-in-picture and complies with the local security policies of the machine.
- If the picture-in-picture functionality doesn't work, troubleshoot by checking whether you can use Remote Desktop to connect to the machine running Power Automate for desktop from another machine and connect from the local machine to other machines.
- Issues might occur when several VPN clients are used in a picture-in-picture session. The identified issues are related to app sign out, and the VPN client identified so far is Zscaler.
- To avoid issues related to Cross Device service, disable the auto-start setting for the Mobile Devices service.
- If smartcard is used to sign in to Windows, the following policy should be set to *Not Configured* or *Disabled*:
- `Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Device and Resource Redirection\Do not allow smart card device redirection`
- Picture-in-Picture is currently not supported on Azure AD joined cloud machines.

[!INCLUDE[footer-include](../includes/footer-banner.md)]