Having problems getting Exchange to support internal free/busy and inter-org mailbox migrations at the same time.  It looks like the Exchange 2013 powershell command (Set-ExchangeServer -Identity yourservername -InternetWebProxy) doesn't allow for a proxy bypass so that we can ensure all our local traffic stays local.   I've found many articles that indicate that this issue can be overcome in Exchange 2010 by modifying the proxy config associated with WinHTTP.... Unfortunately I'm unable to find any reference to Exchange 2013 using WinHTTP.   Can you provide insight into how a proxy bypass can be specified in Exchange 2013?

Here's the article that covers Exchange 2010.  Unfortunately no reference to Exchange 2013 in this article.   I'm hoping for some document from Microsoft that details proxy bypass for Exchange 2013 because I need to share this information with my client.

Configuring Proxy Settings for WinHTTP

Thank you in advance!

All commands in the link you provided are of Windows instead of Exchange. I.e. there is no difference between Exchange 2010 and 2013 if you're using the mentioned approach.

All commands in the link you provided are of Windows instead of Exchange. I.e. there is no difference between Exchange 2010 and 2013 if you're using the mentioned approach.

• Proposed as answer by Lynn-LiMicrosoft contingent staff, Moderator 22 hours 28 minutes ago

All commands in the link you provided are of Windows instead of Exchange. I.e. there is no difference between Exchange 2010 and 2013 if you're using the mentioned approach.

• Proposed as answer by Lynn-LiMicrosoft contingent staff, Moderator Thursday, May 14, 2015 9:00 AM
• Marked as answer by Lynn-LiMicrosoft contingent staff, Moderator Tuesday, May 26, 2015 1:54 AM

There is always the chance that Exchange 2013 moved away from WinHTTP to some other HTTP API for some reason, which is why i'm looking for Microsoft documentation confirming the use of WinHTTP. Are you aware of any such documents on Technet or elsewhere? I also find it extremely odd that there are no posts that i've been able to find where other admins use the netsh commands on a system that runs Ex2013. Looking for docs... Regards

It's quite common that certain behavior is documented for older version but not for new. You can safely assume there is no change in such scenario, i.e. the old docs applies to new version.

I am seeing similar behavior with Exchange 2010 while I am trying to retrieve free/busy locally. I have a CAS server that has proxy configured using InternetWebProxy and WinHTTP.  Using network monitor tool I can see that Exchange does not respect proxy exceptions list that were configured using netsh and sends ALL traffic to proxy configured by InternetWebProxy parameter.

I am just wondering if there is a way of configuring proxy exception list using InternetWebProxy parameter?

Regards,