Ops / IT Pro
The course is part of these learning paths
Getting Started With Azure App Service
There's a lot of effort that goes into keeping our applications available, and secure. That's why so many cloud vendors offer platforms for hosting web based applications. If you're building web apps, APIs, mobile backends, or business processes then you should consider looking into App Service! App Service has a lot of functionality. It meets compliance standards from around the world, it's highly scalable, it supports multiple langauges and makes it easy to get your code deployed.
This Getting Started with Azure App Service course it's basically an intro, but for developers and IT Pros. In this course you'll learn about the features of App Service at a high level as well as for each component. Then you'll learn about each of the 4 components of App Service through some demos. If you're a developer or IT Pro working with Azure, but new to App Service, this course is for you.
This course will help get you up-to-speed on App Service so that you can start developing / managing apps.
Getting Started With Azure App Service: What You'll Learn
|Lecture||What you'll learn|
|Course Intro||What to expect from this course|
|App Service Overview||A high-level overview of App Service|
|Web, Mobile, API App Overview||A high-level overview of Web, Mobile, API Apps|
|Logic App Overview||A high-level overview of Logic Apps|
|Mobile Apps: Easy Tables||How to use Easy Tables as a "no-code" option|
|Mobile Apps: Client||Running the client code from an iOS simulator|
|Mobile Apps: .NET Backend||Using a .NET backend|
|Mobile Apps: Auth||Using authentication with App Service|
|API Apps||Creating API Apps|
|Logic Apps||Automating business processes|
|Web Apps||Authentication and remote debugging|
|Deployments||Deployment slots and GitHub based deployments|
|Monitoring and Logging||Monitoring and logging options|
|Scaling||Scaling up and out|
|Next Steps||What's next|
Welcome back! In this lesson we’ll take a high level look at Logic Apps, which are a really user friendly way to create business processes.
When it comes to Web, Mobile and API apps, their purpose is pretty self descriptive. However with Logic apps, it’s not as obvious. So, what exactly do logic apps do?
Logic apps allow you to visually create workflows. As an example, imagine that every time a file is added to an FTP server you could have it copied to OneDrive and then notify you on Slack that it’s done. Why would you want that, I don’t know, maybe you wouldn’t. But you could! The point is that with an easy to use graphic interface you can create workflows that chain together individual tasks. It’s not just tasks, you also can use conditional logic and loops, allowing for a sort of visual programming model.
Let’s check out a Logic app in the portal. Here I have a logic app already created, however I haven’t created an actual workflow.
You can see from this overview page that there are a list of default starting triggers, which include things such as, an HTTP request, a Tweet, an new file on OneDrive, or an FTP server, and more. Logic Apps all start with a trigger to kick off the workflow. Azure’s documentation lists off the different types of triggers, and you see there are few different types.
The first is a Request type
This allows the logic app to become an endpoint for you to call.
Recurrence is just a scheduled task.
HTTP is a pretty powerful option since it allows you to poll an HTTP endpoint.
ApiConnections are like the HTTP trigger however they are based on Microsoft-managed APIs
HTTPWebhooks allow you to subscribe and unsubscribe to events
ApiConnectionWebhooks are similar to the HTTPWebhook trigger except based on Microsoft-managed APIs
In addition to these common triggers, there’s also a list of common templates. These include things such as posting to Slack if a new tweet matches a hash tag. This isn’t an exhaustive list of the things you can do, just a few common workflows.
Let’s look at an example of the UI by selecting the HTTP request and response template. In this example Logic apps will generate a request URL and you can have it return a response with your own header and body. This can be useful for stubbing out a simple API.
Clicking new step opens up several options including a new action, conditional statement, or loops. If I select action you can see that there are a lot of options here, starting with Azure services. That means we can interact with SQL databases, Azure Functions, Service Bus and more.
There’s also a lot of community supplied actions for integrating with things such as Jira, GitHub, BitBucket, Basecamp, MailChimp, Salesforce, Sharepoint, and all the rest of these!
If I select the Jira option you can see some of the different actions that can be taken, and on the other tab are the triggers available.
So, at a high level this is Logic Apps! It’s a hosted way to create and manage business processes in the cloud.
Okay, hopefully you’re familiar with what App Service offers. In the next section we’re going to go from high level overviews into more low level development. Alright, I’ll see you in the next lesson!
About the Author
Ben Lambert is a software engineer and was previously the lead author for DevOps and Microsoft Azure training content at Cloud Academy. His courses and learning paths covered Cloud Ecosystem technologies such as DC/OS, configuration management tools, and containers. As a software engineer, Ben’s experience includes building highly available web and mobile apps. When he’s not building software, he’s hiking, camping, or creating video games.