Deploying Web Application Proxy (WAP) in a cluster ensures high availability and load balancing for your externally published applications. However, lifecycle management tasks—such as decommissioning old hardware, scaling down infrastructure, or performing a clean OS reinstall—require you to safely remove a WAP server from the cluster.
On a healthy remaining node, force a configuration refresh by restarting the Web Application Proxy service using the command: Restart-Service WAPCS . remove web application proxy server from cluster
Regardless of the reason, improperly removing a WAP server can lead to authentication failures, orphaned endpoints, and security blind spots. This guide walks you through a meticulous, step-by-step removal process. Deploying Web Application Proxy (WAP) in a cluster
If you skip Step 2, the ADFS server will still attempt to send "relying party trust" updates to the removed proxy, causing event ID 364 and proxy sync timeouts in the event log. Regardless of the reason, improperly removing a WAP
Remove the server's IP address from any external or internal load balancers (e.g., Azure Traffic Manager or F5).