Click here to Skip to main content
14,981,841 members
Articles / Hosted Services / Serverless
Article
Posted 30 May 2018

Tagged as

Stats

1.1K views

Make Serverless Music – Orchestrate your workflow with Azure [Part 2 – Logic Apps]

Rate me:
Please Sign up or sign in to vote.
0.00/5 (No votes)
30 May 2018CPOL2 min read
A quick walkthrough on taking the Flow created in Part 1 and upgrading to Azure's workflow orchestration offering

Ready for a 30 second tutorial? Because Microsoft recognizes the needs of its users often grow and evolve outside your initial estimates, they’ve made it a 2-step (I’ve made it in to 4 steps for verbosity) process:

  1. Read & work through Part 1 of this series
  2. When you’re done, go to your Flow dashboard and click the Flow you just created
  3. Click ... More near the top of the screen
  4. Choose ‘Export’ | ‘Logic Apps template (.json)’

Image 1

DONE!

OK not quite, let’s walk through importing this in to Azure’s IT-Pro Enterprise-grade workflow orchestration offering: Logic Apps. As of the time of this writing it’s pretty well-known in the integration/orchestration space that MSIT itself has migrated over 1000 back-end processes at Microsoft from various systems, scripts, etc in to Logic Apps. This product is no joke, y’all. The execution engine for Logic Apps is the exact same one you’re sending requests to when you submit an Azure resource deployment request (ARM Template, Portal, or otherwise); it’s robust, resilient, and reliable.

Importing a Microsoft Flow in to Logic Apps

First thing’s first, fire up your Azure Portal.

Now, because what you’ve exported is essentially the JSON definition for a Logic App that will do everything your Flow did, we need to deploy it as such. To do this in the portal, click “Create a resource” and search for, aptly named, “Template deployment”

Image 2

Go ahead and click Create New and choose ‘Build your own template in the editor’:

Image 3

Choose, as you might’ve guessed, ‘Load File’ and pick your exported Flow JSON file. You’ll get the JSON loaded in, not formatted, so you just have to trust it 😉 Click ‘Save’ and behold some more Azure magic.

The next screen asks you for the Azure resource Basics, but also asks you to fill out any custom parameters your Flow needs! In our case, it only needs to know the name of the Flow and its location – easy peasy:

Image 5

Once deployment is complete, head to the created Logic App. First thing’s first, we have to turn it on by clicking the ‘Enable’ button.

Image 6

Once you’ve done that, go ahead and click the ‘Logic App Designer’. You should be met with a familiar sight:

Image 7

Let’s check out our HTTP endpoint – this URL will be different from the one in Flow – and give it a quick test to make sure it’s all kosher:

Image 8

Image 9

And that’s all there is to “growing up to Logic Apps” from Microsoft Flow. The designer experience is exactly the same if you want to start from scratch and, as I alluded to at the end of the Flow blog post, Logic Apps has a much richer DevOps story as you can deploy them from ARM Templates using Visual Studio Team Services and even author them within Visual Studio 2017 using the Logic Apps Extension.

Next up, checking out this same implementation with Azure Functions!

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Share

About the Author

BC3Tech
Software Developer (Senior)
United States United States
I'm a Sr. Software Engineer in the Seattle area primarily focused on serverless technologies in the cloud. In my free time I enjoy hiking & other adventures with my family around the Puget Sound and the country! You can find out more about me at my homepage: http://bc3.tech/brandonh

Comments and Discussions

 
-- There are no messages in this forum --