FIX: Predefined WCF Bindings not taking in account a default Web proxy configuration in BizTalk Server

Applies to: BizTalk Server 2020 BranchBizTalk Server 2020 DeveloperBizTalk Server 2020 Enterprise

Symptoms


When predefined WCF bindings are used like basicHttpBinding, webHttpbinding or WSHttpBinding, then the default proxy configuration in IE settings or in <defaultProxy> of a Microsoft BizTalk Server config file are ignored and not used.

Resolution


This problem is fixed in the following cumulative update for BizTalk Server:

More Information


Default proxy will be usedwhen send port is "Use proxy" and proxy address is not provided in sendport transport properties. If "Use send handler proxy settings" is selected, send port uses the proxy settings same as the send handler hosting this port.
System proxy credential canbe provided from windows credential manager by creating a new genericcredential. In case of no generic credential for corresponding proxy server, windows credential of context user will be used for authentication.

References


For information about the service packs and cumulative update list for BizTalk Server, see the following article in the Microsoft Knowledge Base:

2555976 Service pack and cumulative update list for BizTalk Server

For more information about BizTalk Server hotfixes, see the following article in the Microsoft Knowledge Base:

2003097 Information about BizTalk hotfixes and Cumulative Update support