Operations | Monitoring | ITSM | DevOps | Cloud

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.

Cloud Docs feature in Serverless360 helps you to document your Microsoft Azure Subscription. It comes with the capability to aggregate data from disparate Resource Providers in Microsoft Azure in a single report. This allows for the creation of composite technical documentation across resources enabling richer insights that would otherwise be impossible. Interpreting your cost and resource information on Microsoft Azure subscription into legible documentation is what Cloud Docs are for.

With the accelerated pace of digital transformation, DevOps, adoption of new platforms, and also managing cloud resources are becoming increasingly challenging for central IT. Applying available best practices, compliance requirements and cost management are adding to the challenge. With the Serverless technologies, customers can apply such policies to cloud resources and run them over a long time.

Logic Apps are a gift to the integration of business scenarios as they are quite easy to understand and integrate with other systems but there are some challenges faced by the users in real-time.

This blog explains a peculiar issue faced when Azure Durable Functions are deployed using Azure DevOps. In case you need to know what Azure Durable Functions are, please refer to Microsoft’s documentation on Durable Functions here as the explanation of it, is not under the scope of this blog. Durable functions work best when built with versions .NET Core 2.2 and above. After developing and testing a durable function, it can be deployed to Azure in many ways.

This article will focus on using Azure Application Insights to monitor the real-world business apps. Azure Application Insights is an Application Performance Management (APM) service for developers and DevOps professionals. It is used to monitor an app that is live in real-time. It supports a variety of platforms including .NET, Node.js, Java, and Python hosted on-premises, hybrid, or any public cloud. Application Insights can be used in two ways to monitor your Application.