Microsoft Azure Logic Apps Reviews

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.

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 use Microsoft Azure Logic Apps for building an insurance product. We integrate multiple solutions using it.

The product has efficient connectors.

Microsoft Azure Logic Apps could have more customization options for connectors.

We have been using Microsoft Azure Logic Apps for nine months.

I rate the product's stability a ten out of ten.

We have more than 50 Microsoft Azure Logic Apps users in our organization. I rate its scalability an eight.

The technical support team's response time could be faster.

Positive

We are using MuleSoft. The connectors need improvement. Also, its deployment process is lengthy for building applications compared to Logic Apps.

The initial setup is straightforward. I rate the process a nine out of ten. It takes around 25 to 30 minutes to complete. It requires four executives for implementation.

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

I rate Microsoft Azure Logic Apps a nine out of ten. It works well for deployment and building connectors. It allows us to connect interfaces of two different platforms easily in a graphical way rather than using coding.

Our use case of Azure Logic Apps is for the integration of data coming from different sources to the manager. We are Microsoft partners and I'm the company director. 

I like the connectivity, that it's easy to use and has the capabilities to be able to integrate with other Azure-based environments.

I'd like to see more connectors available as well as a more advanced development environment.

I've been using this solution for two years. 

The solution is stable. 

The solution is scalable. 

We are a Microsoft partner so we have good support although we haven't used it for this product. 

The initial setup is relatively straightforward and takes a couple of hours. As a consultancy company providing this product to our customers, we carried out our own in-house deployment. We're currently implementing this solution for six of our customers. The deployment requires an architect and one or two others. 

Licensing costs are paid monthly or annually and I believe they are reasonable. The cost is dependent on the connectors. 

I recommend this solution and rate it eight out of 10. 

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 this solution for integration. It is deployed on cloud.

We have about 50 people using this solution.

Logic Apps is valuable because my team uses it for integrating SaaS tool sets.

It's a skill that must be learned. I find the current interface useful, but I could see how others would want the UI bits that are used for creating Logic Apps to be simplified.

I have been using this solution for two years.

The solution is stable.

It's decently scalable.

We have never had to use technical support. The solution is straightforward and documentation is decent.

Initial setup was straightforward. Maintenance is done in-house.

I would rate this solution 7 out of 10.

We use the solution for orchestration and workflow to execute all the processes manually.

The most important feature is integration by email.

The solution can integrate with different ETL tools. It can integrate with Azure Data Factory and a more open connecter.

I have been using Microsoft Azure Logic Apps for two years.

The product is stable.

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

Three users are using this solution in our organization.

I rate the solution’s scalability a nine out of ten.

Customer support is good but takes time to respond.

Positive

The initial setup can be done within an hour.

I rate the initial setup an eight out of ten, where one is difficult and ten is easy.

The product is expensive. It has a pay-as-go model. If the consumption is high, it will cost more. The billing depends on consumption.

Logic Apps is a low-code development. One can easily do the development and save the workflow. It is user-friendly, offering different connectivity with different services. It should be leveraged as much as possible.

Overall, I rate the solution an eight out of ten.

It's very easy to use, and it's blazing fast. The best thing about Logic Apps is actually its ability to create a solution in a matter of hours. It doesn't need any kind of provisioning, and you don't need any kind of hardware. You can create very small elements like these Logic Apps, and you can build a whole solution from those very simple and small elements.

I also like that they are completely incorporated with your existing active directory. You can use user groups directly from the active directory inside Azure and access it from the Logic Apps.

You don't need to do anything special, and you just have access. You can just check if the user is, for example, allowed to do some action. Normally it would take you some additional steps and some additional calls to check it. You have to come back to the active directory to make this possible. In Logic Apps, you just have it, and you can use it. 

I think that there's this concept of logging and recall to the Logic App. It shows you every single step, every single product, and the result it's returning to the next step. It also has an amazing debugging feature. 

You can rerun some calls and see if, after a correction of the Logic App, for example, you get the correct results. So, it's almost like it's alive. It's like you make a change, poof it, and it's in production, and it's working. The speed of the composition of the problem and creating a real solution for it is extremely fast with this solution. It's extremely fast in creation.

The documentation could be better. I think that's the only thing that was causing a normal level of problems. In terms of the documentation, it came from Cosmos DB and an additional product from Microsoft Azure.

I have been using Microsoft Azure Logic Apps for more than a year.

Microsoft Azure Logic Apps is scalable.

It's very cheap, but it comes with pluses and minuses. The positive thing is that it's very cheap, but on the other hand, it's extremely hard to tell how much it will cost.

At the start of the project, it's almost impossible to tell how many times you will be calling some kind of Logic App function. You cannot state how much of the internet transfer you will use or how much data your will use.

We're developing our solutions on three elements. One element is Logic Apps, and it represents our functionalities. The second element is Cosmos DB, which is the database and the persistence for our solutions. The third element is the storage account. Inside the storage account, you have a special folder called Web. You can put it inside this folder. You can put any single-page application, like Angular.

In the Angular application, you have hosting of that application and application files for free. So, we put an Angular single-page application into this storage account, which is calling Logic Apps, for the functionalities and endpoints.

In the backend, we had the Cosmos DB, which is the database for the whole thing. You can add elements from the outside to connect the customer's data center to Azure and this application you have made. Azure doesn't even have to know or have access to customer systems. 

In the end, you have a very scalable solution without the high risk of someone breaking it, and he will just know the data inside it. But he would not gain any access to the customer data center.  

On a scale from one to ten, I would give Microsoft Azure Logic Apps a nine.