Microsoft Azure Logic Apps Reviews

For one of the projects that we used, this solution dealt with SharePoint and Power apps. So there, we have to do some kind of connectivity and calculations on the fly. It was related to reading a file and our heavy processing. That was one scenario. There have been a few others as well.

If we are working with a service-oriented architecture, as an architect as a baseline, it supports us very well in terms of expandability, and the kind of robustness it brings, especially with its serverless nature is fabulous. That's not a problem. So that's how we view it. It allows us to focus on a particular functionality within this context, and that's great. 

However, the challenge lies in the fact that it's often difficult for most developers to integrate it into their daily activities seamlessly. That's where it becomes problematic. 

There are two challenges. First, it's a bit costly at the end of the day. It's difficult to calculate pricing, and that affects the business. That's one challenge. 

Second, it's asynchronous. So, getting a development team to work on it, making it function properly, is a challenge. Salespeople often have this new notion of sequential programming, so they don't fully understand how it can be used in a disconnected or asynchronous mode. It's difficult for them. It's challenging. In terms of analytics and navigation, using all these modern architectures, it's there, and it works nicely. But if somebody is using a legacy application or needs to make an extension, then it becomes difficult because those applications don't really support asynchronous processes, especially building applications this way. It's challenging to sell those things.

So, pricing and handling asynchronous processes are the two main areas that need improvement.

The primary challenge is handling the costs, especially the difficulty in providing precise, concrete numbers to the business. This becomes a significant issue because we can't predict what kind of processes will be required. Once you invest, there are various variables in the market, such as manufacturing, and once you get connected, you need a connector, which often comes at an additional premium cost. Every business is sensitive to this aspect. 

Sorting out the licensing is very complex, particularly when using multiple services. For example, if you want to use Power Apps, Logic Apps, SharePoint, and other services, things become complex and confusing. You can't go to the business and provide a clear budget because businesses prefer a specific number they can allocate. However, it's challenging to provide precise, point-to-point cost estimates because there isn't much detailed information available online. The cost estimates are often high-level.

Here is an example. We are building a chatbot, and one part of it is based on the number of requests. We're a company with 7,000 employees. If the chatbot becomes successful, we could have 100 questions or even 20 to 30 interactions per day per user. However, if it's not successful, it might drop down to just 1 to 2 interactions per day from 20 to 30. The cost variation is so significant that it's challenging to present a consistent cost to the business. It could range from ten thousand dollars per month to maybe just one thousand dollars. The range is hard to explain, and in reality, we don't know. And then there are hidden costs. When you try to connect to something, you suddenly realize it's also license-based, user-based, like seven engineers not using it. The price can increase unexpectedly from a couple of hundred dollars to maybe a few thousand dollars per month or even more. This complexity is causing people to avoid using it.

I have been working with Azure Logic Apps for a couple of years. We did a few projects here and there. Normally, for Azure Logic Apps, we worked in patches, with a few clients agreeing to use it for specific functionality. Most of them are related to SharePoint or Office. They're on the cloud directly. But we haven't come across a situation where the entire application is built around Azure Logic or all these modern services, purely Azure. Generally, it's whether Azure databases may be slow. They use Power Apps and SharePoint in the backend, which is the most popular approach. It's a double operation.

The stability is more the way we develop it. It is not a problem with the apps.

It is scalable. I have never seen a situation where there are scalability issues.

We work with enterprise and medium customers.

The customer service and support are very tricky. They will promptly come to help. Most of the time, they are able to help. But if things get complex, it is difficult to get the information from them. Generally, if you have a paid service, they are good.

Neutral

It is a service, so we don’t need to install it.

Deployment is okay once you set up the process correctly. Normally, it doesn't work in isolation. So whenever we update, there will be two or three of these. PowerApp and other things will be updated. The update is okay. It's not a problem. If you have to move between environments, then it's something we need to think about. There's no particular standard for people to have different things, and in some cases, we do have. It can be resolved.  

We used this solution for one or two projects, but it cost a lot. Very expensive.

Overall, I would rate Microsoft Azure Logic Apps an eight out of ten. It is a good product but not the best.

I would advise that you should know how service architecture works. You should know where the service is going to be adjusted in their application. It's not that you'll start putting everything. You need to understand the nature when you go with service architecture. If you don't understand, then there is a problem. 

Otherwise, it is okay. It's a good solution. You may have a few challenges, but it will be okay. It's a nice solution.

The solution is used to create automation as a part of SIEM. It is also part of the security orchestration. When we need automation, we use Sentinel to create a playbook. We can automate things according to the playbook. Sentinel, playbooks, and Logic Apps are interconnected.

Templates are valuable. There are formulas so that we can modify them according to our needs. Connectors are very useful for streamlining data integration tasks. The solution has a lot of data connectors.

The solution must generate more templates. Pre-defined templates would make automation easy for engineers. There must be a separate portal for Logic Apps. It must provide features like drag and drop and image import. It would be helpful if the vendor could provide more data connectors.

I have been using the solution for one and a half years.

We did not have any breakdowns. It is a useful feature of Azure.

The number of users depends on the clients. If the clients require anything, they can create an incident, and we receive an alert on the console, just like ServiceNow. It is really useful. We need not log in to Azure repeatedly. We have visibility into alerts and threats. It helps with threat hunting.

The installation was neither easy nor difficult. We must know about subscriptions and permissions. We must know what roles are required to install it and what subscriptions are required to integrate with the third-party products.

If we have P1 and P2 subscriptions, Microsoft will not charge us for creating applications on the Azure portal.

I will recommend the tool to others. It is not only useful for automation but also for monitoring Azure storage. Overall, I rate the product a nine out of ten.

Logic Apps are used for integration. We use Azure Data Factory (ADA) for most cases, but in a few instances, we'll go with Logic Apps if ADA is not sufficient.

The use cases are very limited. But for a few specific things, especially when we want to integrate with .NET web applications, we'll go with Azure Logic Apps.

Its integration capabilities are great, allowing connectivity with various applications and services. 

If Logic Apps could be built-in as part of Azure Functions, it would be better. We don't need to use it for every case, only for special cases. However, Logic Apps require writing more logic and are more critical in terms of performance.

It's not a useful tool. When I use it for bigger cases, I don't think it's much faster. The main issue is performance, especially when dealing with large amounts of data. Performance-wise, that's the only thing Microsoft should focus on.

We are currently using Azure Logic Apps. It has been around for four months. 

I would rate the stability of this solution a six out of ten. It is average. 

The scalability is good. I would rate it a seven out of ten. Currently, the usage mostly depends on the project. We are using it with five to six team members.

The technical support is good, especially from Azure. We are getting good support.

Positive

The initial setup was a little complex.

It's complex because when we want to build integration processes or certain tasks, we need to write more code, and it's not straightforward. The format is different, so it's not easy to figure out.

I would rate my experience with the initial setup a five out of ten.

The deployment depends on the project. Sometimes it takes one day, sometimes two days. It depends on the requirements. Each case is going to be different. We are using Azure DevOps.

The pricing is okay. It's not highly priced. It's in the medium range. It's not like Oracle, where there's a separate application. When you purchase Azure, you get all the features included. Most of the time, you get a good rate. It's not cheap, but it's also not costly.

I would rate it seven out of ten. 

We are using Azure Data Factory, EEF, and Azure Data Lake.

For integration purposes, it's good. You can go with Logic Apps, but it depends on the requirements. If you can achieve good features with other data gateways, like Azure Data Factory, then you can go with that. Because Logic Apps has a different process, Azure Data Factory is simpler. This is why we try to minimize the usage of Azure Logic Apps and only use them when required.

I would rate it around six based on its performance, usability, and reliability.

Microsoft Azure Logic Apps is a fantastic suggestion, especially for those who may not have extensive coding knowledge but understand the requirements well. It provides an easy way to create an auto-response solution. For instance, if you have services running in Azure and want to generate an alert, it allows you to integrate seamlessly. You can trigger tasks based on alerts, creating multi-layered tasks with loops, conditions, and more. It will enable you to perform multiple actions.

I have an example where I automated a business process using Logic Apps and even published an article on the same solution. The customer is required to monitor their NSGs. In the Logic App flow, I designed an alert system if any deny event occurred. It created an HTML-formatted alert identifying the request details, such as the user, specific server, and port that were denied. This alert was then sent to the respective admin users, allowing them to enable the request. If enabled, the request would go back to the system, triggering a script to enable it; otherwise, it would remain disabled.

In another experience, I created an internal application for the purchase order department using Power Apps and Microsoft Azure Logic Apps. I utilized it to gather data from an Azure SQL database and generate a PDF report. This report was then sent to the relevant stakeholders.

Using connectors in the product is quite straightforward and user-friendly. The platform provides a list of connectors, and users can easily search for the specific connectors they need. 

An area of improvement I've encountered is related to the number of connectors available in Logic Apps. While there are many connectors, I found that the "send email" connector may not work as expected, and one has to rely on Office 365 plugins or other alternatives. This could enhance user experience, especially when considering the additional overhead and licensing requirements associated with Office 365. It also needs to improve security features. 

I rate the solution's stability an eight out of ten. 

The tool's scalability is managed by the backend service itself, as it is a managed service.

The tool's tech support is good and customer-friendly. 

The tool's deployment is straightforward. The deployment time can vary and is not necessarily due to the complexity of the product itself. Instead, the time taken depends on the specific requirements of the integration. Factors such as the complexity of the requirement, the number of conditions, and the need for multiple tests can influence the deployment time. Correctly connecting the suitable connectors, using the appropriate syntax, and implementing loops, among other considerations, may contribute to the overall time spent on deployment. However, it's important to note that the solution, as a service, is not inherently complex.

I rate the overall product an eight out of ten. For anyone looking to automate processes, tasks, configuration, application execution, script execution, or data extraction from databases without extensive coding knowledge, I would recommend using Microsoft Azure Logic Apps.

The solution can be integrated with many services. It can integrate with Azure Automation, Azure Defender, web apps, and essentially anything for which a connector is established.

Our customers use SAP to create approval requests from their managers, like PO requests and approval and leave requests. Everything is generated from SAP. We pull the information from SAP and send it to the manager on Microsoft Teams. A manager needs to approve it on Teams instead of SAP. The solution builds connectivity between Teams and SAP.

The prebuilt connectors available for SAP are really useful. The solution is easy to use and has a plug-and-play or drag-and-drop concept. We can create connectors easily. We don't have to do too much R&D and write codes to make it work.

The solution could add an AI version to make it easier for people. Microsoft is deploying Copilot across all the platforms like Microsoft 365, Teams, Word, Excel, PowerPoint, and everything. Azure can also add Copilot to the product to make it easier for developers.

I have been working with the product for the last five years. I am using the latest version of the solution. I help Microsoft partners to scale their business in the Middle East, Africa, and Central and Southeast Europe. I run alliances or sales as a service for Microsoft ISVs.

The product is very stable. I rate the solution’s stability a nine out of ten.

The solution has high scalability. Currently, we have 100 users. Eventually, we will scale to 3000 users. We serve all types of clients, particularly medium enterprises. However, the solution can be scaled to any business. I rate the solution’s scalability an eight or nine out of ten.

We are very happy with customer support.

Positive

I have used Power Automate. I used Power Automate in one of our solutions for our customers. It runs in more than 800 stores and has around 20,000 users.

The initial setup is pretty straightforward. I rate the ease of setup an eight or nine out of ten. The product is deployed on the cloud. The setup takes around one month from the testing to production. It also includes the time for the team to get educated about the solution. We were more familiar with Power Automate. We had to do a little bit of reading first to deploy the solution.

To deploy the product, we downloaded a trial version, experimented, looked at the menus, downloaded available resources, joined the community, and sought some help from Microsoft, our technical partners, and development managers. There's a lot of documentation available. We reviewed the documentation too.

The tool’s pricing could be better. I rate the solution’s pricing a four out of ten on a scale where one is low, and ten is the high price. The product is not pricey. It is a pay-per-use model. The more transactions we do, the higher we will be charged. We are charged for the actual transactions.

People considering using the solution should find out their business use case. Some applications are very heavy on transactions. They should be careful about the total number of sessions they will need to purchase. The solution is fantastic if the business use case does not require too many transactions. Overall, I rate the solution a nine out of ten.

There are two ways to use this solution. Firstly, you can connect Azure to other solutions like Jira. It automatically populates all the services. Secondly, once you are logged in, you can create your own resource group and see all these services.

We have 12 teams using this solution. 

We can write external features and transfer the data using JPIMs securely which has been most valuable. 

The standard logic app could be simplified. Thats what we would like to see in the next release.

I have been using this solution for five years. 

This is a stable solution. 

This is a scalable solution. 

The Microsoft support team provide good support. We have experienced some delays where it has taken a few hours for solutions to be provided but in general they supported us well. 

The initial setup is simple. A straightforward setup takes approximately one to three hours. Once a policy and conditional statements are created, everything can be setup in the logic app. 

Overall, this is a good solution. More issues tend to appear when connecting in an on premises environment compared to the cloud. 

I would rate this solution a nine out of ten. It is flexible and user-friendly. The logic app is specifically easy to navigate. 

We use Microsoft Azure Logic Apps to do a lot of workflows and from different areas. For example, connecting to web services, and websites, triggering based on certain conditions.

The most valuable features of Microsoft Azure Logic Apps are the triggering based on certain events. You can trigger a Logic App and put your logic behind it and take certain actions. The actions could be anything based on the business logic. For example, if you say something happens, an order comes in, and the order can sit in one of the Azure services. Whenever an order comes in, the Logic App can go look and trigger an event. You can write your logic inside your Logic App and it works similar to a workflow.

The solution is always improving every month.

I have been using Microsoft Azure Logic Apps for a few years.

The stability of Microsoft Azure Logic Apps is stable. However, we have had some issues in the past. They do resolve issues that arise from new releases.

Microsoft Azure Logic Apps is scalable.

The people who are using Microsoft Azure Logic Apps are the IT and teams who are supporting the company or organization. For example, Azure administrators and developers. There is a total of approximately 10 people using the solution.

The support is good from Microsoft. Based on the premium surveys we have, they act immediately.

The initial setup of Microsoft Azure Logic Apps was not complex. It is straightforward. Anyone who's familiar with the service could set it up. However, you can build complex things on top of it, on a very high level.

We do not need very many staff members for the maintenance and support of the services in Microsoft Azure Logic Apps.

My advice to others is Microsoft Azure Logic Apps is easy to use compared to other services. You don't need hardcore development experience to use it. It's more of a UI-based, drag and drop, sort of logic-building capability. You don't necessarily require to have core developer skills to use it. You only need to be familiarized with some of the services and basic administration of Azure. Anyone can build applications based on Logic Apps.

I rate Microsoft Azure Logic Apps a seven out of ten.

We mainly use Azure Data Factory, Azure Synapse, Synapse Analytics, Data Lake storage, and Azure Databricks.

I mainly use Microsoft Azure for services on the cloud. We're trying to create an Azure Data Transfer Layer (DTL) tool directly in the cloud environment.

We usually solve complex use cases with Azure Data Factory or notebooks. So, we haven't used Logic Apps extensively.

We used Logic Apps to return notifications and push them from Logic App to data lake storage. That's the kind of functionality we achieved through Logic Apps.

In Microsoft Azure, this orchestration tool is a data factory. It's simple to use and has good UI with most connectors available to connect with different source systems and databases and Azure Databricks. 

So, we use it as a data transformation tool. So, on a big volume of data, we can do it. I've been using Microsoft Azure for five or six years, so I'm quite comfortable with it.

Azure Logic Apps is an analytics tool that's pretty easy to use. Compared to AWS and GCP, it's quite comfortable. The UI is much improved.

Additional features or extensions could potentially be integrated with Logic Apps.  

I only used Logic Apps for a few months. But I have been using Microsoft products for ten years. For example, I have been using data engineering use cases I have been using Microsoft Azure for the last five years. 

Security and stability are quite good. I would rate the stability an eight out of ten. 

I would rate the scalability an eight out of ten. It was a back-end application used by developers for development purposes. It was an automated pipeline that received notifications and pushed them to data lake storage. Once built, it was rarely touched, only for adding notifications.

Our cloud engineers dealt with it, they raised tickets with Microsoft team.

I have been using Microsoft products for the last ten years. On cloud services, we use Logic Apps and data lake storage. Logic Apps for SQL databases. I used it in a project for six months.

And Oracle-integrated tools are new in the market. The client asked us because one of our clients has already purchased an Oracle license, and he introduced us to this tool. To use this Oracle integrator, data integrator, we explore it okay. Because he already has a license to use this tool. He asked us to use those tools. 

That's why we went on the Internet to explore it and learn how to use it. But in the end, we found that we didn't have expertise in these tools because our team hadn't worked on these tools earlier. So then we drop a plan to use this.

It is quite easy to setup Logic Apps. I would rate my experience with the initial setup a nine out of ten, with ten being easy to set up.

We used Azure DevOps for deployment, but for private endpoint configuration in the private cloud, it required infra-team involvement.  

Logic Apps is cheap with its pay-as-you-go model. We only pay for usage time, no license fees. So Logic Apps is good in that aspect.

I would rate the pricing a seven out of ten, where ten points mean a very expensive solution. 

Logic is okay. It's for a limited kind of application or short Apps. And, not for the complex applications.

Overall, I would rate the solution a seven out of ten.