Operations | Monitoring | ITSM | DevOps | Cloud

Azure Service Bus is a brokered messaging service offered by Azure that can be used to decouple the various applications forming the business integration solving the business problem. The Applications transfer messages between them to share the data between them. The messages can be in XML, JSON or simple text format.

There are two types of queuing mechanisms supported by Azure. Storage Queues are part of the Azure Storage infrastructure, feature a simple REST-based GET/PUT/PEEK interface, providing reliable, persistent messaging within and between services. Service Bus Queues are part of a broader Azure messaging infrastructure that supports queuing as well as publish/subscribe mechanism, and more advanced integration patterns.

Azure App Service, one of the most used among the Azure offered Services. When the requirement is to host web applications, REST APIs, and mobile back ends, Azure App Service is the go-to Http- based solution. Apps hosted in Azure App Service can be integrated with on-premises or cloud services. It supports both the Windows and Linux-based environments to run and scale the applications.

In a real-time business scenario, various Azure services are integrated to define a business process. Day by day these business processes grow in complexity and monitoring them turns out to be a real challenge. In order to overcome these challenges, Serverless360 provides end-to-end tracking via Business Activity Monitoring.

Azure Functions team is back again for their monthly live webcast with a lot of interesting updates and community highlights. This webcast was quite special since their announcement on Social Media regarding the new Azure Functions management experience in the portal certainly created a buzz. In this session, Jeff Hollan, Byron Cardiff and Matthew Henderson joined to give us a picture of the latest happenings in the Azure Functions space.

Two years ago, I wrote a similar post on Microsoft Flow: How to pass the SQL data table results in a Markdown-formatted table into an Email notification or Approval Requests. It is still quite up to date, i.e., it is an excellent solution that you can still use today. The only problem with that article is that I was using “send an email” action in Power Automate Outlook connector that is currently deprecated.

Recently, I had a scenario in which it was necessary to access the content of the source JSON message and extract a property that contains a date-time. That property was in the last object (a repeating object) for control purposes, and my first idea was to get it done with Azure Function and that’s it. But then I was thinking, if I need to use Function for all these simple tasks, what’s the point?

Azure Functions is a serverless compute service that lets you run event-triggered code without having to explicitly provision or manage infrastructure, in other words, Microsoft’s Azure Functions is a modern serverless architecture, offering event-driven cloud computing that is easy for developers to use. This blog is about Azure Functions triggers and bindings.

You may know my series of blog posts about BizTalk Server Tips and Tricks that I normally write in the BizTalk360 blog. Well, the goal of this Logic Apps Tips and Tricks series will be the same; to provide simple tips or tricks that may improve your performance on developing Logic Apps workflows, avoiding issues, apply best practices and so on. But you may think, “What a strange way to start this topic, deprecated actions? Why should I use deprecated actions?”.

It is really exciting to see the Azure Functions team back again to the monthly live webcast after quite a long time. Here is a bit of introduction about this webcast who is new to the community, the Azure Functions team at Microsoft has been conducting a webcast every month to let the community stay up-to-date on the latest developments. This is a nice way for them to reach out and engage with the community to gain feedback on the features.