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: implementing Error handling inside Logic Apps.

Are you surprised? Are you under where are the first four tips? I start this series of blog posts on my blog, and you can see and read the previous Best practices, Tips, and Tricks here: And I will be sharing some of them here and others on my blog. So stay tuned for both blogs. Of course, the most recurring task is adding comments to our triggers and actions, but it is always good to know you to delete them. Some of you may be thinking that is a trivial task, simple like adding a comment.

Implementing a business process can be challenging because you typically need to make various services work together. Think about everything your company uses to store and process data. How do you integrate all these products? Azure Logic Apps gives you pre-built components to connect to hundreds of services. You use a graphical design tool to put the pieces together in any combination you need, and Logic Apps will run your process automatically in the cloud.

With the emergence of the hybrid solutions, solutions such as BizTalk Server that were purely on-premises solutions are communicating with SaaS solutions and are being deployed in a hybrid model. There are many advantages to cloud integration. Organizations can take advantage of powerful features of the Azure Platform and other cloud-based services from Microsoft, such as Service Bus, Logic Apps, Power BI, and Event Hub.

I recently published a post regarding BizTalk Schema Validation: DateTime Restrictions on my personal blog. Still, I was curious to see if we have the same capability in Logic Apps Standard and Consumption. And by doing that, see how compatible these two technologies are regarding XML Schemas and validations.

There are such cloud services that can drastically accelerate your innovation and reduce your time to market by providing you with functionalities that are simple, ready-to-use and that allow you to add a real added-value to your users. Azure Communication Services is one of those. In this article, we’ll have an overview of what Azure Communication Services (“ACS” for short) is, what functionalities it provides and what are some of the use cases in which it can be leveraged.

Azure SQL Database is at the heart of many applications running on Azure. Whether a company is migrating its on-premises applications to Azure or designing a new application from scratch, there are high chances of Azure SQL Database being considered and used.

App registrations is a mechanism in Azure AD allowing to work with an application and its permissions. It’s an object in Azure AD that represents the application, its redirect URI (where to redirect users after they have signed in), its logout URL (where to redirect users after they’ve signed out), API access and custom application roles for managing permissions to users and apps.

Over the years, containerization has grown in popularity among organizations and will continue to grow. For example, containerization is slowly becoming the de facto approach when it comes to building applications following the microservices architecture. It is undeniable that containerization has a lot of advantages, but these advantages come at a cost.

One of the most notable advantages of the Cloud is the ability to scale resources to meet demand. We then scale out or up when the demand increases, and we scale in or down when the demand decreases. For the record, scaling out / in refers to increasing or decreasing the number of instances of a given resource, whereas scaling up / down refers to increasing or decreasing the capacity (CPU, Ram, Disk, I/O performance) or a given instance.