Ismail Kiswani - PeerSpot reviewer
Manager at Al-kiswani
Real User
Cost-efficient platform with a valuable integration feature
Pros and Cons
  • "The product’s most valuable feature is integration."
  • "There could be more AI features included in the product."

What is our primary use case?

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

What is most valuable?

The product’s most valuable feature is integration.

What needs improvement?

There could be more AI features included in the product.

For how long have I used the solution?

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

Buyer's Guide
Microsoft Azure Logic Apps
May 2024
Learn what your peers think about Microsoft Azure Logic Apps. Get advice and tips from experienced pros sharing their opinions. Updated: May 2024.
771,212 professionals have used our research since 2012.

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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

How are customer service and support?

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

How would you rate customer service and support?

Positive

How was the initial setup?

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.

What was our ROI?

The product generates around 10% ROI for us.

What's my experience with pricing, setup cost, and licensing?

It is a cost-efficient platform.

What other advice do I have?

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

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
Owner & Senior Azure Developer at a tech services company with 1-10 employees
Real User
Top 5
Serverless with good integrations and a relatively easy setup
Pros and Cons
  • "If there's something that isn't possible, you can write some code and call that code from a Logic App."
  • "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."

What is our primary use case?

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.

What is most valuable?

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. 

What needs improvement?

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.

For how long have I used the solution?

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

What do I think about the stability of the solution?

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. 

What do I think about the scalability of the solution?

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

How are customer service and support?

I've never contacted technical support. 

How was the initial setup?

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. 

What was our ROI?

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

What's my experience with pricing, setup cost, and licensing?

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.

What other advice do I have?

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.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Microsoft Azure Logic Apps
May 2024
Learn what your peers think about Microsoft Azure Logic Apps. Get advice and tips from experienced pros sharing their opinions. Updated: May 2024.
771,212 professionals have used our research since 2012.
Aser Murias - PeerSpot reviewer
Director at BI Smart
Real User
Top 10
User-friendly with easy integration with other Azure-based environments
Pros and Cons
  • "Easy to use and is able to integrate with other Azure-based environments."
  • "The solution lacks sufficient connectors."

What is our primary use case?

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. 

What is most valuable?

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

What needs improvement?

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

For how long have I used the solution?

I've been using this solution for two years. 

What do I think about the stability of the solution?

The solution is stable. 

What do I think about the scalability of the solution?

The solution is scalable. 

How are customer service and support?

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

How was the initial setup?

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. 

What's my experience with pricing, setup cost, and licensing?

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

What other advice do I have?

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

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
Sr. Specialist Process at Delphime
Reseller
Top 20
Simple to use but limited for complex applications
Pros and Cons
  • "I would rate my experience with the initial setup a nine out of ten, with ten being easy to set up."
  • "It's for a limited kind of application or short Apps. And, not for the complex applications."

What is our primary use case?

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.

What is most valuable?

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.

What needs improvement?

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

For how long have I used the solution?

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. 

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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.

How are customer service and support?

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

Which solution did I use previously and why did I switch?

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.

How was the initial setup?

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.

What about the implementation team?

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

What's my experience with pricing, setup cost, and licensing?

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. 

What other advice do I have?

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. 

Which deployment model are you using for this solution?

Private Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Microsoft Azure
Disclosure: My company has a business relationship with this vendor other than being a customer:
Flag as inappropriate
PeerSpot user
Head Of DevOps at Kantar
Real User
Enables us to integrate SaaS tool sets
Pros and Cons
  • "Logic Apps is valuable because my team uses it for integrating SaaS tool sets."
  • "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."

What is our primary use case?

We use this solution for integration. It is deployed on cloud.

We have about 50 people using this solution.

What is most valuable?

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

What needs improvement?

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.

For how long have I used the solution?

I have been using this solution for two years.

What do I think about the stability of the solution?

The solution is stable.

What do I think about the scalability of the solution?

It's decently scalable.

How are customer service and support?

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

How was the initial setup?

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

What other advice do I have?

I would rate this solution 7 out of 10.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
Anand-Shah - PeerSpot reviewer
Software Architect at Iskraemeco
Real User
Top 5Leaderboard
A cloud solution for orchestration and workflow with high stability

What is our primary use case?

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

What is most valuable?

The most important feature is integration by email.

What needs improvement?

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

For how long have I used the solution?

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

What do I think about the stability of the solution?

The product is stable.

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

What do I think about the scalability of the solution?

Three users are using this solution in our organization.

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

How are customer service and support?

Customer support is good but takes time to respond.

How would you rate customer service and support?

Positive

How was the initial setup?

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.

What's my experience with pricing, setup cost, and licensing?

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.

What other advice do I have?

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.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
Sambit Kumar Sahu - PeerSpot reviewer
Software Development Engineer at Yovant Labs Pvt. Ltd.
Real User
Top 5
Has good stability and works well for building connectors
Pros and Cons
  • "The product has efficient connectors."
  • "Microsoft Azure Logic Apps could have more customization options for connectors."

What is our primary use case?

We use Microsoft Azure Logic Apps for building an insurance product. We integrate multiple solutions using it.

What is most valuable?

The product has efficient connectors.

What needs improvement?

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

For how long have I used the solution?

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

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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

How are customer service and support?

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

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

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

How was the initial setup?

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.

What's my experience with pricing, setup cost, and licensing?

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

What other advice do I have?

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.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
Contract Software Engineer at Stermedia
Real User
A fast and user-friendly cloud-based platform that's able to create a solution in a matter of hours
Pros and Cons
  • "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."

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

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

What do I think about the scalability of the solution?

Microsoft Azure Logic Apps is scalable.

What's my experience with pricing, setup cost, and licensing?

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.

What other advice do I have?

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.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Download our free Microsoft Azure Logic Apps Report and get advice and tips from experienced pros sharing their opinions.
Updated: May 2024
Buyer's Guide
Download our free Microsoft Azure Logic Apps Report and get advice and tips from experienced pros sharing their opinions.