Open Server Manager and click > Remove Roles and Features . Select the target server and uncheck Remote Access .
Note: Using the aliases swpc (Set) and gwpc (Get) is also common in technical documentation. Verify the server is gone by running: powershell (Get-WebApplicationProxyConfiguration).ConnectedServersName Use code with caution. 2. Decommissioning the Server Role
Once the node is removed from the cluster's configuration, you must officially uninstall the role from the server itself to clean up local binaries and services. remove web application proxy server from cluster
In the sub-features, ensure is selected for removal. Complete the wizard and restart the server if prompted. 3. Cleaning Up AD FS Relying Party Trusts
If you are completely dismantling the WAP infrastructure rather than just removing one node, you may need to remove the proxy trust on the AD FS side. Remove-AdfsWebApplicationProxyRelyingPartyTrust . Open Server Manager and click > Remove Roles and Features
Use the following command to filter out the decommissioned server (replace 'ServerToRemove' with the FQDN of the node you are removing): powershell
Set-WebApplicationProxyConfiguration –ConnectedServersName ((Get-WebApplicationProxyConfiguration).ConnectedServersName -ne '://domain.com') Use code with caution. Verify the server is gone by running: powershell
Best practice for security if the server is permanently retired. WAP – How to remove a WAP Server from WAP clusters
This guide outlines the standard procedures to gracefully decommission a WAP node using PowerShell and Server Manager. 1. Removing the WAP Node via PowerShell
Ensure external/internal records no longer point to the removed IP. Certificate Authority