#LogicApps – Let’s create our first Logic App in #Azure

Hello!

In today’s post I will continue to explain some of the cool Logic Apps features. The first thing to keep in mind is that a Logic App is specific type of Azure App Service. To this day, supported types are

• Web App
• Web App for Containers
• Functions App
• API App
• Logic App

As with Microsoft Flow, we have the chance to use a visual designer to create our processes. In this case, and to keep the post simple, I will use the template that is created by default: Ping Site

Important: In the free and trial mode of Logic Apps, they are created with a 60-minute lifespan. Which gives us more than enough time to understand how they work.

Once we have created our Logic App, we can work with it from the Azure portal. As with Microsoft Flow we have the ability to use a visual designer to create and define the execution process of the Logic App. As we can see in the following image, the example process starts with a trigger that every 1 hour will execute a Ping to a specific url

One of the advantages of working with Logic Apps is that we can work also with the “source code” of the Logic App. Here we do not expect to see lines and lines of C # or JavaScript, but rather we can see a JSON definition with the process that defines the Logic App

Obviously this is the time to get dirty and update some of the coding behind the Logic App. And as it could not be otherwise, we have a SAVE button to save our changes

I have not yet talked about how to integrate our changes with a Git repository or with TFS. However, as an Out of the Box feature, every time we record a change in our process, a version of it is generated in Azure.

When we open a specific version version history, we will have the ability to promote it as a “current version” in case we decide to use that version. At all times, we can see the process in Designer mode or Code View mode.

And of course, if you are a “break it all” like me, chances are that in some change you have gotten a Big Bug. In the Logic App overview it is possible to analyze the log execution history, and how the triggers have been launched

Finally, we can review the step-by-step execution of a process. Analyze what action has failed and even relaunch the process with the information specific to that version.

As part of the explanation of differences with MS Flow, I think these steps imply that Logic App plays in a higher category. In the next posts, I will continue to explain the characteristics of Logic Apps.

Happy Coding!

Greetings @ Toronto

El Bruno

References

My posts on Logic Apps

• Logic Apps, Introduction and main differences with Microsoft Flow

My posts on Flow

• Check your Apps health in Azure using Application Insights and Microsoft Flow
  How To iterate through collections of elements (Excel, Sharepoint, Cognitive Services and more…)Trigger a Flow associated to an item in a #SharePoint list
• New input options when using Flow Button: list of choices
• Working with Expressions
• Export and Import Flow definitions with advanced options
• How To emulate a Button for a Flow using a Browser
• Advanced options to work with an HTTP Action in Microsoft Flow, Headers, Authentication and more
• Working with Variables in Microsoft Flow
• Handle exceptions, errors, timeouts and more in a Microsoft Flow definition
• Buttons Widgets in iOS and Android
• New action definition to use Computer Vision APIs from Microsoft Cognitive Services
• Schedule a Flow execution, recurrence supported!
• “Save as ” and interaction with physical buttons FLIC and BTTN
• Email Sentiment Analysis on a PowerBI dashboard, and Flow
• Support for Team coauthoring and sharing
• Calling a Flow from a C# ConsoleApp
• Push Notification Support
• How to review a Flow process
• How to invoke a Flow from an external app using HTTP Request