Deploy Azure Resource Manager templates for Azure Logic Apps

After you create an Azure Resource Manager template for your logic app, you can deploy your template in these ways:

Deploy through Azure portal

To automatically deploy a logic app template to Azure, you can choose the following Deploy to Azure button, which signs you in to the Azure portal and prompts you for information about your logic app. You can then make any necessary changes to the logic app template or parameters.

Deploy to Azure

For example, you're prompted for the following information after you sign in to the Azure portal:

  • Azure subscription name
  • Resource group that you want to use
  • Logic app location
  • The name for your logic app
  • A test URI
  • Acceptance of the specified terms and conditions

For more information, see these topics:

Deploy with Visual Studio

To deploy a logic app template from an Azure Resource Group project that you created by using Visual Studio, follow these steps to manually deploy your logic app to Azure.

Deploy with Azure PowerShell

To deploy to a specific Azure resource group, use the following command:

New-AzResourceGroupDeployment -ResourceGroupName <Azure-resource-group-name> -TemplateUri

For more information, see these topics:

Deploy with Azure CLI

To deploy to a specific Azure resource group, use the following command:

az group deployment create -g <Azure-resource-group-name> --template-uri

For more information, see these topics:

Deploy with Azure DevOps

To deploy logic app templates and manage environments, teams commonly use a tool such as Azure Pipelines in Azure DevOps. Azure Pipelines provides an Azure Resource Group Deployment task that you can add to any build or release pipeline. For authorization to deploy and generate the release pipeline, you also need an Azure Active Directory (AD) service principal. Learn more about using service principals with Azure Pipelines.

For more information about continuous integration and continuous deployment (CI/CD) for Azure Resource Manager templates with Azure Pipelines, see these topics and samples:

Here are the general high-level steps for using Azure Pipelines:

  1. In Azure Pipelines, create an empty pipeline.

  2. Choose the resources you need for the pipeline, such as your logic app template and template parameters files, which you generate manually or as part of the build process.

  3. For your agent job, find and add the Azure Resource Group Deployment task.

    Add "Azure Resource Group Deployment" task

  4. Configure with a service principal.

  5. Add references to your logic app template and template parameters files.

  6. Continue to build out steps in the release process for any other environment, automated test, or approvers as needed.

Authorize OAuth connections

After deployment, your logic app works end-to-end with valid parameters. However, you must still authorize any OAuth connections to generate valid access tokens for authenticating your credentials. Here are ways that you can authorize OAuth connections:

  • For automated deployments, you can use a script that provides consent for each OAuth connection. Here's an example script in GitHub in the LogicAppConnectionAuth project.

  • To manually authorize OAuth connections, open your logic app in Logic App Designer, either in the Azure portal or in Visual Studio. In the designer, authorize any required connections.

If you use an Azure Active Directory (Azure AD) service principal instead to authorize connections, learn how to specify service principal parameters in your logic app template.

Next steps