Microsoft Azure offers a cloud-based messaging service called Azure Service Bus. The goal is to streamline communication between disparate components or applications, regardless of whether they are distributed across multiple environments and locations or operating on the same Azure platform. With Azure Service Bus, you can develop distributed systems that are scalable, reliable, and decoupled.

Welcome again to another Logic Apps Best Practices, Tips, and Tricks. In my previous blog posts, I discussed some of the essential best practices you should have while working with the Azure Logic App. Today, I will speak about another helpful Best Practice, Tips, and Tricks that you must consider while designing your business processes (Logic Apps): How do we get distinct values from an array or repeating structure?

In the first part of this proof-of-concept – How to replay messages from Azure Service Bus? – Part 1: The dead-letter queue, we explored how to replay messages that have entered the dead-letter queue. In this second part, we explore how to resend a specific message of our choice.

When working and dealing with asynchronous messaging patterns – in this case, using Azure Service Bus – depending on the requirements, you will find many scenarios when you need to reprocess messages. Sometimes, a message failed because a system was offline for a certain period, there was a bug with the service, and we needed to resend specific messages and many other reasons.

In today’s cloud-centric, serverless computing landscape, applications are increasingly distributed and complex, composed of numerous microservices, functions, and external dependencies. Azure Functions, a serverless compute service offered by Microsoft Azure, plays a pivotal role in building scalable, event-driven applications.

FinOps is an evolving concept increasingly practiced in cloud computing organizations to manage and optimize their infrastructure cost. It requires team collaboration among Finance, Engineering and IT Operations to gain a deep understanding of the expenditure, take financial accountability, and make informed decisions to maximize the business performance.

Organizations that invest in cloud technologies like Microsoft Azure might notice that cloud costs can easily get out of control. When cloud services use the Pay-as-you-go payment model, small amounts must be paid each time a cloud service is used. However, when you have deployed hundreds of cloud resources, the total spending can end up with a much higher monthly bill than expected. By optimizing your cloud costs, you lower your monthly Azure bill and gain cost efficiency and predictability.

If you are running a company, you might have provisioned several Virtual Machines in Azure. Those VMs might execute critical business processes like incoming orders, processing healthcare-related data, handling logistics processes, or any other processes that are important in your industry.

Azure API Management is a Microsoft Azure cloud-based solution that helps businesses effortlessly create, publish, secure, and analyze APIs (Application Programming Interface). APIs are the building blocks of any business and play an essential role in data exchange. Azure API Management monitoring is vital to enable the business to function seamlessly. It helps early problem detection, resource optimization, and data-driven decision-making to increase the quality of the API ecosystem.

Let’s embark on a new journey as we begin a series of blog posts dedicated to the migration of BizTalk Server to Azure Integration Services. I’d like to highlight that when I mention the migration to Azure Integration Services (AIS), I’m making a clear distinction from Logic Apps. This differentiation is important because, contrary to what some consultants and salespeople may suggest, migrating BizTalk Server entirely to Logic Apps is not a viable path!