Azure Logic Apps

| by Jonathan Allen Follow 615 Followers on May 01, 2015. Estimated reading time: 1 minute |

Historically working with BizTalk has been overly difficult. Once you get past very simple scenarios, the learning curve for BizTalk was so steep that most developers didn’t even bother trying. They would either hack something together or just skip BizTalk entirely and just use purely custom code.

Microsoft’s intends to fix this problem with what they are calling “Logic Apps”. Like BizTalk before it, Azure Logic Apps are focused on integration scenarios. The first thing you’ll notice is the large number of connectors to popular services such as Twitter and Dropbox in addition to the usual database and HTTP-based connectors.

API connectors such as the aforementioned Twitter connector use OAuth to generate a client token. Each API connector defines its own list of available actions for App Logic to consume. This is exposed to Azure using the REST API definition standard swagger. Like WSDL for the WS-* stack, applications can parse the API definitions and automatically generate a simple user interface.

Workflows need to be triggered by something. Some triggers are simply timer based, others watch for new data from connectors. And interesting feature of triggers in App Logic is that they are stateful. This allows your triggers to conditionally perform actions based on what it did previously.

By default, each action after the first is implicitly triggered when the previous action completes successfully. Developers may explicitly state the dependencies, which may be conditional based on expressions in the data.

Actions can be marked as repeated. When this is turned on, it acts like a for-each loop over the items returned from the previous action.

In the demo, Microsoft showed piping the result of a Twitter search into files on Dropbox. This requires the Dropbox action to have an understanding of the data pulled from the Twitter step. This can be done using notation known as Template Language Extensions. A first glance it looks like X-Path, but it is designed to work on JSON data formats.

App Logic and Visual Studio

If you don’t like working with the visual designers in Azure, you can create your workflows in Visual Studio. When working in that environment, you’ll be working on JSON-based workflow definitions in raw text format.

For more information on Microsoft’s replacement for BizTalk, watch the Channel 9 video Logic Apps.

Rate this Article

Adoption Stage

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread
Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread


Login to InfoQ to interact with what matters most to you.

Recover your password...


Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.


More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.


Stay up-to-date

Set up your notifications and don't miss out on content that matters to you