Conditions and Actions


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

Conditions and actions. Workflow can be thought of as a series of conditions that we're looking for in our connected systems and the appropriate action that we want to take when we see those conditions. In some cases, your Logic App will require only a few steps to perform the job. However, the workflow framework can handle many steps in a chain and take different paths along with conditional branching according to your business logic. 

In our example, the condition we were looking for was the creation of a new part order request. Perhaps in an Enterprise Resource Planning, ERP, like Dynamics AX, SAP, or J.D. Edwards. The action that is taken is to create a new approval time, perhaps via an electronic form or a temporary data store. This would be followed by another condition which checks for the approval amount and then creates the actual approval request. Perhaps via an email or an electronic form. To ensure the approval that was turned around in a timely manner, we could configure a triggered schedule or a timeout for a response to the request. Another action after the timeout could be to route to another approver or to notify the person who placed the original request via an email integration or other notification like a SharePoint site, collaboration tool, task manager or project tool. 

No single off-the-shelf software application could easily handle all those processing elements and connections but a Logic App would be a good fit to this kind of requirement. 

Actions can involve built-in Azure features like Azure Functions, app service actions, control variables, database operations, conversions and transformations and XML responses to name a few.

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.