Logic Apps for visual workflows in Azure - Commands & Configuration

Introduction

Logic Apps help you automate tasks by connecting different apps and services visually. They solve the problem of manually doing repetitive work by creating workflows that run automatically.

When you want to send an email automatically when a file is uploaded to cloud storage.

When you need to copy data from one system to another without writing code.

When you want to monitor social media for specific keywords and get alerts.

When you want to automate approval processes with multiple people involved.

When you want to integrate different cloud services to work together smoothly.

Config File - logicapp.json

logicapp.json

{
  "$schema": "https://schema.management.azure.com/schemas/2016-06-01/workflowdefinition.json#",
  "contentVersion": "1.0.0.0",
  "parameters": {},
  "triggers": {
    "manual": {
      "type": "Request",
      "kind": "Http",
      "inputs": {
        "schema": {}
      }
    }
  },
  "actions": {
    "Send_an_email": {
      "type": "ApiConnection",
      "inputs": {
        "host": {
          "connectionName": "office365",
          "operationId": "SendEmail",
          "apiId": "/subscriptions/00000000-0000-0000-0000-000000000000/providers/Microsoft.Web/locations/westus/managedApis/office365"
        },
        "parameters": {
          "to": "[e-mail]",
          "subject": "Hello from Logic Apps",
          "body": "This is an automated email sent by Logic Apps."
        }
      },
      "runAfter": {}
    }
  },
  "outputs": {}
}

This JSON defines a Logic App workflow.

triggers: Starts the workflow manually via HTTP request.

actions: Sends an email using Office 365 connector.

This file can be deployed to Azure to create the Logic App.

Commands

Log in to your Azure account to manage resources.

Terminal

az login

Expected Output

To sign in, use a web browser to open the page https://microsoft.com/devicelogin and enter the code ABCD1234 to authenticate.



You have logged in. Now let us find all the subscriptions to which you have access...

Create a resource group to hold your Logic App and related resources.

Terminal

az group create --name example-resource-group --location eastus

Expected Output

{

  "id": "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/example-resource-group",

  "location": "eastus",

  "managedBy": null,

  "name": "example-resource-group",

  "properties": {

    "provisioningState": "Succeeded"

  },

  "tags": {},

  "type": "Microsoft.Resources/resourceGroups"

}

→

--name - Specifies the name of the resource group.

→

--location - Specifies the Azure region for the resource group.

Create the Logic App in the resource group using the workflow definition file.

Terminal

az logic workflow create --resource-group example-resource-group --name example-logicapp --definition logicapp.json

Expected Output

{

  "id": "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/example-resource-group/providers/Microsoft.Logic/workflows/example-logicapp",

  "name": "example-logicapp",

  "type": "Microsoft.Logic/workflows",

  "location": "eastus",

  "properties": {

    "state": "Enabled"

  }

}

→

--resource-group - Specifies the resource group where the Logic App is created.

→

--name - Sets the name of the Logic App.

→

--definition - Points to the JSON file defining the workflow.

Check the details and status of the created Logic App.

Terminal

az logic workflow show --resource-group example-resource-group --name example-logicapp

Expected Output

{

  "id": "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/example-resource-group/providers/Microsoft.Logic/workflows/example-logicapp",

  "name": "example-logicapp",

  "type": "Microsoft.Logic/workflows",

  "location": "eastus",

  "properties": {

    "state": "Enabled",

    "provisioningState": "Succeeded"

  }

}

→

--resource-group - Specifies the resource group of the Logic App.

→

--name - Specifies the Logic App name to show.

Key Concept

If you remember nothing else from this pattern, remember: Logic Apps let you build automated workflows visually without writing code by connecting triggers and actions.

Common Mistakes

Trying to deploy the Logic App without logging into Azure first.

The Azure CLI commands require authentication to work and will fail if not logged in.

Always run 'az login' and complete authentication before managing Azure resources.

Using an invalid or incomplete JSON definition file for the Logic App.

Azure will reject the deployment if the workflow definition is not valid JSON or missing required fields.

Validate your JSON file and use the official schema to ensure it is complete and correct.

Not specifying the resource group or Logic App name correctly in commands.

Commands will fail or target the wrong resources if these parameters are missing or incorrect.

Double-check resource group and Logic App names before running commands.

Summary

Log in to Azure using 'az login' to authenticate your session.

Create a resource group to organize your Logic App and resources.

Deploy the Logic App using a JSON workflow definition file.

Verify the Logic App deployment and status with 'az logic workflow show'.