Microsoft Azure Logic Apps Reviews

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. 

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. 

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.

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.

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.

We use the solution to integrate other systems like SAP and Salesforce for orchestration and the API. We also use it to automate business processing and balancing workflows.

The solution integrates customer CRM data with various systems. It offers a user-friendly interface, making integration tasks straightforward and efficient.

The design is highly beneficial. It functions as a sandbox environment.

The pricing could be improved.

I have been using Microsoft Azure Logic Apps for five to ten years.

The product is very stable.

The solution is scalable.

The technical support is good. Documentation is also very good.

The initial setup is straightforward. Also, the learning curve is easy.

Microsoft Azure Logic Apps has a straightforward nature. The process is much simpler. This design is designed for seamless integration, making Logic Apps the preferred choice.

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

The use case depends on the situation. 

We primarily use this solution to schedule time-based event triggers.

Sometimes, we use it for the simple starting of machines or automating the start of certain machines. It can be set up on a timer or some sort of time-based event trigger that we need to schedule, and the trigger is set up for certain logic.

I like the ability within Logic Apps to design the workbooks through the portal with minimal code.

I would like the ability to add more features or to become more of a designer first or to be a declarative type of environment. 

Doing more with Logic Apps through the portal with less code or less script being written would be ideal.

It would be beneficial to have less code and tighter integration between different cloud services.

I have been dealing with Microsoft Azure Logic Apps for two years.

It's a very stable solution. We don't face many issues. It is very rare to have issues with the other platforms themselves.

Microsoft Azure Logic Apps is very scalable. It's extremely scalable.

My experience may be different, or not be common. I have had wonderful experiences with the technical support team recently. I am very happy. I may be one of the few that is a very happy customer in that area.

I have used Microsoft Azure File Storage, Web Apps, compute for virtual machines, and networking components. I have not used Azure search recently.

I have also used Firewall Manager, recently, but I wouldn't say that I have a lot of hands-on experience.

The initial setup was very easy.

I completed the setup myself. It is what I do.

Pricing is relative.

If we are comparing to other public cloud vendors, such as Amazon or Google Cloud platform, I wouldn't say that it's expensive. However, when we're comparing between a host such as GoDaddy or Digital Ocean, then it's a bit on the expensive side.

Definitely, I would recommend it. Make sure that what you need can be done through Logic apps and not other alternatives, or not with other functions, and not with any other alternative system. 

You need to do the research and learn about the limitations or know what Logic Apps is designed for to ensure that it fits the use case that they're trying to do.

This applies to all the services. At least properly plan or read about the service before going all-in and trying to have Logic Apps deliver something that's not meant to deliver.

In summary, this is a good product but tThere is always room for improvement.

I would rate Microsoft Azure Logic Apps an eight out of ten.