Demo - Creating a Logic App


Course Introduction
3m 51s
1m 3s

The course is part of this learning path

Start course

The Microsoft Azure cloud offers many options for developers who want to build websites and services on Web Apps. Normally, the coding is done using proprietary Microsoft languages like C#, Visual Basic, and others. More recently Microsoft has made it easier for open source developers to use the IDE and language of their choice with support for PHP, Java, Node.js, and Go for server-side code. However, some web solutions may not require a complex programming language to meet the requirements, and that’s where Logic Apps comes in.

This course looks at some of the features and benefits of Logic Apps and examines the kinds of business processes that you can easily model. We will look at the wider topic of workflow and automation problems and then show you how to transform these into Logic App solutions. We will also look at the internal components that make up a Logic App, including triggers, conditions, actions, and standard connectors.

For connecting to third-party SaaS services, or even your own homegrown APIs, you will learn how to create a custom connector. You will also learn about rapid deployment using Azure templates.

Learning Objectives

  • Implement simple automation and workflow using Logic Apps
  • Model business processes as a series of conditions and actions
  • Monitor Azure Apps, Office 365, or third-party services using triggers
  • Connect to Azure services and other well-known third-party websites

Intended Audience

  • People who want to become Azure developers
  • Non-developers who want to build point-and-click solutions
  • Solution architects


  • General exposure to basic cloud technology
  • Familiarity with the Azure Portal

Creating a logic app. First, let's create a logic app placeholder by selecting the create a resource button and searching for logic apps. Notice that logic apps custom connector also shows up in the search. 

Next, let's create a new logic app by clicking add. 

For the purposes of this demo, I've gone ahead and created a resource group to hold the logic apps. This is usually the first step in creating any object in Azure, either with the portal or through code. 

This will take a few seconds to deploy. Now you can look at the newly-created logic app by clicking go to resource. 

There are quite a few templates that you can use as a starting point. Each one has a few steps with conditions and actions. Some common triggers are also listed. 

We will select this one entitled send an email when item in a SharePoint list is modified. 

For demo purposes, I have already created a SharePoint list called test list, which contains tasks. The condition is called when a new item is created. 

Notice that I can graphically create new steps as needed. Here's the address of the SharePoint list. We also have the interval and frequency for checking the list. 

The get my profile step is already configured from information in Azure AD. 

Now for the send an email action. I will need to identify a user who will be the recipient of the email. That's done by clicking here and selecting a user from Office 365. 

When I click on code a view, you can see the JSON template definition file for the logic app. This is important for deployment and reuse. So we will return to it later. 

For now, let's go ahead and run the logic app. 

Now we will go over to SharePoint online and create a few tasks in the list. 

If you go back over to Azure, you can see the history of the logic app, the number of times it checked for the condition and the actions that were taken. 

Finally, let's go over to Outlook online. Here you will find a few emails that were sent by the logic app as a result of the test tasks that were created.

About the Author
Derrick So'Brien

Derrick is a content contributor and trainer for Microsoft cloud technologies like Azure, Office 365 and Dynamics 365. He works across North America and Europe to help companies and organizations with these technology shifts. Before that he has worn many hats but prefers to wear them one at a time.

When he is not night walking during his travels, you can find him on a bicycle path or performing guitar solos to an imaginary audience in his basement.