Current version of the Remote Desktop for Mac (Version 10.7.3 (1966) is not supporting multiple workspaces to subscribe to. The windows version of the client do support it. When will this feature be available n the Mac client as well.   Currently you have unsubscribe and subscribe again to switch between Azure Virtual Desktop Workspaces. This is not practical when you need to switch often between two workspaces. ... View more

When connecting to an AVD workspace using Microsoft Remote Desktop for Mac, the user is prompted for their password every time. You can change this by going through a semi-hidden, multi-step process to add credentials, but that is not obvious and hard to find: hover over the workspace name click the edit button. Next to user account, select add user account...  go through steps to add. select the account. save. Please make this simpler by adding the same functionality that exists for Windows where you can just select "Remember these credentials" ... View more

Hi, I upgraded to Microsoft Remote Desktop Client for Mac: 10.8.2 but a connection I use just errors on trying to connect. I restored 10.8.1 from backup and it's working fine again, so thinking it is the new version causing the problem. It is quite an old server it's connecting to for this connection. Other, more modern servers are working fine with the newer version of RDP client.   Running on Ventura, 13.3.1.   ... View more

Hi,    I am using Microsoft Remote Desktop Mac client ( https://apps.apple.com/fr/app/microsoft-remote-desktop/id1295203466?mt=12 ) everyday to connect to remote app hosted on Windows servers. I upgraded to 10.8.0 this morning and the app does not connect anymore. It throws error code 0x3000064   It fails both when using imported RDP file, and when using Workspace connection.   OS: MacOS Catalina 10.15.7   Regards, Aurélien ... View more

It would be really cool if the macOS and iOS clients of Microsoft Remote Desktop sync'd the remote desktops along with passwords via iCloud (or even some other service / mechanism, but iCloud preferred). I maintain a fairly large number of servers for clients and use multiple computers / iOS devices in my day to day work. It would be great if the Remote Desktop lists were in sync across all of my devices. ... View more

RDP for Mac version 10.7.7 has broken multiple monitor support ... View more

I regularly connect to a Windows 10 Enterprise (1909) desktop using three monitors from my macOS 12 laptop. Last night the AppStore updated Microsoft Remote Desktop to version 10.7.4 and now it not longer works when "Use all monitors" is turned on. When I connect it loads on only one monitor with a resolution of 1024x768. If I turn off "Use all monitors" I get full resolution on one monitor. To make sure it is not my laptop I downloaded the beta version of 10.7.3 from https://install.appcenter.ms/orgs/rdmacios-k2vy/apps/microsoft-remote-desktop-for-mac/distribution_groups/all-users-of-microsoft-remote-desktop-for-mac and confirmed that is worked correctly with that version. ... View more

  Connections from Mac computers running Microsoft Remote Desktop to connect to remote servers start throwing up "Error Code: 0x4" when attempting to connect to servers today. Servers are confirmed working and functional, connections are fine from Windows clients and iOS clients. Only macOS clients seem to be impacted.   I went back through the Beta Builds and tried every version.    Build 2048 was the last version of Remote Desktop for macOS that worked correctly.   Every single build since, and including, 2057 fails to connect with error 0x4.   Thanks, Scott   ... View more

The option "Use all monitors" has been working flawlesslly for me for several years (all through COVID).   A few days ago, it stopped working.  I believe it is a bug introduced in the update 10.7.7, on the MacOS version of Remote Desktop, downloaded around 29-Jun-2022.   Please fix this bug and issue an update ASAP. ... View more

Ability to add multiple workspaces as you can with the Remote Desktop client within windows OS.   Useful for working on multiple AVD implementations for customers requires this flexibility whereas right now, I use multiple incognito browser sessions to facilitate this when working on macOS.    Running version 10.7.0 (1933) ... View more

Please allow us to choose which monitors Microsoft Remote Desktop works on (for the Mac App). For example, I would like to use my two external display monitors to run and display Microsoft Remote Desktop and continue to have my MacBook display maintain its space. Currently, if I have my MacBook open and start MRD, all three displays run MRD and its a hassel to try and minimize the screen on my MacBook and continue to work with the two externals. I would like a setting that allows MRD to recognize all displays and lets you choose which ones to open MRD on. ... View more

How to reproduce: Connect to your Windows (10\11) from MacOS RDP Client  Open Visual Studio 2019 with some source file Try scroll source code file up and down with macbook trackpad Actual Result:  Small and medium finger speed on trackpad does not start scrolling at all Hard push finger speed scroll a lot of lines of source file up\down, so it hard to scroll to specific code line Expected Result: Please make the trackpad scrolling experience via macos RDP client just the same as without RDP (native) for line-based scrolling UI applications (Like VS2019) ... View more

Hello! After update Microsoft Remote Desktop 10.8.2 (Mac OS 13.3.1) can't connect to Windows Server 2003. 10.8.1 connect without any problem. ... View more

Microsoft Remote Desktop client for Mac has a long and ghastly history. (Yes ghastly is the right word and this is not a typo where 'glorious' should have been used.)   Version 1.x had a bug whereby anybody using a Mac with a non-US keyboard was tortured by the software failure to map keys correctly to the Windows session. The most infamous examples of this where that the Mac " (speech marks) key would generate an @ (at symbol) in Windows and vice versa although a number of other incorrect key mappings also apply.   Version 2.x did finally fix this bug.   Microsoft then bought a 3rd party RDC client and this became the next Microsoft official client and I cannot remember if this was released as version 5.x or 7.x. Regardless as this was new/different code it REINTRODUCED THE SAME BUG!!!   Note: I have just reproduced this with Microsoft Remote Desktop 10.8.1 (2048) running under macOS Ventura 13.2.1 with as mentioned a UK Mac keyboard.   Literally thousands and thousands of Mac users throughout the world except the USA have been complaining about this ever since.   When I last was personally victimised by Microsoft with this issue many years ago I also reported this but I found that the Parallels Remote Desktop Client for Mac did not have this bug. The reason being it was not written by American programmers who are wilfully ignorant regarding international keyboard layouts.   Unfortunately I now once more have to use an RDC client and I am finding that the Parallels client whilst still available is not connecting to the Microsoft RDC server whereas the Microsoft client does successfully connect even if it then inflicts cruel and unusual punishment in the form of this now ancient keyboard mapping error.   I have however been able to prove that the RDC client for Mac available here - www.jumpdesktop.com DOES connect to the same Microsoft RDC server and DOES NOT have this keyboard mapping bug. However the JumpDesktop client is a chargeable product.   Microsoft over the decades has in a number of cases committed grave offences against Mac-kind but in more recent times has been comparatively friendly to the Mac using community. Why therefore is this bug which affects potentially BILLIONS of people around the world i.e. anyone who does not have a Mac with an American keyboard still not been fixed?   PLEASE FIX IT AT LONG LAST!   How to reproduce. 1. Connect a non-US keyboard to a Mac, this could be a USB or Bluetooth keyboard, it does not have to be an Apple brand keyboard but genuine Apple keyboards would be the most common use. 2. The Mac should be configured to use the relevant keyboard layout - in my case this is UK but I know that it affects all other non-US layouts e.g. French, German, etc. 3. Connect to a Windows RDC session 4. On the Windows desktop open an app like Wordpad 5. On the Mac type in to the Wordpad document abcdefghijklmnopqrstuvwxyz these all map correctly. Now on the Mac type the @ (at) symbol, in Window you will instead see the " (speech marks) symbol, now on the Mac type the " (speech marks) symbol, in Windows an @ (at) symbol will appear. As mentioned other keys like the \ (back slash) are also incorrectly mapped. 6. Download the trial version of the JumpDesktop client 7. Use JumpDesktop to connect to the SAME Windows RDC server 8. Repeat the same typing test in to Wordpad, this time all the keys are correctly mapped with no settings having to be altered either on the Mac or in Windows.   Conclusion, Microsoft programmers are at fault. ... View more

10.7.7 appears to have introduced an issue where the remote display no longer scales to full screen and is also only displayed on a single display when multiple displays are used.    Screenshot from 3440x1440 external monitor.                 ... View more

Since the update to MacOs 12, I started having problem with the clipboard transfer . The clipboard transfer between my Mac and a Remote Desktop Windows session . All of a sudden during the session , the clipboard transfer ceases to work . I have not found the trigger . The best resolution right now is to disconnect and reconnect . This can happen 1 or 2 times per hour . ... View more

The Mac Microsoft Remote Desktop Beta client for Azure VD either supports full screen (one monitor) or Use All Monitors.   I have 3 monitors (including my Macbook) and would like to use 2 of them for Azure VD and one for other purposes. I cannot select just 2.   In addition, If i start a session with one full screen monitor - i cannot mid-session change to use all 3 (or just my selected 2 in my perfect scenario), i am forced to disconnect and then choose 'use all monitors'.   Looking forward to this being a feature! ... View more

When I update the version 10.8.2(2057), the desktop show below.   It worked well before I update it.     ... View more

The macOS Remote Desktop Client still cannot authenticate against a Remote Desktop using a Smart Card. I know this was the most popular request on UserVoice, before Microsoft shut down their account there. Seems like M$ is not interested in security, if it doesn't make them money.   Note: Not talking about Smart Card redirect here, but authentication in the first place, instead of username + password. ... View more