(EXCHG.80).aspx – Where only Site Affinity is can be configured. Microsoft documented Deployment Considerations for the Autodiscover Service in: This basically “force” the automatic propagation of settings into the profile, including the checkbox for “Connect to Microsoft Exchange using HTTP” and filling the information for the HTTP proxy and authentication methods.

Then the autodiscover application picks up the change and publish it, along with the url’s for OAB,EWS & Availability. Once “Outlook Anywhere” is configured on a client access server an EXPR entry is created.

This is an unsupported method, use at your own risk! See Exchange 2013 Outlook Anywhere Considerations for more.

If you’re going to deploy Exchange 2013 anytime soon – work your way to adapt autodiscover, and bring back the EXPR value.

If you want only specific users to be able to use Outlook Anywhere while others don’t I would advice considering the Set-CasMailbox -MAPIBlockOutlookRpcHttp:$true cmdlet to allow/block specific users. With that being said, a few commentators stated that they would like to continue using Outlook Anywhere and with Autodiscover enabled and the EXPR removed this will result in constant “removal” of the Outlook Anywhere settings that were statically configured. Removing the EXPR while Autodiscover is being utilized (which is probably the case in most deployments) will achieve preventing Outlook Anywhere from being used.

Exchange 2007 outlook 2019