This article details the known issues and limitations you might encounter for each platform when using Windows App.
Select a tab for the platform you're using and follow the steps.
Here are the known issues and limitations for Windows App for Windows:
Resetting user data through the user interface isn't supported. Instead, you can reset Windows App in the Windows settings. For more information, see Reset or Repair MSIX Apps.
Integration with your local Windows start menu isn't supported.
Using Private Link to connect to Azure Virtual Desktop isn't supported.
Single sign-on (SSO) with Active Directory Federation Services (AD FS) isn't supported.
Connecting to Azure Virtual Desktop in Azure Government isn't currently supported on Windows, but is planned to be supported in the future. Connecting to Windows 365 Government is supported.
Connecting to Azure Germany, Azure operated by 21Vianet, or Azure Virtual Desktop (Classic) isn't supported.
Windows App doesn't work in some environments where proxy servers require proxy/HTTP authentication.
Windows App Insider ring doesn't currently function and will be removed from the UI until fixed.
Here are the known issues and limitations for Windows App for macOS:
Microsoft Teams in a remote session doesn't enumerate individual audio devices like the local experience due to a limitation of the WebRTC framework on macOS. Instead, Teams presents the default speakers and microphone selected in the macOS settings at the time the remote session was started.
When you upgrade from Remote Desktop to Windows App, Windows App doesn't have access to your previously saved passwords in keychain. To provide Windows App access to your previously saved passwords:
Open the Keychain Access app by searching for it in Spotlight. Press Command + Space to open Spotlight, then type Keychain Access and press Enter.
Under Default Keychains, select the login keychain.
In the search box, type com.microsoft.rdc.macos. Your saved passwords are listed.
Right-click a saved password, then select Get Info.
In the new pane that opens, select Access Control, which shows a list of apps that can access the password.
Select Microsoft Remote Desktop, then select the - (minus) button to remove it from the list.
Select the + (plus) button, then navigate to the Applications folder and select Windows App.
Select Save Changes. You need to enter your keychain password to save the changes.
Repeat from step 4 for each saved password you want to provide Windows App access to.
Using screen capture protection in Azure Virtual Desktop has the following limitations. For more information, see Platform considerations for screen capture protection on macOS.
- Enabling SCP may interfere with screen sharing in Microsoft Teams, potentially causing shared windows to appear blank or not display properly. If Teams-based collaboration is required, screen capture protection may need to be temporarily disabled on the device.
- Some native applications might not fully respect screen capture protection enforcement. This is a limitation of the operating system's available APIs, not a defect in screen capture protection itself.
Here are the known issues and limitations for Windows App for iOS/iPadOS:
The camera redirection protocol (MS-RDPECAM) doesn't support dynamically changing the camera resolution or orientation while the camera is in use, such as when rotating the device. To work around this issue, you can:
- Stop using the camera, then start the camera again.
- Change which camera you're using. For example, in the camera app and assuming you're using the front camera, change to the rear camera, then back to the front camera.
On an iPhone with a display size smaller than 6.1 inches, you only get small device thumbnails by design.
Windows App on Apple Vision Pro in compatibility mode (preview) doesn't support multi-window.
When using Teams optimizations (preview) on Windows App on an iPhone, users might experience low audio output volume playing only from the earpiece speakers. Users are recommended to use Bluetooth headphones as a workaround. This doesn't affect iPad devices.
Here are the known issues and limitations for Windows App for Android and Chrome OS:
- You can't connect to Windows 365 Frontline.
Here are the known issues and limitations for Windows App in a web browser:
Using Private Link to connect to Azure Virtual Desktop isn't supported.
Single sign-on (SSO) with Active Directory Federation Services (AD FS) isn't supported.
Connecting to Azure Virtual Desktop in Azure Government isn't currently supported in a web browser, but is planned to be supported in the future. Connecting to Windows 365 Government is supported.
Connecting to Azure Germany, Azure operated by 21Vianet, or Azure Virtual Desktop (Classic) isn't supported.
Direct launch is for Windows 365 resources only.
Downloading a .rdp file for connection with Windows App on a different platform.
When a user uses Microsoft Defender for Cloud Apps, they can land on the home page for Windows App instead of the full path of their link. Users can fix this issue by appending .mcas.ms to the URL. For more information, see Navigating to a particular URL of a suffixed app and landing on a generic page.
Copy and paste works as expected when using keyboard shortcuts, such as CTRL+C for copy and CTRL+V for paste, but not initially when using copy and paste from a right-click context menu where the paste option isn't available. This behavior happens because Windows App doesn't have access to the clipboard content until you initiate a copy and paste action from the keyboard, at which point the paste option is available.
Related content
Learn more about troubleshooting Windows App: