Logic Apps Community Showcase


Some of you may know that while we’ve been working to improve Logic Apps, we’re also very aware of our community and working hard to stay involved.  You’ll see us actively involved in our forums, keeping track and discussing suggestions sent into Uservoice, and we recently started a monthly webcast (you can see our first recording here).  It’s been awesome to see how some of the community members have stepped up in the last month to keep involved and share out how they’ve been able to use Logic Apps — and it’s given us some very valuable feedback to work with as well.  Here’s just a few to share what all has been worked on:


Logic Apps for Site Provisioning in Office 365 – Stef van Hooijdonk

This is a good example of pulling together a number of different services (email, service bus, SharePoint) in order to complete a Logic App workflow. 

Logic Apps Working with On-Premise SQL Data – Steven Van Eycken

A very popular scenario, and Steven does a great job walking through the setup step-by-step with screenshots to help along the way.

How to Create an API App with Visual Studio – Sven Van Den Brande

Sven goes into how you can create your own custom API app to integrate with Logic Apps.  This is something we will also be going into detail during our next webcast tomorrow – so be sure to tune in.


Thanks to all those who have reached out.  We also got a good number of tweets to our twitter account (@logicappsio) and emails with community members sharing some apps they’ve created.  We’ll be sure to keep sharing some of the best as they come in.

For those of you interested in getting involved, be sure to tune into our next live webcast happening July 21 @ 11am PDT here.  You can also follow that link after the broadcast for a recording of the event.  We plan on sharing some cool new stuff we’ve been working on to help you make the most out of Logic Apps.  Thanks again – and be sure to let us know if you have any questions or comments.


Comments (2)

  1. ChrisMankowski says:

    What API or Swagger guidance is there to make an interface that is VERY easily consumed by logic apps?

    Here is my scenario that I want to work:

    – API accepts an enum, but rather than typing a number (enum value) type in the string

    – API accepts a string array, multi-select is possible

    – API allows a referenced object, to refer to an array of another object. etc.

    This is possible on the native Editor.swagger.io, however I can't make it work on Swashbuckle.

    I hope that this Azure Logic app "feature" is possible, since it is essential to the data mapping I wish to do.

    Specifically, I want to map ADFS claims from one provider to ADFS claims to another provider. (as an example, I'm creating an OAuth alternative that uses custom claims and requires mapping)

    If I should post elsewhere, LMK

  2. Chris!

    First off I’m really sorry, I didn’t see your comments come through until today so apologies for the late reply (at least I don’t think I’ve replied yet).

    There are a few options – one approach is that you create the swagger.json yourself (don’t rely on Swashbuckle, you can definitely use that as a base) and publish it in the spot specified by the apiapp.json file at your project root (defaults to /swagger/doc/swagger.json I believe).  

    However Swashbuckle does have some extension methods that make doing what you want easier.  There is an extension method called the “DocumentFilter” as part of swashbuckler that pretty much says “Do all your magic to guess my swagger, but then I’m going to manually specify a few things.”  You can see it on the Swashbuckle Github page under “Modifying Generated Operations.”  I’ve used that before the specify more custom Swagger and it works great.   You can actually see an example in this GitHub (the CustomDocumentFilter method is at the bottom): github.com/…/SwaggerConfig.cs

    Let me know if that helps

Skip to main content