New Post: special characters in SettingsFileGenerator.xml

If the PowerShell script is modifying SettingsFileGenerator.xml and causing the XML to become invalid, then I'd say the right path of action is to fix the PowerShell script. It should be XML-escaping at least <, > and & when present inside any password.

If the Excel XML file contains

Strong&Password

then yes, the exporter will convert it back to Strong&Password.

If you're in Visual Studio, you can run Tools\Deployment Framework for BizTalk\Export Environment Settings with the solution open.

Thanks,
Tom