This document provides an introduction to Logic Apps, which allow users to simplify and implement scalable integrations and workflows in the cloud. Logic Apps are part of the App Service family and provide a visual designer to connect various connectors to build automated workflows and processes. The document outlines objectives, key Logic App concepts, and includes links to documentation, samples, and pricing information.
Thank you ________ for that introduction. As ___________ said, my name’s Mark Medrano. I’ve spoken here before and you may be asking, like I was, “Why another 101?”
Why indeed. Next time we’ll take a deep dive into something. But for now, here’s your introduction to Logic Apps. It was GA’d 4 or 5 months ago and through my awesome employer and their connections, I was able to meet some of the product team out in North Carolina. It’s just really cool to be reading some of the documentation and be like “Wow, that’s the guy that wrote this stuff, and I talked to him.” Geek star-struck I guess.
So here’s are some email addresses where you can get to me and a bunch of really smart guys. If you’ve got a question or problem with Logic Apps in the future, I’m sure we’d love to help out, whether you’re a client or not. Because, hey, community.
And to answer before anyone else asks, Yes, I am the Mark Medrano featured on the hit NPR radio show “Peak Curiosity” this morning. The segment will air again around 5:40 today and be available for all posterity on the KRCC website. I’m available for radio, short-run syndicated television, feature films. For the talent scouts in the crowd, get with me after the meeting and I’ll have my people get with your people.
Now back to business, here’s what we’re going to learn
*
*
Pretty simple, short and sweet presentation.
Straight from Microsoft, *
But most importantly, they’re part of the PaaS
That means it’s literally infinitely scalable, you don’t have to worry about maintenance, you only pay for what you use, and it quick to setup and tear down.
It’s got triggers and actions
A trigger is something that tells this logic app to begin executing
An action is everything else
For the purposes of billing each is an “execution”
So what’s the draw? This looks pretty simple, I can probably code something like this up easy.
It has lots and lots of pre-made components for you to reuse
And you’re right, it’s deceptively simple because all of those components are there to do much of the lifting.
For about 80% of the time, the designer does pretty well. But not everything is exposed so you’ll be getting your hands dirty in the workflow definition.
Behind the designer is plain a json definition. There isn’t too much in the way of intellisense support when you drop down to the code view but you’ll find it’s fairly forgiving – in that the error messages you see aren’t too hard to decipher.