Play Legos - The Microsoft way
Updated February 20, 2022

Play Legos - The Microsoft way

mahesh marthi | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User

Overall Satisfaction with Azure Logic Apps

The main USP of Azure Logic Apps is its connectors. MS has come a long way in providing various connectors to different services. The main implementation I have used is for services that provided Rest APIs to connect and also amongst Microsoft Saas and Paas offerings. Using MSI enables the management of authentication while using Paas/Saas offerings like Azure Functions, Log analytics, etc. The other scope where I have used it the most is for Playbooks (it's just a logic app with Sentinel Trigger) which offers huge relief for automation of SIEM (Sentinel.)
  • Connecting to different services using OOB connectors
  • Support for HTTP connectors which enables user to leverage RestAPIs
  • Readability, i.e., it looks just like a Visio diagram. Even managers or HRs can have a look and get to know what's happening
  • It's a Programmer's Lego. It's fun connecting them at the same time getting the work done
  • Limitations on a variable. For instance, an array can hold only 1500 as of now. There are several limitations like these. Increasing these numbers helps users a lot.
  • Nesting Depth: A single if-else statement itself takes two levels. If there are multiple levels, then there is no choice but to have another logic app.
  • Execution Time: This is a huge drawback as far as I am concerned. One can easily develop and deploy a logic app in 30 mins, which might take at least 3 hours if we have done it in any other way (like c# coding + functions). But the main pain point is the testing. If a loop has 5000 elements and is using the same variable, the runtime might take literally an hour to complete.
  • API connections: Let's say if an API has a limit of 1000 calls per 5 minutes, and my logic app needs to do 5000 calls. There is no way I can create 5 API connections and dynamically use them in Azure Logic Apps.
  • Explaining the functionality to customer was easy using Azure Logic Apps
  • Azure Logic Apps takes a long time to execute compared to conventional approaches (functions)
There are some logic that are too complex to be executed in Azure Logic Apps. It's a smart choice to execute them in Azure Functions. Azure Logic Apps has an OOB connector to connect to Azure functions. The authentication part is taken care of by MSI (so nothing needs to be done from the developer side. Just flip a switch and assign RBAC).

Do you think Azure Logic Apps delivers good value for the price?


Are you happy with Azure Logic Apps's feature set?


Did Azure Logic Apps live up to sales and marketing promises?


Did implementation of Azure Logic Apps go as expected?


Would you buy Azure Logic Apps again?


Microsoft Defender for Endpoint (formerly Microsoft Defender ATP), Microsoft Defender for Cloud Apps (formerly Microsoft Cloud App Security), Microsoft Sentinel (formerly Azure Sentinel), Azure App Service
1. For simple tasks / moderately difficult tasks (where there are not too many condition checks)
2. We have less time for development, and the Agenda is simple.
3. Avoid Azure Logic Apps when you are unsure about hitting the limits (check latest limitations of Azure Logic Apps in MS docs)

Azure Logic Apps Feature Ratings

Pre-built connectors
Connector modification
Support for real-time and batch integration
Data quality services
Data security features
Monitoring console