
The WAP servers can be either joined to an DMZ Active Directory for management purposes, or left as standalone computers in a WORKGROUP. It is recommended to place all WAP server(s) in a DMZ network, which is separated from the internal, corporate network by an internal firewall.If 2 adapters are used, the first adapter must be connected to the internal network, and the second adapter must be connected to the external network Internet or public DMZ network. At least 1 network adapter installed in the server, connected to the internal network either directly, or through a firewall or NAT device.
#Publish new application wizard windows
Server running Windows Server 2012 R2 Essentials, Standard, or Datacenter.Also WAP can be part of a DirectAccess infrastructure deployment, or when securely publishing Exchange or SharePoint services. Using WAP, you can configure additional features provided by AD FS, including: Workplace Join, multifactor authentication (MFA), and multifactor access control. In general, WAP provides reverse proxy functionality for web applications in the corporate network which allows users on most devices to access internal web applications from external networks. One of the primary roles of the WAP is to performs pre-authenticates access to web applications using Active Directory Federation Services (AD FS), and in this capacity the WAP functions as an AD FS proxy.

The Web Application Proxy (WAP) is a role service of the Remote Access server role in Windows Server 2012 R2.
