Logic Apps overview - Azure Tutorial

- [Instructor] So what about logic apps and how can logic apps help you with your workloads? So just a small overview here about logic apps. We build logic apps to automate business workflows. We can schedule, we can automate, we can orchestrate tasks, all this using a no-code experience. And that's the big plus of this. So you don't need to be a developer in order to create those workflows, grab data from a SQL database, then send that data into Cosmos DB or getting some pictures from Blob Storage and then copy those pictures into another service. Getting data from a social network and then send that to cognitive services and understand is that post with a good sentiment, bad sentiment about your company, your organization. And then just add this to Salesforce, for example. So all this is some things that we can achieve using this no-code experience with logic apps. All this also using serverless models so there's no infrastructure for you to manage, like a virtual machine where you need to patch, you need to think about security of that infrastructure. So we don't have that. And of course fully managed and just an example like schedule a recurring task for example that you need to run multiple times a day. Something simple that sometimes we need to build. And sometimes I see customers building virtual machines for this kind of things where they could just build a very very simple logic app and they will be happier with the output of that. Some key terms that we have here, it will be like the logic app, well, that's the logic app itself. Then we also have the workflow, which basically is the series of steps that define a task, a business process or workload. Each workflow starts with what we call a trigger. That's what starts all those steps that we have here. So the trigger will be always the first step there. Then we also have actions, which basically subsequent step in the workflow that follows the trigger will just execute a certain task and then the another task. So we have those actions and we have connectors. So connectors we have basically built-in connectors and managed connectors. The built-in connectors are just like the name says, built-in, so the ones that come by default. And we already have literally hundreds of built-in connectors for logic apps. We can reach services that are Microsoft Azure 365 Dynamics, all of that. But we can also reach third party services. I was just giving the example of Salesforce before. So there is a connector for that. There is a connector for the most known social networks. So you can just use those. And usually those connectors, they come with a bunch of triggers, a bunch of tasks that you can use in your workflows, in your logic apps. Even if you need to get on-prem data, you can always do this. And usually we do this via integration accounts. Also, to get data and to do exchange message that follow electronic data interchange, so IDI enterprise application integration, AS2, EDVAC, X12. So all of those protocols also usually use this via this integration account. So how do you create the new logic app? Well, there's no code experience needed so you don't need to have coding experience. You can just use the Azure portal and there is a UI for you to use. And of course we also have extensions and we can also use Visual Studio and Visual Studio Code and do this straight from those applications, which to be totally honest, it's a little bit my preference because then we can just source save all the logic app. So it's something that you always want to have under source control system like Git or GitHub or DevOps, Repose, something like that.