Microsoft Azure Logic Apps Reviews

We use Azure Logic Apps for orchestration and as a workflow engine. It's more about building and managing workflows. For instance, the tool can create a single integration that aggregates data from various sources. This capability is one advantage Azure has over solutions like MuleSoft.

One special aspect of Azure Logic Apps is its easy integration of various applications, especially when connectors are already available. For instance, there are connectors for database applications and systems like SAP. You can drag and drop the connectors to complete your integration quickly.

An area for improvement for Azure Logic Apps could be enhancing its ability to handle large datasets. When dealing with extensive data, we often have to use Azure Data Factory, which is mostly limited to scheduled jobs.

When we contact support, there is often a delay in resolving issues. They do not match MuleSoft's level of support.

Neutral

I can't provide specific details on the return on investment from Azure Logic Apps, as we haven't used it extensively in our projects. However, I can mention that it does offer the potential for a quicker setup of integrations due to its wide range of available connectors. If you're working with applications that have connectors within the solution, the process of building and deploying integrations can be faster. 

We often use Azure Functions to create integrations, perhaps even more than Azure Logic Apps, mainly due to technical considerations. We choose which component to use based on its suitability for the task and the specific technical requirements. For instance, Azure Logic Apps might not be the best choice for transforming large datasets, like moving 200-300 megabytes from the cloud. Instead, it was easier to handle this using Azure Functions. With Azure Functions, we could transform data from XML and then cache it. 

I would recommend Azure Logic Apps, especially for small organizations looking to expand their integration capabilities over time. With Azure Logic Apps, you pay for what you use, allowing you to scale your investment alongside your integration needs. Starting at as little as 100 dollars a month, you can gradually increase your investment as your integration matures.

I rate the overall product an eight out of ten. 

With Microsoft Azure Logic Apps, we can orchestrate and pull event-based triggers. We can use the solution to schedule a workflow based on any new record inserted into our database.

The solution's best feature is that it is compatible with the cloud and has many connectors and third-party adapters. You can connect it with almost every system.

We have lots of other systems. When we raised a complaint with Microsoft, they asked us not to use the solution for a particular purpose. We wanted to use Microsoft Azure Logic Apps, but we faced a timeout. We had a call with Microsoft regarding one of the issues. The support person with whom I was discussing was also not very comfortable with that question.

I have been using Microsoft Azure Logic Apps for the last one year.

We are working on the same technology in our company. Approximately 40 to 50 people on our team use Microsoft Azure Logic Apps.

The solution's customer support depends on the type of partner you are. If you are a gold partner, they will reply immediately. However, if you have a lower level of collaboration with Microsoft, they will take some time. The technical support team does fix issues, but they take time.

The initial setup of the solution would be a bit difficult if you are using CI/CD. CI/CD, container integration, and container deployment are one-time processes. Setting them up once makes the rest of the deployment easier. If you don't do it initially, you have to copy and paste, which will take time. I suggest you invest time in creating a CI/CD to avoid the later dependencies or consequences of not using CI/CD.

You will be charged too much if you are unaware of the solution's cost. Initially, when I was doing my development and POCs, one day, I forgot to close the connection or the artifact I created. The next morning, I learned that INR 40,000 had been deducted from my credit card.

Some companies use the solution for monetary benefits. Other companies upgrade their technology to compete with other technologies. In my current organization, everything is working fine, but they must also upgrade their technology. They were not saving money with the tool but had to upgrade themselves in technology.

You should be aware of the solution's configuration. You don't have to write any code, even for your basic work needs. However, you do have to configure some things and be aware of the triggers and actions. There is also a lot of help available on Google and YouTube to do it.

We have to write the code in such a manner that the next person who is using it or visiting that particular code should be aware. If you don't write properly what type of work you are doing inside a particular code, it'll be very difficult to identify what you have done. If I pick one particular action, the action should be very clear about what I'm doing in that action.

Otherwise, it will be very messy. If you use the default naming structure, it will be like one, two, or three variables. If you do not write the proper name of that variable, it'll be very difficult to identify what type of work you were doing inside that scope, function, or action.

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

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.

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. 

What I found most valuable in Microsoft Azure Logic Apps is that you can run a workflow or do a high-level process orchestration, then you can call the other function and fulfill the process. For example, if you want to update a customer, you first need to get the customer's phone number and simulate the steps of the process, then Microsoft Azure Logic Apps can orchestrate that process.

A room for improvement in Microsoft Azure Logic Apps is that it's expensive. Every step is going to cost you money, so if someone is not doing the steps carefully, at the end of the day, it will cost a lot of money. Each time you execute a step, the cost will depend on how much you use Microsoft Azure Logic Apps, and how many workflow steps you have. Each time a step needs to be executed, there'll be a cost added to your bill. If the developer isn't careful with how he uses the solution, this can blow up the cost.

What I'd like to see in the next release of Microsoft Azure Logic Apps is for the cost and security to be better.

My experience with Microsoft Azure Logic Apps is four years.

Microsoft Azure Logic Apps is a stable solution, specifically for process orchestration. From this perspective, its performance is fine.

The support from Microsoft is very good, though my team didn't contact Microsoft specifically about Microsoft Azure Logic Apps, but about other solutions.

The initial setup for Microsoft Azure Logic Apps is easy, and this is why people use it. The turnaround time to set the solution up is short, and the time to get up to speed on how to use it is short.

Though the learning curve for Microsoft Azure Logic Apps is short, you have to keep in mind that you could create an app that costs a lot of money, so you need to be very careful and have a good understanding of what it is before creating it. Otherwise, you could blow up the cost.

Microsoft Azure Logic Apps could be costly if a user isn't careful. The costs associated with the solution could still be improved.

I evaluated AWS Step Functions.

Microsoft Azure Logic Apps is a PaaS application, and as it's in the cloud, there's no concept of versions. In the conventional world, you have a version 9, 10, or 11, for example, but in the cloud, it is a PaaS, and you're using that PaaS.

Between seven to eight developers write the code for Microsoft Azure Logic Apps in my company, but these developers come and go, depending on the project.

My advice to anyone who wants to use Microsoft Azure Logic Apps is to go with AWS Step Functions, for the cost and the security. It's also much easier to implement AWS Step Functions compared to Microsoft Azure Logic Apps. AWS Step Functions costs less when compared to Microsoft Azure Logic Apps.

My rating for Microsoft Azure Logic Apps is seven out of ten. If anyone wants to use it, then no problem.

My company is a Microsoft customer.

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.

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.

We use the product for integration between on-premise and cloud products.

The product’s most valuable feature is integration.

There could be more AI features included in the product.

We have been using Microsoft Azure Logic Apps for three years.

I rate the product’s stability a nine out of ten.

I rate the platform’s scalability a ten out of ten.

Microsoft Azure Logic Apps’s premium support services are excellent.

Positive

The initial setup is easy. I rate the process a ten out of ten. We have a deployment team consisting of four executives. It takes a few hours to complete the process.

The product generates around 10% ROI for us.

It is a cost-efficient platform.

It is an excellent and efficient product. I rate it a nine out of ten.