Remove Web Application Proxy Server From Cluster [updated] [Reliable × Manual]

WAP doesn't have a native "drain" command like a load balancer. Instead, remove it from the outer load balancer pool first, then wait for 5-10 minutes for existing Kerberos tokens and WAP cookies to expire.

: Use the following PowerShell command to remove the WAP feature and its associated management tools: powershell

Run the following command to remove the Remote Access and Web Application Proxy features, followed by a deployment-safe restart: powershell remove web application proxy server from cluster

Note: You will be prompted to confirm the removal. Type 'Y' to proceed.

If the removed server still appears in stale diagnostic logs or cluster lists, restart the Active Directory Federation Services traffic on the ADFS nodes to force a synchronization refresh. Update DNS Records WAP doesn't have a native "drain" command like

Simply uninstalling the role does not always cleanly remove the proxy trust object from the internal AD FS database. It is best practice to revoke the trust explicitly via PowerShell.

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. Type 'Y' to proceed

On [Date] at [Time], the Web Application Proxy server [Server Name] was successfully removed from the production cluster.

PowerShell is often the most reliable method, especially if the GUI is unresponsive or if you are automating your infrastructure management.