As mentioned earlier, the reverse proxy is required to make the web services of our Front End Server available to external users. The role of the reverse proxy is to publish resources to an external network, while creating a transparent and secure layer between the Internet user and our website and services. The connection will point to the records on the public DNS and so we will need rules to rewrite calls and direct them correctly to the internal servers.

Mobile clients make a heavy use of the web services of Lync, especially the Lync 2010 version that is basically an IM client (with push capabilities on some mobile devices).

The first decision we need to take here is about what kind of technology we are going to use for our reverse proxy.

A less costly solution could be the use of a reverse proxy on a Linux deployment or Internet Information Services (IIS) as in this post, Using IIS ARR as a Reverse Proxy for Lync Server 2013 at http://blogs.technet.com/b/nexthop/archive/2013/02/19/using-iis-arr-as-a-reverse-proxy-for-lync-server-2013.aspx. If we need a more complete and secure solution, there is a really long list of vendors and products. You can refer to the TechNet page dedicated to certified load balancers for Lync at http://technet.microsoft.com/en-us/lync/gg131938.aspx.