Microsoft is planning to release any update on Azure Web Application Proxy Connector version to Support 3rd Party browser or not ?
Publish RDS with Azure Application Proxy without exposing RDGateway
I was recommended to publish my question here instead of twitter: https://twitter.com/MrRobama/status/1245059086955220992?s=20
Is there any way I can publish RDS with Azure Application Proxy and avoid exposing the RD Gateway on the internet?
As far as I can tell.. If I want to use Azure Application proxy and leverage SSO then I have to set the authentication mode to passhtrough. This works but completely defeats the purpose. I want to preauthenticate using Azure AD (to use with MFA and Conditional Access) and also have SSO to RDGateway.
right now I can set it up so that I can preauthenticate with Azure AD but the RDGateway is still exposed on the public internet.
Would love to hear a response from you!
Sign in to comment
Sort by: Most helpful
@Robert Amartinesei I have tried to answer both your questions below:
SSO in case of Pre-authentication via Azure AD:
SSO is supported if Azure App Proxy is setup to perform pre-authentication using Azure AD. This is well documented here: https://learn.microsoft.com/bs-latn-ba/azure/active-directory/manage-apps/application-proxy-config-sso-how-to.
Also, for SSO you need to host both the RD Web and RD Gateway endpoints on the same machine with a common root. For example, if root url is https://internal-url.example.com, RD Web url will be https://internal-url.example.com/rdweb and RD Gateway url will be https://internal-url.example.com/rpc. Now while configuring app proxy, you need to create mapping only for https://internal-url.example.com url and not for /rdweb or /rpc.
RDGateway exposed on the public internet:
In an RDS deployment, the RD Web role and the RD Gateway role run on Internet-facing machines. These endpoints are exposed for the following reasons:
RD Web provides the user a public endpoint to sign in and view the various on-premises applications and desktops they can access. Upon selecting a resource, an RDP connection is created using the native app on the OS.
RD Gateway comes into the picture once a user launches the RDP connection. The RD Gateway handles encrypted RDP traffic coming over the internet and translates it to the on-premises server that the user is connecting to. In this scenario, the traffic the RD Gateway is receiving comes from the Azure AD Application Proxy.
Please "Accept as answer" wherever the information provided helps you to help others in the community.
There is no way to integrate full SSO with preauth in this setup. Essentially you need to authenticate with azure once and then login to the web portal once and then you're fully authenticated. The few custom configurations I've seen people post about that leverage Azure SSO actually break the security of the pre-auth since they allow for RDP files that have been created to simply be re-used without triggering MFA, which means that a custom RDP file could be worked up to sneak in this way too.
Microsoft's document on configuring RDS with pre-auth and app proxy specifically configure for the two sign-ins as I described above- https://learn.microsoft.com/en-us/azure/active-directory/manage-apps/application-proxy-integrate-with-remote-desktop-services
So I don't know what Amanpreetsingh was talking about there.