Feature: Use Azure Key Vault or App Configuration instead of SettingsFileGenerator.xml

[miai-dgsbs]

Cause: SettingsFileGenerator.xml is extremely hard for merging changes.

[eloekset]

Secrets should never be in SCC, so SettingsFileGenerator.xml causes bad habits for users of BTDF. Actually we're looking at Azure Key Vault for out BizTalk projects deployed on-premises. It's very interesting to see that others are thinking about the same thing. We should share thoughts about how to implement support for this.

I did something similar for Octopus PS scripts in this PR: eloekset/publish-btdfBiztalkApplication#7 This is also merged into the develop branch of the main repo at: https://github.com/elangovana/publish-btdfBiztalkApplication/tree/develop Unfortunately we didn't continue the move to Octopus at work, so I haven't created a new release of the scripts. I documented my work in the wiki at my own fork of the repo, but haven't copied this over to the main repo yet: https://github.com/eloekset/publish-btdfBiztalkApplication/wiki/Octopus-Deploy

[eloekset]

I just saw this presentation about Azure App Configuration, which can reference Key Vault for secrets and has a great API to manage all kinds of configuration for various environments. The free tier should be sufficient for each BizTalk applicaiton when used only from BTDF during deployment. This issue should be renamed to say Azure App Configuration instead of Azure Key Vault.

[akishaha]

Looking forward for this feature as this will make things more neater and secure.