Known issues and limitations of Windows App

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.

• Connecting to Azure Germany and Azure Virtual Desktop (Classic) isn't supported.

• Pin remote resources to the taskbar from the Start menu.

Here are the known issues and limitations for Windows App for macOS:

• Some keyboard behaviors may vary on macOS due to differences in how layouts are mapped. Here are the known limitations:

  • Shortcut redirection currently works only with English keyboard layouts or layouts similar to English.

  • On certain layouts, such as German, where “Z” and “Y” are swapped, shortcuts may not behave as expected.

  • Local macOS and remote Windows sessions may use different keyboard layouts, causing mismatched shortcut interpretation.

  • Some macOS keyboard layouts do not exist on Windows, preventing consistent mapping.

• In 11.2.7, UDP transport (RDP Shortpath) is disabled by default while engineering works on fixes to improve reliability and overall experience. This is a temporary change. If admins desire to enable UDP, they can do so by setting the user defaults key: ClientSettings.EnableAvdUdpSideTransport.

• 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:

  1. Open the Keychain Access app by searching for it in Spotlight. Press + to open Spotlight, then type Keychain Access and press .

  2. Under Default Keychains, select the login keychain.

  3. In the search box, type com.microsoft.rdc.macos. Your saved passwords are listed.

  4. Right-click a saved password, then select Get Info.

  5. In the new pane that opens, select Access Control, which shows a list of apps that can access the password.

  6. Select Microsoft Remote Desktop, then select the - (minus) button to remove it from the list.

  7. Select the + (plus) button, then navigate to the Applications folder and select Windows App.

  8. Select Save Changes. You need to enter your keychain password to save the changes.

  9. 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.

• Standalone installer May Fail to Register with Microsoft AutoUpdate, Preventing Automatic Updates

  • When installed using the macOS standalone package, Windows App might not automatically register with Microsoft AutoUpdate, which can prevent the app from receiving future updates.

  • To fix this, run the following command (do not use sudo):

    defaults write com.microsoft.autoupdate2 Applications -dict-add "/Applications/Windows App.app" "{ 'Application ID' = MSRD10; LCID = 1033; 'App Domain' = com.microsoft.rdc.macos; }"
    

  • Restart Windows App and Microsoft AutoUpdate and confirm Windows App (current version) appears in the Microsoft AutoUpdate product list.

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 only sign in as an external identity that is a work or school account, or that is a Microsoft account that is signed into Authenticator as a 'Connected account'.

Here are the known issues and limitations for Windows App in a web browser:

• When using Windows App in a web browser, the text input cursor in Office apps may appear black instead of white when the Office theme is set to Dark. This can make the cursor hard to see and lead to editing mistakes. To work around the issue, you can improve visibility by manually changing the cursor color in Windows system settings inside the remote desktop session:

  • Open Settings in the Windows session.

  • Go to Accessibility.

  • Select Text Cursor from the left pane.

  • Under Text Cursor Indicator, turn it On.

  • Choose a bright color (e.g., white or yellow) for the cursor indicator to make it stand out against the dark background.

  • Apply changes and return to your Office app.

• 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 + for copy and + 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.

• In Windows App on the web, redirected local printers don't display their original printer names and instead appear as (Local printer) in the remote session. Printer redirection continues to function, but individual redirected printer names aren't currently exposed in the same way as they are in the Windows App desktop client.