Requirements for WAP

Unfortunately, the ability to make use of the Web Application Proxy comes with a pretty stingy requirement. You must have AD FS installed in your environment to be able to use it. Even to test it, because the WAP configuration is stored inside AD FS. None of the WAP configuration information is stored on the remote access server itself, which makes for a lightweight server that can be easily moved, changed, or added to. The downside to this is that you must have AD FS running in your environment so that WAP can have a place to store that configuration information.

While a tight integration with AD FS does mean that we have better authentication options, and the users can take advantage of that AD FS single-sign-on to their applications that are published through WAP, so far this has proven to be a huge roadblock to implementation for any smaller size business. Many folks are not yet running AD FS, and if the only reason they are looking into implementing AD FS is so that...