Deploy Azure Resource Manager templates for Azure Logic Apps

  • Article
  • iv minutes to read

After y'all create an Azure Resource Manager template for your logic app, yous can deploy your template in these ways:

  • Azure portal
  • Visual Studio
  • Azure PowerShell
  • Azure CLI
  • Azure Resources Managing director Balance API
  • Azure DevOps

Deploy through Azure portal

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

Deploy to Azure

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

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

For more information, run into these topics:

  • Overview: Automate deployment for logic apps with Azure Resource Manager templates
  • Deploy resources with Azure Resource Managing director templates and the Azure portal

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 resources group, employ the following command:

              New-AzResourceGroupDeployment -ResourceGroupName <Azure-resources-group-name> -TemplateUri https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/quickstarts/microsoft.logic/logic-app-create/azuredeploy.json

For more than information, see these topics:

  • Deploy resources with Resource Managing director templates and Azure PowerShell
  • New-AzResourceGroupDeployment

Deploy with Azure CLI

To deploy to a specific Azure resource group, utilise the post-obit command:

              az deployment group create -1000 <Azure-resources-group-proper noun> --template-uri https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/quickstarts/microsoft.logic/logic-app-create/azuredeploy.json

For more information, see these topics:

  • Deploy resources with Resource Manager templates and Azure CLI
  • az deployment grouping create

Deploy with Azure DevOps

To deploy logic app templates and manage environments, teams unremarkably utilise a tool such as Azure Pipelines in Azure DevOps. Azure Pipelines provides an Azure Resource Group Deployment task that you can add together to any build or release pipeline. For authority to deploy and generate the release pipeline, you also demand an Azure Active Directory (AD) service main. Learn more than 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:

  • Integrate Resource Manager templates with Azure Pipelines
  • Tutorial: Continuous integration of Azure Resource Manager templates with Azure Pipelines
  • Sample: Orchestrate Azure Pipelines by using Azure Logic Apps
  • Sample: Connect to Azure Storage accounts from Azure Logic Apps and deploy with Azure Pipelines in Azure DevOps
  • Sample: Connect to Azure Service Omnibus queues from Azure Logic Apps and deploy with Azure Pipelines in Azure DevOps
  • Sample: Set an Azure Functions action for Azure Logic Apps and deploy with Azure Pipelines in Azure DevOps
  • Sample: Connect to an integration business relationship from Azure Logic Apps and deploy with Azure Pipelines in Azure DevOps

Here are the general loftier-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 function of the build process.

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

    Add "Azure Resource Group Deployment" task

  4. Configure with a service main.

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

  6. Continue to build out steps in the release process for whatever other surroundings, automated exam, or approvers every bit needed.

Authorize OAuth connections

Subsequently deployment, your logic app works end-to-end with valid parameters, but to generate valid access tokens for authenticating your credentials, you still have to qualify or use preauthorized OAuth connections. Even so, you only take to deploy and cosign API connection resource once, meaning you don't take to include those connectedness resources in subsequent deployments unless you accept to update the connection information. If you employ a continuous integration and continuous deployment pipeline, you'd deploy just updated Logic Apps resources and don't accept to reauthorize the connections every time.

Hither are a few suggestions to handle authorizing connections:

  • Manually qualify OAuth connections by opening your logic app in Logic App Designer, either in the Azure portal or in Visual Studio. When yous qualify your connection, a confirmation page might appear for you lot to let access.

  • Preauthorize and share API connection resources across logic apps that are in the aforementioned region. API connections exist as Azure resources independently from logic apps. While logic apps take dependencies on API connection resources, API connection resources don't have dependencies on logic apps and remain after y'all delete the dependent logic apps. Too, logic apps can use API connections that exist in other resources groups. However, the Logic App Designer supports creating API connections only in the same resource grouping as your logic apps.

    Notation

    If you lot're because sharing API connections, brand certain that your solution can handle potential throttling problems. Throttling happens at the connection level, so reusing the aforementioned connectedness across multiple logic apps might increase the potential for throttling bug.

  • Unless your scenario involves services and systems that require multi-gene authentication, you tin utilise a PowerShell script to provide consent for each OAuth connection past running a continuous integration worker as a normal user account on a virtual machine that has active browser sessions with the authorizations and consent already provided. For case, you can repurpose the sample script provided past the LogicAppConnectionAuth project in the Logic Apps GitHub repo.

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

Next steps