Remove | Web Application Proxy Server From Cluster

Identify the exact name of the server you wish to remove. powershell (Get-WebApplicationProxyConfiguration).ConnectedServersName Use code with caution. Copied to clipboard

Step 1: assess impact. Priya checked active sessions and recent authentications. Only a small percentage of traffic had routed to node 03 in the last 10 minutes. No ongoing sign-ins were mid-flight. Good—she could safely drain it.

Wait until established connections drop to zero (or near zero for long-lived persistent sessions — set a max wait of 30 minutes).

Get-WebApplicationProxyEndpoint

Ensure the remaining nodes in the cluster have sufficient capacity to handle the load of the removed server.

This returns the fully qualified domain names (FQDNs) of all servers currently recognized as part of the WAP cluster. 2. Logical Removal from the Cluster

What (e.g., Windows Server 2019, 2022) are your WAP nodes running? remove web application proxy server from cluster

Ensure the remaining WAP servers are properly communicating and that their configuration is consistent.

Option 1: Using PowerShell (Quickest for Configuration Cleanup)

Log directly into the WAP server you want to remove. Right-click the PowerShell icon and select . Step 2: Run the Deployment Removal Command Identify the exact name of the server you wish to remove

Do not disconnect a server while it is actively handling user requests. You must gracefully stop new connections from reaching the node. Log into your external network load balancer.

In modern enterprise architecture, Web Application Proxy (WAP) servers are critical components for providing secure, reverse-proxy access to internal applications. Often deployed in clusters for high availability, there comes a time when a server needs to be removed—whether for decommissioning, hardware upgrades, or maintenance.