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.
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
- Install Visual Studio Code with Azure Logic Apps (Standard) and Azure Functions extensions
- Create a new folder and switch to it in the Terminal tab
- Run
azd auth login
- 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.
The following folder structure is created.
├── infra [ Infrastructure As Code files ]
│ ├── main.bicep [ Main infrastructure file ]
│ ├── main.parameters.json [ Parameters file ]
│ ├── app [ Infra files specifically added for this template ]
│ └── core [ Full set of infra files provided by Azure Developer CLI team ]
├── src [ Application code ]
│ └── workflows [ Azure Logic App Consumption ]
└── azure.yaml [ Describes the app and type of Azure resources ]
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
First time an environment name, subscription and location need to be selected. These will then be stored in the .azure
folder.
Resource group and all components will be created. Also Logic App Consumption are being deployed/provisioned using infra code.
The following connections are currently implemented:
servicebus
office365
sharepointonline
azureblob
common data service
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.