Microsoft Azure Logic Apps Reviews

I am a monitoring engineer and primarily use Logic Apps as part of the monitoring integration project. It is leveraged for orchestrating different tasks and recognizing Azure Monitor alerts to build data pipelines.

Microsoft Azure Logic Apps has saved us a significant amount of time and is straightforward to use due to its excellent documentation.

Its notable advantage is its user-friendly UI, which allows easy testing. It is cloud-agnostic and aids data engineers by facilitating the creation of data pipelines, including AI-related ones. The built-in connector feature is also valuable, enabling integration with services like Teams and email notifications.

The OpenAI components in Logic Apps could be more understandable, especially in training data or handling Azure Monitor alerts more simplistically, enhancing interpretability.

I have been using Logic Apps for one year.

Logic Apps is stable and reliable.

Logic Apps is easily scalable due to its use of the application service's auto-scaling capabilities.

I haven't had direct contact with Microsoft customer support as another colleague manages our support interactions.

Positive

Before Logic Apps, I worked with other cloud services like AWS and Azure Cloud for monitoring purposes.

The installation of Logic Apps is straightforward and easy, requiring minimum personnel effort.

Just one person is sufficient to handle the installation of Logic Apps.

Logic Apps offers around 30% savings in terms of cost and time, enhancing development flexibility.

Logic Apps is free to use, though there may be costs associated with additional data storage or overuse of emails, which could require additional services.

Previously, I worked with OpenShift in an on-premises environment and Azure Cloud services.

I'd rate the solution eight 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.

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.

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.

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 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. 

I've got a few use cases.

I have one use case where I read emails from an inbox, and then I process files in the attachments of that email.

I also read from a database on-premise with an on-premise integration. I'm not sure what it's called, however, it was really easy to set up, and I could access the on-premise database in my Azure Cloud and then talk to the Logic App from my Azure web application. 

There's another use case where I read from a database and create a file in a file storage account.

It is incredibly easy to use. You open it, and it's just like a designer. It asks: "Well, what step would you want to take?"

There are good integrations available. 

If there's something that isn't possible, you can write some code and call that code from a Logic App.

It is stable. 

It has a lot of integrations, which are quite easy to understand mostly. However, especially when using a function or a parameter, that could be easier as that's not very well-documented, and it's not very clear from the tool itself how to use it. When using parameters or functions, it gets a bit tricky.

I've used the solution in the last 12 months. 

For the most part, it's pretty stable. If I do have some problems with an integration, that sometimes fails me. The stability there kind of depends on the step of the integration, however, Logic Apps itself is very stable. I'd rate the stability at an eight or nine out of ten. 

Nobody else in my organization is using the solution at the moment.

I've never contacted technical support. 

How easy or hard the setup is depends on if you already have already an Azure account or not. If you do, it's very easy as it's simply creating a Logic App, and it's using it. It couldn't be easier. If you don't have an Azure account, it's a bit more complicated and is more like setting up an Azure account, which is complicated.

In terms of actual deployment time to get something up and running, you just build it, and it's running, so it is very fast. 

Typically, it is worth the money to adopt the solution. Even if it gets expensive, it's still worth it.

The solution is  serverless, so you only pay for what you use. It could be the case that the first 10,000 or so instances are free, so you only pay if you use it a lot. Then, if you do use it a lot, yeah, well, it depends on your use. If you're processing large files, and you're doing a million a day, you are going to pay quite a lot. If you are processing a hundred emails a month, you are paying nothing.

I'm an end-user.

I've been using the latest version of the solution.

We chose the product as it was easy to connect to on-premise services, especially an on-premise SQL database, which is pretty easy using Logic Apps.

Companies should probably use it if they have the use case. It's an easy and cheap way to integrate with some on-premise services. Other ways are ultimately maybe easier, yet they are often very difficult to set up and a lot more expensive.

I'd rate the solution nine out of ten. If you are a bit tech-savvy, you can just use it. It can do a lot, and it can do it easily.