Generally, it is not recommended to store passwords in the binding file and by default BizTalk administration UI clears it out when exporting binding to the xml file. But in development environment where you have automatedcontinuous integration build and deploymentnot having password in the binding file will prevent application from starting and CI process fail. It can become tedious in staging deployments (TEST, UAT) as well, especially if you have multipleendpoints that use accounts with passwords. In such cases, having password for development account (hopefully not the same as production)in binding file can make life easier.

To do that, export binding file after application is fully configured. Open it and locate section(s) with configuration for the ports/locations of interest. For example for the WCF receive location it will be in:


Find emtpy password tag in this section that will look like:

&lt;Password vt=”1″/&gt;

Change it to enclose you password value and vt attribute value to “8”:

&lt;Password vt=”8″&gt;MyPassword&lt;/Password&gt;

Save and use this binding for an automated deployment script.