Operations | Monitoring | ITSM | DevOps | Cloud

You may be thinking, hey Sandro, what the hell? That is basic information and a straightforward task. Why do you want to write about that? Indeed it is, and you are right that it is an effortless and straightforward operation, at least at first glance. But like most things, nothing is that simple if you look closer. But let me explain better. Let’s imagine that we have an API call MoniorBizTalkPorts.

Due to rapid cloud adoption and with never-ending user requirements, the Azure architecture might become complex and you might eventually lose sight of the overall cloud estate and how it relates to each other. Since the Azure portal was designed in a technology vertical silo and it has near zero application visibility, it is not possible to monitor them as a business application in the Azure portal.

It has been a while since I wrote about this topic. I didn’t finish this blog series for several reasons, and now, one year later, it is the right time to continue this story. In the first part of this blog series, I have explained how you can expose a Logic App in API Management. It is a straightforward and simple process. Microsoft did a great job on this user experience.

Last week, I worked on a POC – how can we dynamically set SQL Server Connector configurations within Logic Apps? – that became a real project and a real architect solution. And one of the critical pieces was Azure App Configuration. Azure App Configuration stores configuration data as key-values.

In the first part of this article, we mention that at the moment, you have three options for you to start developing your Logic Apps: And we already analyze the advantages, disadvantages, and how to start developing Logic Apps by using the Azure Portal and Visual Studio. Today we are going to do the same but this time using Visual Studio Code.

In the first part of this article, we mention that at the moment, you have three options for you to start developing your Logic Apps: And we analyze the advantages, disadvantages, and how to start developing Logic Apps by using the Azure Portal. Today we are going to address. Today we are going to do the same but this time using Visual Studio 2019.

A few weeks ago, my good friend Josh Cook wrote a blog post for Power Automate about getting the error message when implementing the try/catch pattern with a Flow. We discussed if this could be used with Logic Apps, and Josh confirmed that it could, even though the Logic App documentation doesn’t cover it very well. Josh’s original Flow post is- Grabbing an error message from a failed run.

In this three-part blog postseason, we will describe the different development tools that are available or the different development approaches that we can use to create how Logic Apps. And for each approach/tool, we will describe: First of all, and rephrase Microsoft description: Azure Logic Apps is a cloud service that automates the execution of your business processes or workflows (sequence of tasks that produce a specific outcome).

Microservices architecture is getting adopted extensively in the world of distributed applications. There are various options and frameworks available to implement the Micro Services, e.g., Azure Service Fabric, Azure Kubernetes Services, Azure Functions, etc. The hottest trend these days seems to be serverless. The promise of consumption-based pricing, where you only pay for what you use and nothing more, is enticing.

Any application built today is expected to be highly responsive, highly available, and required to adapt to enormous changes in real-time at peak business hours, store ever-increasing volumes of data, and make that stored data available for users a fraction of seconds. To achieve such low latency and high availability, you need to deploy these applications’ Instances in data centers that are close to their users.