Clean Install from Azure DevOps

When you perform an incremental ARM template release via Azure DevOps, you run into the risk that manual adjustments to logic apps or other artifacts like servicebus subscriptions are overlooked. For that reason it’s a good idea to always start from a clean canvas by deleting all resource groups in your solution.

Using private NuGet Feed

If you want to use custom assemblies as NuGet packages in Visual Studio and your DevOps pipelines, you will have to add your assembly to the Assemblies folder in DevOps first. Next go to the NuGet Package Manager settings in Visual Studio.

Web App Configuration

You can store the application setting for an Azure Web App at two places: in the web.config and in the Azure Portal (under Configuration). In the DevOps release pipeline / Deploy Azure App Service task, you can specify the AppSettings under Application and Configuration Settings. You can change AppSettings and Connection Strings in the web.config by enabling XML variable substitution.

Parameterizing Azure Artifacts

The traditional approach to parameterize logic apps and/or API Management services is to use parameter files. As an alternative to parameter files, you can use variable groups in your DevOps release definition. Variable groups can be maintained by operators who have access to your DevOps team project.

Release pipeline subscription

When you add a Resource Deployment step in a release pipeline, you will have to select an Azure Resource Manager service connection (or service principal) instead of the subscription itself. Add the Azure Resource Manager service connection via the DevOps Team project settings. Don’t forget to add your account to DevOps Release Administrators and Project Administrators.