The course is part of this learning path
Creating a Logic App
Creating a Custom Connector for Logic Apps
Creating a Custom Template
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.
- 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
- 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 custom template for Logic Apps. This last section of our course will look at templates. As the name implies, you can save your Logic App and use it as a starting point.
Since Azure can deploy infrastructure with code, the JSON files that generate the new objects are normally made available to you as a designer. This is one of the main goals of the Resource Manager architecture as an improvement over the older Cloud Service approach.
When you're viewing the template in Azure, you can usually choose an editor view which will highlight the configurable input parameters for deployment in a separate tab. There will also be options for the Command Line Interface, CLI, PowerShell, Microsoft .NET and Ruby definitions for deployment. Developers can choose the technique that fits their comfort zone. This also encourages the acceptance of Azure resources for first-time users of Microsoft technology without any dependence on other Microsoft tools like Visual Studio. This works well for the open-source community and developers who may not want to drift outside of their regular coding environment or programming language.
About the Author
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.