Study guide

12.4 Web Application Proxy & Microsoft Entra Application Proxy

Administering Windows Server Hybrid Core Infrastructure AZ-800

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

About Exam AZ-800: Format, Scoring & the September 2026 Retirement

2 Chapter 1: Active Directory Domain Services Architecture & Deployment

1.1 Deploying & Managing Domain Controllers On-Premises 1.2 Domain Controllers in Azure IaaS & Virtualized DC Cloning 1.3 Read-Only Domain Controllers (RODCs) & Password Replication Policies 1.4 Flexible Single Master Operation (FSMO) Roles & Troubleshooting 1.5 Active Directory Sites, Subnets & Site Link Topology 1.6 AD DS Replication: Topology Generation, Convergence & Diagnostics 1.7 Forest and Domain Trust Relationships

3 Chapter 2: AD DS Security Principals, Service Accounts & Domain Join

2.1 Managing Users, Groups & Objects in Multi-Domain and Multi-Forest Environments 2.2 Service Account Types & Group Managed Service Accounts (gMSA) 2.3 Joining Windows Server to AD DS, Microsoft Entra Domain Services & Microsoft Entra ID 2.4 Creating & Managing Users, Groups and Organizational Units at Scale

4 Chapter 3: Hybrid Identity & Microsoft Entra Integration

3.1 Microsoft Entra Connect Sync Architecture, Installation & Filtering 3.2 SourceAnchor, Synchronization Rules & Microsoft Entra Connect Health 3.3 Microsoft Entra Cloud Sync & Disconnected Multi-Forest Topologies 3.4 Hybrid Authentication Methods & Staged Rollout 3.5 Microsoft Entra Domain Services 3.6 Integrating Microsoft Entra ID, AD DS & Entra Domain Services: Choosing an Architecture

5 Chapter 4: Group Policy in AD DS and Hybrid Environments

4.1 Group Policy Architecture & Processing Order (LSDOU) 4.2 Group Policy Filtering, Loopback Processing & Client-Side Extensions 4.3 Group Policy Preferences, Item-Level Targeting & Central Store 4.4 Group Policy in Microsoft Entra Domain Services & Fine-Grained Password Policies

6 Chapter 5: Remote Server Management in Hybrid Environments

5.1 Windows Admin Center (WAC) Deployment On-Premises and in Azure 5.2 PowerShell Remoting, WinRM & the Kerberos Double-Hop Problem 5.3 Just Enough Administration (JEA) for Constrained PowerShell Endpoints 5.4 OpenSSH on Windows Server & PowerShell Remoting over SSH 5.5 Secure RDP Access, Remote Desktop Gateway & Azure Bastion

7 Chapter 6: Hybrid Management with Azure Arc and Azure Services

6.1 Azure Arc-Enabled Servers Architecture & Onboarding 6.2 Azure Machine Configuration & VM Extensions on Arc Servers 6.3 Azure Update Manager: Assessment, Maintenance Configurations & Dynamic Scoping 6.4 Azure Automation for Hybrid Workloads: Runbooks & Hybrid Runbook Workers

8 Chapter 7: Hyper-V Virtualization & Virtual Machine Configuration

7.1 Hyper-V Type 1 Architecture, Installation & Hardware Prerequisites 7.2 VM Generations, Secure Boot, vTPM, Enhanced Session Mode & Direct VM Access 7.3 Compute, Dynamic Memory & Hardware Acceleration 7.4 VM Resource Controls, CPU Groups & Host Compute Partitioning 7.5 Hyper-V Virtual Hard Disks & Checkpoint Management 7.6 Hyper-V Virtual Switches, NIC Teaming & Switch Embedded Teaming (SET) 7.7 Integration Services, Guest Components & Time Synchronization

9 Chapter 8: Hyper-V High Availability, Security & Containers

8.1 Hyper-V Failover Clustering & Cluster Shared Volumes (CSV) 8.2 Hyper-V Replica & Azure Site Recovery (ASR) 8.3 Guarded Fabric & Shielded Virtual Machines 8.4 Windows Server Container Hosts, Isolation Models & Images 8.5 Managing Container Instances & Linux Containers with WSL 8.6 Windows Container Networking & AKS Enabled by Azure Arc 8.7 Managing Container Images, Tags & Azure Container Registry

10 Chapter 9: Azure IaaS Virtual Machine Administration

9.1 Azure VM Sizing, Series Selection & Managed Disk Tiers 9.2 Azure VM Host Caching, Disk Bursting, Ephemeral OS Disks & Disk Operations 9.3 Azure VM High Availability: Availability Sets, Zones & Proximity Placement Groups 9.4 Virtual Machine Scale Sets, Autoscale & Azure Dedicated Hosts 9.5 Azure VM Networking, NSGs & Connectivity

11 Chapter 10: Hybrid DNS Infrastructure & Name Resolution

10.1 Active Directory-Integrated DNS Architecture, Dynamic Updates & Zone Types 10.2 DNS Records, Aging & Scavenging and the GlobalNames Zone 10.3 DNS Forwarding, Conditional Forwarding & Azure DNS Zone Integration 10.4 Hybrid Name Resolution with Azure DNS Private Resolver 10.5 Windows Server DNS Policies & DNSSEC

12 Chapter 11: IP Addressing, DHCP & IPAM Management

11.1 DHCP Server Role, the DORA Lifecycle & Active Directory Authorization 11.2 DHCP Scopes, Option Hierarchy, Reservations & Relay Agents 11.3 DHCP High Availability & Failover Configurations 11.4 IP Address Management (IPAM) Deployment & Auditing 11.5 Resolving IP Address Issues in Hybrid Environments

13 Chapter 12: Hybrid Network Connectivity, Remote Access & Private Access

12.1 Remote Access Role, VPN Protocols & Site-to-Site VPN to Azure 12.2 Network Policy and Access Services (NPAS), RADIUS & Policy Processing 12.3 Azure Network Adapter & Azure Extended Network 12.4 Web Application Proxy & Microsoft Entra Application Proxy 12.5 Microsoft Entra Private Access & Global Secure Access 12.6 Azure Relay & Hybrid Connections

14 Chapter 13: File Services, DFS, SMB & Azure File Sync

13.1 Windows Server File Share Access, NTFS Permissions & Access-Based Enumeration 13.2 File Server Resource Manager: Quotas, File Screens & Storage Reports 13.3 DFS Namespaces (DFS-N) & DFS Replication (DFS-R) 13.4 BranchCache: Distributed Cache and Hosted Cache Modes 13.5 Modern SMB Protocols, SMB Multichannel & SMB over QUIC 13.6 Azure File Shares, Tiers & Hybrid Permissions 13.7 Azure File Sync, Cloud Tiering & Monitoring 13.8 Migrating DFS Namespaces & DFS Replication to Azure File Sync

15 Chapter 14: Windows Server Storage Infrastructure & High Availability

14.1 Disk Partitioning, Volumes & Enterprise File Systems (NTFS vs ReFS) 14.2 Data Deduplication Architecture, Usage Types & Management 14.3 Storage Spaces & Storage Spaces Direct (S2D) 14.4 Storage Replica & Storage Quality of Service 14.5 iSCSI Target Server, IQNs, CHAP Authentication & Multipath I/O

12.4 Web Application Proxy & Microsoft Entra Application Proxy

Key Takeaways Explain This Topic AI

The application publishing paradigm has evolved from perimeter DMZ reverse proxies (WAP/AD FS) to outbound-only cloud reverse proxies (Microsoft Entra Application Proxy) and finally to protocol-agnostic Zero Trust Network Access.

Web Application Proxy (WAP) is a role service of the Windows Server Remote Access role, is deployed in the DMZ, is deliberately not domain-joined, and requires an inbound TCP 443 firewall pinhole plus pre-authentication via AD FS or pass-through.

Microsoft Entra Application Proxy eliminates every inbound firewall port by having a lightweight on-premises private network connector hold persistent outbound HTTPS (TCP 443) connections to *.msappproxy.net and *.servicebus.windows.net.

Entra Application Proxy performs pre-authentication in Microsoft Entra ID, so Conditional Access policies such as MFA, device compliance, and sign-in risk apply before a packet ever reaches the internal web server.

Single sign-on to a backend using Windows Integrated Authentication requires Kerberos Constrained Delegation (KCD) on the connector's computer object, using the S4U2self and S4U2proxy extensions.

Last updated: August 2026

Web Application Proxy & Microsoft Entra Application Proxy

Traditional enterprise application publishing relied on perimeter demilitarized zones (DMZs), inbound firewall port exceptions, public IP addresses, and broad network-layer VPNs. These legacy architectures create substantial attack surfaces: opening inbound firewall ports exposes web servers to zero-day internet scans, while traditional VPNs grant remote devices broad network-level access, allowing lateral movement in the event of an endpoint breach.

Microsoft's modern application publishing ecosystem implements Zero Trust principles across three generations of technology. This section covers the first two — Web Application Proxy (WAP) for perimeter AD FS federation and Microsoft Entra Application Proxy for outbound-only web application publishing, both of which are limited to HTTP/HTTPS. The third generation, Microsoft Entra Private Access , extends the same identity-centric model to every protocol and is covered in section 12.5; Azure Relay , which solves the narrower problem of exposing a single on-premises TCP endpoint to an Azure PaaS service, is covered in section 12.6.

1. Evolution of Remote Application Publishing

Understanding the architectural trajectory from legacy perimeter DMZs to cloud-delivered Security Service Edge (SSE) is vital for enterprise design and AZ-800 certification. +-----------------------------------------------------------------------------------+

  • | EVOLUTION OF APPLICATION ACCESS PARADIGMS |
  • | |
  • | [GENERATION 1: PERIMETER DMZ] |
  • | - Web Application Proxy (WAP) + AD FS |
  • | - Requires Inbound Port 443, Public IPs, Perimeter DMZ, Public DNS |
  • | - Lateral Movement Risk: Moderate (DMZ Isolation) |
  • | | |
  • | v |
  • | [GENERATION 2: CLOUD REVERSE PROXY] |
  • | - Microsoft Entra Application Proxy |
  • | - Outbound-only HTTPS (Port 443), Zero Inbound Ports, Entra ID Pre-Auth (MFA) |
  • | - Scope: HTTP / HTTPS Web Applications Only |
  • | | |
  • | v |
  • | [GENERATION 3: ZERO TRUST NETWORK ACCESS (ZTNA / SSE)] |
  • | - Microsoft Entra Private Access (Global Secure Access) |
  • | - Outbound-only Connectors + GSA Client on Endpoints |
  • | - Scope: ALL Protocols & Ports (TCP, UDP, RDP, SMB, SSH, Kerberos, Legacy ERP) |
  • +-----------------------------------------------------------------------------------+
  • Comparative Architectural Matrix

Architectural Metric Web Application Proxy (WAP) Entra Application Proxy Entra Private Access (ZTNA) Azure Hybrid Connections

Network Placement Perimeter DMZ Internal LAN Internal LAN Internal LAN / Server

Inbound Firewall Ports Requires Inbound 443 Zero (Outbound 443 only) Zero (Outbound 443 only) Zero (Outbound 443 only)

Supported Protocols HTTP / HTTPS HTTP / HTTPS All TCP & UDP Protocols Specific TCP Port (e.g. 1433)

Client Software Req. None (Browser-based) None (Browser-based) Global Secure Access Client None (PaaS integration)

Pre-Authentication AD FS / Pass-through Microsoft Entra ID (MFA/CA) Microsoft Entra ID (MFA/CA) Shared Access Signature (SAS)

Single Sign-On (SSO) Kerberos (KCD) KCD, Headers, SAML Kerberos, NTLM, Entra SSO Application-level Auth

Target Consumer External Public Internet External Telecommuters Roaming & Hybrid Enterprise Azure App Services / Funcs

2. Web Application Proxy (WAP) Architecture

Web Application Proxy (WAP) is a role service of the Remote Access role in Windows Server. Designed specifically to reside in perimeter demilitarized zones (DMZs), WAP acts as a reverse proxy and AD FS proxy. +-----------------------------------------------------------------------------------+

  • | WEB APPLICATION PROXY ARCHITECTURE |
  • | |
  • | [INTERNET] [PERIMETER DMZ] [INTERNAL LAN] |
  • | +-------------+ +-----------------------+ +-------------------+ |
  • | | Remote User | ==(HTTPS)==>| Web App Proxy (WAP) | ===>| Internal Web App | |
  • | +-------------+ Port 443 | - No Domain Join | KCD | - Kerberos / NTLM | |
  • | | - Reverse Proxy | +-------------------+ |
  • | | - AD FS Proxy Role | |
  • | +-----------------------+ +-------------------+ |
  • | | | AD FS Farm | |
  • | +===(Auth Token)==| (Internal DCs) | |
  • | +-------------------+ |
  • +-----------------------------------------------------------------------------------+
  • Key Operational Characteristics

DMZ Placement: The WAP server sits between an external firewall and an internal firewall. It should not be joined to the internal Active Directory domain to prevent domain credential harvesting if the DMZ server is compromised.

Inbound Firewall Requirement: External firewalls must open inbound TCP port 443 forwarding to the WAP server's public IP address.

Pre-Authentication Options:

Active Directory Federation Services (AD FS): Clients are redirected to AD FS to obtain a security token before WAP permits traffic to reach the internal web application.

Pass-Through: WAP forwards raw client requests directly to the backend application without pre-authentication (used for basic authentication or client-certificate authentication).

Kerberos Constrained Delegation (KCD): When publishing internal web applications configured for Windows Integrated Authentication (Kerberos), WAP can authenticate the user via AD FS claims and use KCD to obtain a Kerberos ticket to the backend server on the user's behalf.

3. Microsoft Entra Application Proxy Architecture

Microsoft Entra Application Proxy provides secure remote access to internal on-premises web applications without deploying a DMZ, opening inbound firewall ports, or managing external DNS records. +-----------------------------------------------------------------------------------+

  • | MICROSOFT ENTRA APPLICATION PROXY ARCHITECTURE |
  • | |
  • | [INTERNET CLIENT] [MICROSOFT ENTRA CLOUD] [INTERNAL NETWORK] |
  • | +-------------------+ +-----------------------+ +------------------+ |
  • | | Remote User | | Entra App Proxy Svc | | Private Network | |
  • | | (Browser / M365) | ====> | - Pre-Auth (MFA / CA) | <==> | Connector Agent | |
  • | +-------------------+ | - Token Validation | Out- | (Windows Server) | |
  • | +-----------------------+ bound| | | |
  • | HTTPS | (KCD / NTLM) | |
  • | 443 v v | |
  • | +------------------+ |
  • | | Internal Web App | |
  • | | (e.g., SharePoint| |
  • | +------------------+ |
  • +-----------------------------------------------------------------------------------+
  • Outbound-Only Connector Mechanics

The Connector Agent: A lightweight Windows service installed on a domain-joined Windows Server inside the internal corporate network.

No Inbound Open Ports: The Connector initiates and maintains persistent outbound HTTPS connections over TCP port 443 to the Microsoft Entra Application Proxy cloud service endpoints ( *.msappproxy.net and *.servicebus.windows.net ).

Request Flow:

The user navigates to the external URL (e.g., https://expenses.contoso.com ).

Microsoft Entra ID intercepts the request, validates the user's identity, and enforces Conditional Access policies (MFA, Compliant Device, User/Sign-in Risk).

Upon successful pre-authentication, Entra ID places the request in the cloud proxy queue.

The internal Connector picks up the request over its existing outbound control channel, retrieves the data from the internal backend web server, and streams the response back to the cloud service.

Single Sign-On (SSO) via Kerberos Constrained Delegation (KCD)

When backend web servers use Windows Integrated Authentication (Kerberos), the Private Network Connector uses Kerberos Service for User (S4U) extensions ( S4U2self and S4U2proxy ) to generate Kerberos tickets on behalf of authenticated users: # Register Service Principal Name (SPN) on the Backend Web Server account

setspn -S HTTP/internalweb.corp.contoso.com CORP\svc-web

  • # Configure Kerberos Constrained Delegation on the Connector Server in Active Directory
  • # (Using Active Directory Users and Computers -> Connector Computer Object -> Delegation tab)

# Select: \"Trust this computer for delegation to specified services only\" -> \"Use any authentication protocol\"

  • # Add target service: HTTP/internalweb.corp.contoso.com
  • 4. Choosing Between WAP and Entra Application Proxy

Both products publish internal web applications, so the exam tests the decision criteria rather than the click-path.

  • Decision driver Choose Web Application Proxy Choose Entra Application Proxy
  • Identity provider AD FS is already the token issuer Microsoft Entra ID is the token issuer

Perimeter posture A hardened DMZ already exists and inbound 443 is acceptable Security policy forbids any inbound port

Conditional Access Enforced by AD FS access-control policies Enforced natively by Entra Conditional Access (MFA, device compliance, risk)

Public DNS / certificates You must publish external DNS records and manage public certificates Microsoft provides the *.msappproxy.net endpoint and certificate by default

Non-web protocols Not supported Not supported — escalate to Entra Private Access (12.5)

Exam trap: WAP is a role service of the Remote Access role , not a standalone role, and it is the only one of the two that belongs in a DMZ. A question describing a server that is deliberately not domain-joined and sits between two firewalls is describing WAP. Conversely, any question that stresses "no inbound firewall ports" while still describing browser-based access to an internal web app is describing Entra Application Proxy.

Loading diagram... Application Publishing Security Boundaries: WAP (DMZ) vs Entra App Proxy / Private Access (Outbound)