Support Remote Desktop Web Client HTML5 on Azure AD App Proxy
Microsoft doesn't support the Azure AD Application Proxy on RD WebClient (HTML5). Like this MFA and Condintional Access would be possible.
Another benefit is that HTML5 works on all Webbrowsers without downloading software.
We’ve just release support for this: https://techcommunity.microsoft.com/t5/azure-active-directory-identity/azure-ad-application-proxy-now-supports-the-remote-desktop/ba-p/1257367.
Thank you all for your patience and feedback!
this is such a critical piece of making web client a viable option for any organization. Web Client is a very much welcomed extension to RDS but it's lacking a core feature to protect a perimeter endpoint. We were hoping the latest update released on 8/27 was going to include this - we can't roll out web client until this works. NPS extension provides a work around but still lacks the ability to control white listed IP ranges and requires hand holding of each user to download auth. app and set it up correctly (allow sign in from this device).
Yes yes yes!
Getting this to work would make it an exceptional exceptional capability. Potentially letting in clients from any HTML5 capable browser. RDweb via azure app proxy is shonky at best and the dependency on IE is, lets face it, an archaic approach given MS's direction of travel....
I see version 184.108.40.206 was released, but there's no release notes. Was this feature released in 220.127.116.11?
Pretty please make this available
Is there a tech pre view ready yet?
Please get this working with AAD Application Proxy - we use this for all our external facing services and it makes no sense why the RDS Web Client can't be published using Microsoft's preferred technology for Remote Access
Dave Jopson commented
Eight months later and your update isn't really an update. Well done guys *Slow hand clap*
Some Body commented
Please make the web client available for Azure Application Proxy.
Just installed RDS on Server 2019 in parallel to our existing 2016 RDS infrastructure. RD Web Client STILL does not work through the app proxy. See no benefit in upgrading to 2019 if this functionality is not going to be added. Would really like to switch to the new interface for remote users and be able to more seamlessly use non-IE browsers.
Providing this feature would enable proper MFA logon and the other inbuilt Azure / ADFS DoS mitigation across platforms.
The only other alternative solutions I have found (both depend on RDP client):
RD Gateway over App Proxy or ADFS - Must use Internet Explorer and ActiveX
RD Gateway with NPS / Radius extension to provide MFA - Bad user experience and vulnerable to DoS attack
The Remote Web Client appears to look and function identically to WVD and that has MFA.
Any time table on this feature?
+1 HTML 5 for all devices without ActiveX is really a needed functionality!
Any idea when this will be available ?
Stick it in Azure commented
Just adding another message of support for this change. I have two customers running RDS2016 via Azure AD App Proxy, clients for both are forced into using IE11 due to the ActiveX component which is not ideal. Moving these clients to the HTML5 version via the Azure AD Proxy would increase adoption of the platforms significantly. Eagerly awaiting this!
Jesse C commented
One more vote here to get AAD App Proxy working with the 2019 RDS web client. Any update on the progress?
Pantelis Apostolidis (MVP) commented
Hi team, do we have any updates about Support the Web Client (HTML5) with Azure AD Application Proxy?
We're another AzureADP2 customer seeking AAD Application Proxy support for the RemoteDesktop WebClient; we've ~1000-1500 users awaiting such a solution.
Mark Fuller commented
So what time scale are we looking for this for support with azure application proxy and the html rd client?
I'm interested in a simple way to provide pre-authenticated RDP access for specific users (including guest users) in Azure AD to shared, standalone VMs sitting outside the internal network. Until Azure AD join is supported on Server, I'm left without an elegant option.
we just want to be able to leverage Azure MFA without having the ridiculous NPS hack/workaround.
AAD app proxy introduces a lot of extra latency into the picture unnecessarily...