Web Application Proxy is a Windows Server role that lets users securely access on-premises web applications from outside the office network. It works with Active Directory Federation Services (AD FS) to authenticate users before they reach the internal application, acting as a secure gateway.
Install Remote Access Role
The first step is to install the necessary server role. Using Server Manager, you add the Remote Access role and select the specific Web Application Proxy role service. This installs the software needed to run the proxy on your server.
Join AD FS Farm
For authentication to work, the proxy server must connect to your existing AD FS setup. During the proxy's configuration wizard, you provide the name of your AD FS server and administrative credentials. This joins the proxy to the AD FS farm, establishing a trust so it can forward user authentication requests.
Secure connections are mandatory. You must obtain an SSL certificate from a trusted Certificate Authority (CA) and install it on the Web Application Proxy server. This certificate is then bound to the proxy service, typically through IIS Manager or the proxy configuration, to encrypt all traffic between external users and the published applications.
Application Publishing Rules
To make an internal application available, you create a publishing rule. In the Remote Access Management Console, you specify both the Internal URL (how the app is accessed inside the network) and the External URL (the address users will type from the internet). You configure the preauthentication method, such as Microsoft Entra ID, to integrate with your identity provider for single sign-on.
Verify External Connectivity
After setup, you must test from outside the corporate network. You access the application using the External URL to confirm that the connection is secure (HTTPS), that AD FS authentication prompts correctly, and that you can successfully reach the internal web application.