Integration Down Under is a brand new Microsoft Integration & Azure webcast, in an APAC friendly time zone! And that is an idea that have been simmering for a long time.
We all love Integration Monday, one of the most successful MS Integration webcasts ever, but it was always a recurring joke between the AU/NZ integration professionals who would have to wake up the earliest to be able to watch. So, for a while now, we’ve been discussing how nice would be to have a similar webcast in a time slot that didn’t require lots of caffeine and an alarm clock setup to early in the morning, just to enjoy live…
Then earlier this year Bill Chesnut rallied the troops and brought together a group of Microsoft Azure MVPs – Daniel Toomey, Martin Abbot, Rene Brawuers and myself – to start this project. After a couple of crazy nights furiously discussing details and logistics – social media, logo, topics, among lots of other things – we’ve settled for an inaugural meeting on the 8th Feb, which will kick off the webcast with a series of lightning talks. Here is a taste of what you can expect on the first webcast:
- Bill Chesnut – API Management REST to SOAP
- Martin Abbott – Azure Data Factory v2.
- Wagner Silveira – Azure Functions Proxy
- Dan Toomey – Azure Event Grid
- Rene Brauwers – A reactive integration primer
You can register for the webinar here, thanks to SixPivot, which is kindly providing the Webinar facility.
So please join us on the 8th, and let us know what you think, what topics you are interested in hearing more next and how can we improve more and more!
Have you ever wanted to stop all logic apps in a resource group in one go – either for production maintenance, or maybe because that set of logic apps in a resource group is eating all your resources? If so, welcome to the club… What you probably found is that there is no way to do this in the portal. Coming from a BizTalk background where you can stop all orchestration – or even the whole application) with a right click, in some cases you will ask “Why?”, while in others you might shout “Khaaaannn!” (I know I probably did both). Continue reading “Enable/disable all logic apps in a resource group”
It is Saturday, the last Saturday of my Christmas holiday, and the weather is not exactly “friendly”, so instead of playing in a beach, I am home getting ready for work on Monday.
That reminded me that although I wanted, I didn’t wrote the classic “year in review post” for 2017 – and by classic I mean, the first ever for this blog… 😀 Continue reading “2017 – a year of firsts”
Last June I was one of the presenters at Integrate 2017. And man, I had a blast! Can’t thank enough Theta for sponsoring me going to the event, and Biztalk360 for having me as presenter. It was an amazing experience…
Today the video of my presentation has been published. So go check it out and also check out the amazing presentations on this year’s edition.
Putting theory into Practice
Continue reading “Unlocking Azure Hybrid Integration with BizTalk Server”
When it comes to developing Logic Apps, everyone has a preference. Some people like to develop in the portal, while others like to start development directly from Visual Studio. I am in the first group mainly because a lot of my logic apps involves integration with the Dynamics 365 CRM connector, which doesn’t play well with the Logic Apps editor after I apply the required parameterization (which reminds me that I have to blog about that – will write something about it soon). I also like the simplicity of just opening the browser and be able to develop, debug all in one go.
Continue reading “Developing Logic Apps in the Portal”
A while ago I saw a question in the forums where someone was trying to use a POST operation using the API Management action in Logic Apps and the action card didn’t have any way to input the body object.
To replicate the issue I’ve create a very simple logic app, so simple in fact that I didn’t even bother to define a trigger schema. After creating a new API using that logic app, to my surprise I also couldn’t find any input for the message body. Continue reading “API Management Gotcha – Empty Body Definition”
Previously in Note to self…
I got one step closer to my goal to export all logic apps from a resource group to a Visual Studio project, using linked templates to deploy all logic apps in one when required, but still being able to deploy individual logic apps for a patch template. In previous posts, I’ve managed to use the extend a open source component originally created by Jeff Hollan and maintained by Mattias Lögdberg, adding a couple of extra cmdlets. You can get the last post here.
Visual Studio ARM Deployment Project
For the last step in this process, I needed to create an Azure Resource Manager deployment project. I decided to go through the most pragmatic route – to use an existing project as template. So as a first step, I created an empty Azure Resource Group VS project and tried to find out how artefacts can be associated to it. Continue reading “Rethinking an old Logic App deployment package- part IV”
Previously in Note to self…
I’ve been discussing how I’ve leveraged Jeff Hollan’s Logic App Template Generator and some PowerShell goodness to export a ARM templates to all Logic Apps in a specific resource group. You can read about that here.
Linking ARM Templates together
Azure Resource Manager templates have the ability to link templates, creating a “parent-child” or “nested” relationship, allowing a single template to deploy resources that are defined in various individual templates. The advantages of this technique in my opinion are:
- Each resource can be defined in isolation, which makes maintenance of that resource simpler.
- Related components can be grouped in “parent” templates for a simpler deployment experience, but they can still be deployed individually if required.
This was exactly the type of solution I was looking for, after having to deal with the pain of replacing a logic app template in the middle of a monolithic ARM template containing another 15 templates. That would usually take a couple of hours to make sure that the template was replaced correctly and nothing was removed that would make the deploy to break. Continue reading “Rethinking an old Logic App deployment package – part III”
Previously in Note to self…
I’ve been discussing how my first Logic App deployment package was not exactly what I’ve envisaged. So when I had a chance to revamp it, I jumped into the opportunity. You can read about that here.
Logic App Template Generator
I’ve decided to use Jeff Hollan’s Logic App Template Generator – a PowerShell utility that Jeff created sometime ago and have made available on GitHub. Jeff’s PowerShell module have a two cmdlets: Continue reading “Rethinking an old Logic App deployment package – part II”