Creating an Azure Logic App Directly from Visual Studio

April 08, 2018

In previous posts, I’ve talked about setting up notification systems using logic apps, and shown how you might send Tweets automatically.

One of the things that sort of stands out with logic apps when you first come to them is how online they are. That is, you get a nice visual editor, and they run in the cloud. But what about when you want them to be part of your source controlled solution?

Well, the good news (and the reason for this article), is that logic apps are, behind the scenes, just JSON files with a nice designer. You can certainly source control the underlying files; but you can also edit these, with the same designer you get on the web, directly in VS.

Logic App Tools for Visual Studio

Microsoft have kindly released a VS add-on that will allow you to edit logic apps inside Visual Studio. You will also need the Azure workload installed in Visual Studio.

azure logic apps 1

Creating Azure resources inside VS is done by creating a new Azure Resource Group:

azure logic apps 2

You then get asked what type:

azure logic apps 3

This creates you a template with a deploy (Powershell) script and two JSON files. Now that you have the VS add-on described above you can edit these JSON files in a visual designer:

azure logic apps 4

The logic apps designer that appears gives you exactly the same experience that you have on the cloud:

azure logic apps 5


Deploying this solution to Azure is very simple using the context menu:

azure logic apps 6

azure logic apps 7

You can monitor the output window to see the status:

azure logic apps 8

Finally, a quick look in the Azure portal validates that it has, indeed, deployed:

azure logic apps 9

And a quick look on Twitter confirms that it works:

azure logic apps 10

What about automatic deployment?

The process above works great, but isn’t very good inside any kind of continuous integration pipeline. Fortunately, we have a ready-made deploy script (remember the helpful Powershell script above?).

There’s a couple of tweaks to run this out of the box: - If you didn’t call the resource group the correct name when you created the project, you can correct this inside the script:


- You'll need to log into Azure first:


This displays a log-in prompt and allows you to log-in (hold that question for a minute).

- Finally:

.\\Deploy-AzureResourceGroup.ps1 -ResourceGroupLocation westus

Obviously, the appropriate location might not be westus (it isn’t for me)

Back to your question - which is that, if this log-in displays a prompt then it’s not very automated

There’s a couple of ways to solve this, but this is the easiest*:


And enter your credentials manually. Then:

Save-AzureRmProfile -Force -Path "c:\\MyProfile.json"

That exports the details of your profile; finally, when you need to automatically log-in:

Select-AzureRmProfile -Path "c:\\MyProfile.json"

Now you’re logged on just like before.

Edit logic apps

Now that our app is in Azure, we can edit it:

azure logic apps 12

This opens the same window; and, if you didn’t have the code, it can be downloaded here:

azure logic apps 13

It’s worth noting that the version you can edit in cloud explorer is not the same version that you are editing inside the project.


Finally, using the Run History, you can view the successful (and failed) runs:

azure logic apps 14

Curiously, this logic app is fundamentally flawed (I didn’t realise this restriction in Twitter):

azure logic apps 15

Easily fixed, though:

azure logic apps 16

azure logic apps 17

Please don’t try that at home. I don’t want a cease and desist order from Twitter !


*Easiest is not necessarily the best


Profile picture

A blog about one man's journey through code… and some pictures of the Peak District

© Paul Michaels 2024