BizTalk Server 2020 CU1

SanjivGupta 

Additional features capabilities in the Azure pipeline deployment task: Deploy BizTalk Application

1. Expose Application Stop options so that instead of StopAll you can choose to remove StopReferencedApplications and use value 31 (StopAll minus StopReferencedApplications = 31).
   We had to use PowerShell to remove app references prior to this task, and in some cases change pipelines on receive locations and send ports to a default pass-through. That ought not be required. The interim MSI produced becomes useless because these app references and proper pipelines are missing.
2.  Expose Application Start options for the final re-start allowing the selection of all ApplicationStartOption Enum
   The implemented usage of StartAll is not appropriate for all deployment situations in environments.
3. Allow disabling of the creation of the automatic file share for MSI file
4. Add support for on-premise Azure DevOps Server, not just Azure DevOps Services
5. In an effort to support automated recovery using YAML "on: failure:" when this BizTalkApplicationDeploy@2 task fails, provide a means of securely capturing and storing the original bindings with passwords and other secure values present to be available when restoring under failure. That binding would need to be available only during the YAML deployment job and then automatically be wiped away. Perhaps this can be done with a separate deployment task that is specialized to support roll back.