Logic App Consumption

template to deploy comsumption based workflows

Logic App Consumption is Microsoft's low code offering for implementing enterprise integrations. It offers Connectors which can save you time from building everything yourself.

This templates includes a Logic App Consumption deployment and some popular connections.

Application architecture

This template utilizes the following Azure resources:

• Azure Logic App Consumption to design the workflows
• Azure Monitor for monitoring and logging
• Azure Key Vault for securing secrets

How to get started

1. Install Visual Studio Code with Azure Logic Apps (Standard) and Azure Functions extensions
2. Create a new folder and switch to it in the Terminal tab
3. Run azd auth login
4. Run azd init -t https://github.com/marnixcox/logicapp-consumption

Now the magic happens. The template contents will be downloaded into your project folder. This will be the next starting point for building your integrations.

Contents

The following folder structure is created.

├── infra                      [ Infrastructure As Code files ]
│   ├── keyvault               [ Key Vault files ]
│   ├── logicapp               [ Logic app files ]
│   ├── main.bicep             [ Main infrastructure file ]
│   └── main.parameters.json   [ Parameters file ]
├── src                        [ Application code ]
│   └── workflows              [ Azure Logic App Consumption ]
│       └── SalesOrder         [ Example Logic App ]
└── azure.yaml                 [ Describes the app and type of Azure resources ]

Key Infrastructure Files

<<<<<<< HEAD

• keyvault/keyvault.bicep - Key Vault
• logicapp/consumption.bicep - Logic App Consumption
• main.bicep - Main orchestration
• monitoring.bicep - Observability stack =======
• main.bicep - Main orchestration
• monitoring.bicep - Observability stack
• logicapp.bicep - Logic App Consumption
• keyvault.bicep - Key Vault

355390027c682bf8d853fd046992daa1c07fd6d7

Provision Infrastructure and Logic App Consumption

Let's first provision the infra components. Add a resourceToken parameter to the main.parameters.json to set the application name or leave it out to have a random name generated.

 "resourceToken": {
      "value": "appname"
    }

• Run azd provision

Environment

First time an environment name, subscription and location need to be selected. These will then be stored in the .azure folder.

Allowed values for environment are dev tst acc prd

Resource group and all components will be created. Also Logic App Consumption are being deployed/provisioned using infra code.

Connections

The following connections are currently implemented:

servicebus office365 sharepointonline azureblob common data service

Deployment pipelines

This template includes pipelines for a staged dev/tst/acc/prd deployment for a develop and main branch. Make sure to update the serviceConnection and AZURE_SUBSCRIPTION_ID accordingly.