Azure Application Proxy is a powerful tool that enables secure remote access to on-premises web applications. It allows users to access these applications from anywhere, while ensuring the security and integrity of the underlying infrastructure. In this step-by-step guide, we will walk you through the process of setting up Azure Application Proxy, so you can easily and securely publish your on-premises web applications to the cloud.
What is Azure Application Proxy?
Azure Application Proxy is a feature of Azure Active Directory that enables remote access to on-premises web applications through the Azure portal. It acts as a secure intermediary between users and the on-premises application, eliminating the need for complex VPN configurations or exposing the application directly to the internet. With Azure Application Proxy, you can provide seamless and secure remote access to your on-premises web applications without compromising on security.
Prerequisites
- Azure Active Directory: You must have an active Azure Active Directory (AAD) tenant with Basic or Premium license. If you don’t have one, you can create it by following the instructions in the Azure portal documentation.
- Azure Subscription: You need an active Azure subscription to use Azure Application Proxy. If you don’t have an Azure subscription, you can sign up for one at the Azure portal.
- On-Premises Network: Azure Application Proxy requires a functioning on-premises network with the following components:
- Web Application: You should have an on-premises web application that you want to publish to Azure.
- Server: A server or virtual machine within your on-premises network is required to host the Azure Application Proxy connector. This server should meet below system requirements specified by Microsoft.
- Network Connectivity: The server hosting the connector should have network connectivity to the on-premises web application that you want to publish.
- Permissions: You need appropriate permissions within your Azure AD tenant to configure and manage Azure Application Proxy. Typically, this requires being a member of the Azure AD Global Administrator or Application Administrator role. Ensure that you have the necessary permissions before proceeding with the setup.
- System Requirements: Before installing the Azure Application Proxy connector, ensure that the following prerequisites are met:
- Operating System:
- Windows Server: The connector is designed to run on Windows Server operating systems. The supported versions may vary, but typically Windows Server 2016, Windows Server 2019, or later are recommended.
- Hardware:
- Processor: A 64-bit processor with at least 2 cores is recommended.
- Memory: A minimum of 4 GB of RAM is recommended. The actual memory requirements may vary depending on the workload and the number of connections.
- Disk Space: The connector requires at least 10 GB of free disk space for installation and operation.
- Network Connectivity:
- Internet Access: The on-premises server hosting the connector should have internet access to download the connector software and establish a connection with Azure.
- Outbound Connectivity: The server should have outbound connectivity to the Azure Application Proxy service and the on-premises web application that you want to publish.
- Ports:
- The connector requires outbound access to specific ports for communication with Azure. Ensure that the following ports are open in your network firewall:
- Port 80 (HTTP)
- Port 443 (HTTPS)
- Port 8888 (for connector registration)
Step 1: Configure Azure Active Directory
Before setting up Azure Application Proxy, ensure that you have an Azure Active Directory (AAD) tenant. If you don’t have one, you can create it by following the instructions in the Azure portal documentation.
Step 2: Install and Configure the Azure Application Proxy Connector
To set up Azure Application Proxy, you need to install and configure the Azure Application Proxy connector. The connector acts as a bridge between your on-premises network and Azure. Follow these steps:
- In the Azure portal, navigate to Azure Active Directory.
- Select Application Proxy from the left-hand menu.
- Click on the Download connector button to download the connector software.
- Install the connector software on a machine within your on-premises network.
- After installation, sign in to the connector using your Azure AD credentials.
- Follow the on-screen prompts to complete the configuration process.
Step 3: Publish On-Premises Web Applications
Once the connector is installed and configured, you can start publishing your on-premises web applications to Azure. Follow these steps:
- In the Azure portal, navigate to Azure Active Directory.
- Select Application Proxy from the left-hand menu.
- Click on the Add a publishing button.
- Select Add an internal web application.
- Fill in the required details, such as Name, Internal URL, and External URL.
- Choose the appropriate Preauthentication method based on your requirements.
- Click on the Add button to publish the application.
Step 4: Configure Additional Settings
Depending on your specific requirements, you may need to configure additional settings for your published web applications. Azure Application Proxy offers several options to enhance security and optimize the user experience. Some of the key configurations include:
- Single Sign-On (SSO): Enable SSO for your published applications to provide a seamless user experience.
- Conditional Access: Implement conditional access policies to control access to your applications based on specific conditions.
- Custom Domains: Configure custom domains to provide a branded experience for your users.
Step 5: Test and Verify
After completing the setup and configuration, it is essential to test and verify the functionality of your published web applications. Perform the following checks:
- Access the application using the provided external URL.
- Verify that the application functions as expected.
- Test the security features, such as SSO and conditional access policies.
Conclusion
Setting up Azure Application Proxy allows you to securely publish your on-premises web applications to the cloud, providing remote access to your users while maintaining control and

Leave a ReplyCancel reply