Thanks @planteg. We've long experience of using the Mac version of Remote Desktop since the demise of Citrix XenApp Fundamentals which we used to stream FileMaker Pro from cloud servers to macOS since 2011.
First to emphasise how good Jump Desktop is. We manage 20+ Windows servers, both on the cloud and on clients sites and for this, there is nothing as good for macOS. We protect all our servers by requiring SSH connections for full RDP sessions and the built in SSH tuneels makes this a breeze. It does fall behind Remote Desktop/Windows App in workspaces where it still provides an MDI rather than SDI type environment (think FileMaker 15 compared to 16 onwards). However, in every other way, it beats the Microsoft product for RDP Windows support and access (and supports VNC as well).
Equally, the vast majority of our clients use Remote Desktop and now the Windows App for streaming FileMaker Pro as a workspace from Windows RemoteApp servers.
The upgrade from Remote Desktop to Windows App results in some helpdesk calls, as Microsoft (or the App Store) silently replaces Remote Desktop with Windows App, hence any shortcuts in the Dock just disappear. We've had to create a single page PDF to email to our clients showing them how to find the Windows App in Applications and drag it to the dock. I've no experience as to whether a desktop shortcut would any differently. However, after that we've had no operational problems, with Windows App.
Let's be very clear, this is just a rebranding, this is not a completely new app and is simply the next version of what Remote Desktop would have been. We've found no nasty surprises.
One thing to watch out for as FileMaker developers, and as we use workspaces (i.e. just FileMaker) and not the full RDP Windows Explorer environment, we've always had problems matching our UK keyboards (Jump Desktop supports virtually all international keyboards) to a point we add a custom keyboard to each Windows RemoteApp server. This is unnecessary for our FileMaker users by changing the keyboard mode from Scancode to Unicode and it works fine after that. Unless, as a developer, you're used to being able to find table occurrences by typing the first few letters of a TO name, or typing immediately in a script with out using the space bar to add new script step, in which case we have to revert to Scancode.
I'm probably the wrong person to fully comment on using the full RDP control of a Windows server/PC, as for this we simply turn to Jump Desktop. But in terms of the move from Remote Desktop to Windows App, other than the background replacement of the former to the latter, this is just a rebrand and we don't believe there are any nasty surprises.
What I would say is that Microsoft are very progressive with this app. We've been on the beta program for years and the Mac team there used to have access to FileMaker on one of our cloud servers to fix FileMaker related problems we reported. We lost that communication when Microsoft moved from the HockeyApp platform to their current one. However, I reported a problem with their latest beta release yesterday on the feedback website, had an engineer confirm that they had replicated this and had a fix for it, which has been released today and it has fixed it.
Regards
Andy