Cluster: Remove Web Application Proxy Server From

Removing a Web Application Proxy (WAP) server from a cluster involves both decommissioning the role on the specific server and ensuring the remaining cluster "forgets" the removed node. If a server is simply shut down or the role is uninstalled without updating the cluster configuration, it may still appear as a "ghost" entry in management consoles. 1. Remove the Server from the Cluster List

On the AD FS server:

# Ensure no remnants
Get-AdfsWebApplicationProxyRelyingPartyTrust | Format-Table Name, Enabled, LastHeartBeat
To remove a Web Application Proxy (WAP) server from a cluster, you can use PowerShell to update the ConnectedServersName remove web application proxy server from cluster

Is it the primary configuration master? (Some WAP clusters have a primary node that syncs config to secondary nodes).
What is its current connection count? Use netstat or ss to see active tunnels.
What applications does it publish? Is it the only node publishing a legacy app?

Once the cluster no longer expects the server, you can safely remove the role from the target server itself. Via PowerShell: powershell Removing a Web Application Proxy (WAP) server from
Take note of:
He checked the logs. Seamless handoffs. Zero authentication failures. Is it the primary configuration master
, and remove any published web applications associated with that server. Uninstall the WAP Role
✅ Update your disaster recovery plan – change the recovery order to exclude the removed server.