Today I’m going to speak about another critical best practice, Tips and Tricks that you need to know, especially when you are developing your Logic Apps Consumption directly on the Azure Portal: If we are developing in the Azure Portal, can we roll back to a previous version of an Azure Logic App Consumption?

Modern applications are increasingly built using containers and microservices packed with their dependencies and configurations. Kubernetes is open-source software for deploying and managing those containers at scale—and it is also the Greek word for helmsmen of a ship or pilot. Monitoring the health and performance of your Azure Kubernetes Service (AKS) cluster is critical to ensure that your applications are up and running as expected.

Today I’m going to speak about another important Best practice, Tips, and Tricks that you need to know when you start developing your Logic App solutions: How to get the proper error message from a Logic App failure?

One of the critical differences between distributed tracing and business activity monitoring is that distributed tracing usually assumes that your transaction executes from start to end in a reasonably short time. An example would be that your call to an API might then drop a message on a queue which a function processes and loads into a database.

Let us consider that you have implemented an integrated solution and are using Serverless360 Business Activity Monitoring (BAM) to help provide your support users and business users with visibility of what is happening in the business transaction. BAM provides you with distributed tracing to attain maximum visibility on the integration solution that the functional operations team needs.

Welcome again to another Logic Apps Best practices, Tips, and Tricks. In my previous blog posts, I talked about some of the most essential best practices you should have while working with the Azure Logic App: And some tips and tricks: Today I’m going to speak about another critical Best practice, Tips and Tricks that you need to implement while administrating your cloud integration resources: Implement good governance policies.

Over the last few years, Microsoft has built excellent tooling around different technologies. Today, everything is available and achievable through the Azure Portal, which helps manage complex solutions. However, this brings in challenges when it comes to managing the distributed resources. The struggle to keep track of messages or know the flow of messages through these distributed resources is growing day by day.

In my previous post, I explained How to retrieve Azure Key Vault Secrets using Azure Functions, where you can understand Key Vault URL and the Secret name to retrieve a secret generically, you could use it inside all your Logic App Standard workflows, whether they use the same Key Vault resource or different ones.

Many organizations are investing heavily in the data space, and Azure Synapse is one of the technologies in the Microsoft stack which is very popular. Within Synapse, Data Flows are the component of Synapse used to orchestrate the movement of data into and out of your Data Lake and for orchestrating jobs within your Data Platform. The business heavily depends on your data platform for movements of data within the organization and the analytics-driven from data via Synapse.

Azure Key Vault is a cloud service for securely storing and accessing secrets used by your cloud applications. A secret is anything that you want to tightly control access to, such as API keys, passwords, certificates, or cryptographic keys.