Microsoft Azure Logic Apps Reviews

For one of the projects that we used, this solution dealt with SharePoint and Power apps. So there, we have to do some kind of connectivity and calculations on the fly. It was related to reading a file and our heavy processing. That was one scenario. There have been a few others as well.

If we are working with a service-oriented architecture, as an architect as a baseline, it supports us very well in terms of expandability, and the kind of robustness it brings, especially with its serverless nature is fabulous. That's not a problem. So that's how we view it. It allows us to focus on a particular functionality within this context, and that's great. 

However, the challenge lies in the fact that it's often difficult for most developers to integrate it into their daily activities seamlessly. That's where it becomes problematic. 

There are two challenges. First, it's a bit costly at the end of the day. It's difficult to calculate pricing, and that affects the business. That's one challenge. 

Second, it's asynchronous. So, getting a development team to work on it, making it function properly, is a challenge. Salespeople often have this new notion of sequential programming, so they don't fully understand how it can be used in a disconnected or asynchronous mode. It's difficult for them. It's challenging. In terms of analytics and navigation, using all these modern architectures, it's there, and it works nicely. But if somebody is using a legacy application or needs to make an extension, then it becomes difficult because those applications don't really support asynchronous processes, especially building applications this way. It's challenging to sell those things.

So, pricing and handling asynchronous processes are the two main areas that need improvement.

The primary challenge is handling the costs, especially the difficulty in providing precise, concrete numbers to the business. This becomes a significant issue because we can't predict what kind of processes will be required. Once you invest, there are various variables in the market, such as manufacturing, and once you get connected, you need a connector, which often comes at an additional premium cost. Every business is sensitive to this aspect. 

Sorting out the licensing is very complex, particularly when using multiple services. For example, if you want to use Power Apps, Logic Apps, SharePoint, and other services, things become complex and confusing. You can't go to the business and provide a clear budget because businesses prefer a specific number they can allocate. However, it's challenging to provide precise, point-to-point cost estimates because there isn't much detailed information available online. The cost estimates are often high-level.

Here is an example. We are building a chatbot, and one part of it is based on the number of requests. We're a company with 7,000 employees. If the chatbot becomes successful, we could have 100 questions or even 20 to 30 interactions per day per user. However, if it's not successful, it might drop down to just 1 to 2 interactions per day from 20 to 30. The cost variation is so significant that it's challenging to present a consistent cost to the business. It could range from ten thousand dollars per month to maybe just one thousand dollars. The range is hard to explain, and in reality, we don't know. And then there are hidden costs. When you try to connect to something, you suddenly realize it's also license-based, user-based, like seven engineers not using it. The price can increase unexpectedly from a couple of hundred dollars to maybe a few thousand dollars per month or even more. This complexity is causing people to avoid using it.

I have been working with Azure Logic Apps for a couple of years. We did a few projects here and there. Normally, for Azure Logic Apps, we worked in patches, with a few clients agreeing to use it for specific functionality. Most of them are related to SharePoint or Office. They're on the cloud directly. But we haven't come across a situation where the entire application is built around Azure Logic or all these modern services, purely Azure. Generally, it's whether Azure databases may be slow. They use Power Apps and SharePoint in the backend, which is the most popular approach. It's a double operation.

The stability is more the way we develop it. It is not a problem with the apps.

It is scalable. I have never seen a situation where there are scalability issues.

We work with enterprise and medium customers.

The customer service and support are very tricky. They will promptly come to help. Most of the time, they are able to help. But if things get complex, it is difficult to get the information from them. Generally, if you have a paid service, they are good.

Neutral

It is a service, so we don’t need to install it.

Deployment is okay once you set up the process correctly. Normally, it doesn't work in isolation. So whenever we update, there will be two or three of these. PowerApp and other things will be updated. The update is okay. It's not a problem. If you have to move between environments, then it's something we need to think about. There's no particular standard for people to have different things, and in some cases, we do have. It can be resolved.  

We used this solution for one or two projects, but it cost a lot. Very expensive.

Overall, I would rate Microsoft Azure Logic Apps an eight out of ten. It is a good product but not the best.

I would advise that you should know how service architecture works. You should know where the service is going to be adjusted in their application. It's not that you'll start putting everything. You need to understand the nature when you go with service architecture. If you don't understand, then there is a problem. 

Otherwise, it is okay. It's a good solution. You may have a few challenges, but it will be okay. It's a nice solution.

Microsoft Azure Logic Apps' main use case is workflow. Depending on your needs, many available connectors allow you to configure it with different systems, whether on-premises or in the cloud. They start with a trigger and then execute steps one by one.  Just as we use features in Excel, the tool can manage different tasks and handle various data formats.

The solution's most valuable feature is the no-code/low-code feature. Due to certain restrictions, we might be unable to use some connectors, particularly if they involve sensitive information like usernames and credentials. In such cases, you could use the library. Then, you can deploy that function app to the same subscription and call it via Microsoft Azure Logic Apps.

Not all connectors are readily available, though. There are two types: managed connectors and app connectors. Some connectors require you to provide a username and password to connect to platforms like SharePoint or Salesforce. Due to security constraints, some users may prefer not to use these connectors. Instead, they might opt for the HTTP connector. However, tracking can be a bit challenging. In production, the run history might not be accessible due to security restrictions.

I have been using the product for a year. 

My company has 100 users. 

The tool's support is helpful and does a great job. 

The tool's deployment is easy and manageable. 

The solution is worth its cost. 

The tool's cost can vary depending on your specific use case. Generally, it's considered cheaper, but the price depends on how much you use it and which features you need. Initially, there was a consumption-based pricing model, but now Microsoft offers a standard tier. Microsoft encourages users to migrate from the consumption model to the standard one by 2025. The pricing is a monthly fixed cost, depending on your usage needs.

If you're trying Microsoft Azure Logic Apps for the first time, begin by learning its basics. Understand how to deploy and use it. Then, some practice projects should be done to see how it works in different situations. Finally, get hands-on experience through the Azure portal to feel more comfortable using it for real projects.

If you have a use case where you need to utilize an Azure function, you can directly call that function from within Microsoft Azure Logic Apps using a connector. This connector allows you to call the function with specific inputs and methods, such as Post or Get. Additionally, certain connectors available exclusively in Azure, like blob-related connectors, offer valuable resources for tasks such as editing or creating blobs. 

I rate the product a ten out of ten. 

Our customers use SAP to create approval requests from their managers, like PO requests and approval and leave requests. Everything is generated from SAP. We pull the information from SAP and send it to the manager on Microsoft Teams. A manager needs to approve it on Teams instead of SAP. The solution builds connectivity between Teams and SAP.

The prebuilt connectors available for SAP are really useful. The solution is easy to use and has a plug-and-play or drag-and-drop concept. We can create connectors easily. We don't have to do too much R&D and write codes to make it work.

The solution could add an AI version to make it easier for people. Microsoft is deploying Copilot across all the platforms like Microsoft 365, Teams, Word, Excel, PowerPoint, and everything. Azure can also add Copilot to the product to make it easier for developers.

I have been working with the product for the last five years. I am using the latest version of the solution. I help Microsoft partners to scale their business in the Middle East, Africa, and Central and Southeast Europe. I run alliances or sales as a service for Microsoft ISVs.

The product is very stable. I rate the solution’s stability a nine out of ten.

The solution has high scalability. Currently, we have 100 users. Eventually, we will scale to 3000 users. We serve all types of clients, particularly medium enterprises. However, the solution can be scaled to any business. I rate the solution’s scalability an eight or nine out of ten.

We are very happy with customer support.

Positive

I have used Power Automate. I used Power Automate in one of our solutions for our customers. It runs in more than 800 stores and has around 20,000 users.

The initial setup is pretty straightforward. I rate the ease of setup an eight or nine out of ten. The product is deployed on the cloud. The setup takes around one month from the testing to production. It also includes the time for the team to get educated about the solution. We were more familiar with Power Automate. We had to do a little bit of reading first to deploy the solution.

To deploy the product, we downloaded a trial version, experimented, looked at the menus, downloaded available resources, joined the community, and sought some help from Microsoft, our technical partners, and development managers. There's a lot of documentation available. We reviewed the documentation too.

The tool’s pricing could be better. I rate the solution’s pricing a four out of ten on a scale where one is low, and ten is the high price. The product is not pricey. It is a pay-per-use model. The more transactions we do, the higher we will be charged. We are charged for the actual transactions.

People considering using the solution should find out their business use case. Some applications are very heavy on transactions. They should be careful about the total number of sessions they will need to purchase. The solution is fantastic if the business use case does not require too many transactions. Overall, I rate the solution a nine out of ten.

We use the product for internal data transfers. It has replaced Data Factory in our organization because of the complexity of the data transfers.

The tool’s biggest benefit is the access we have to other Azure products. We can use all the Azure services directly. I like the product. It is the best choice for use cases involving Azure products.

The visual tool that is used to build integration is quite old. It’s really hard to see all the different models at the same time. It must be modernized, and better support must be provided for the visual tool. The tool must provide support for OpenAPI. We create connectors out of some OpenAPI documentation, but they are really old versions.

I have been using the solution for three years.

The solution is stable. It is as stable as Azure.

The tool is not easily scalable. If we want to run it on a dedicated server, it requires an extra server or virtual machine in the background, which is costly. Two people in our company are using the tool. We rarely need to maintain the solution. We conduct maintenance procedures once every three months.

The technical support could be better. The documentation is not optimum. The documentation training and tutorials are minimal and quite old.

The initial setup took some time. We had to create all the resources in Azure. It was done manually three years ago. We took around one and a half days to set everything up. The solution is cloud-based.

The ROI is really high. Having all the different Azure services integrated directly into the tool is handy.

The product is quite cheap. However, when the use cases get bigger, it gets more costly. We would need to have our own server in the background at some point, which would be very costly. It’s cheap if the use cases are low.

If someone has really good use cases in Azure, they should use Logic Apps to transfer data. Overall, I rate the tool a seven out of ten.

We mostly work with Power Automate, but we do have some experience with Logic Apps. For example, if a user makes a request and we need to process their data, we can easily develop an Azure Logic App for that. 

Sometimes, we combine Power Automate and Logic Apps. For example, a user wants to view specific data and sends a request. We can easily collect that data using Azure, along with a combination of Power Automate and Logic Apps where appropriate. We use Power Automate for external interactions and have it call Logic Apps within our application.

A customer registers on our platform. We perform a lot of validation. We call services from different applications to validate the user's identity, PAN number, and other information against government records. 

We apply a sequence of business logic to validate the customer before registering them for the application.

When we initially built the registration system for our application, we used Power Apps and Power Automate to perform the validation. We call different services through Power Automate to validate the input given by the user.

Currently, we use web services, SQL connectors, and a self-connector. We choose the connector based on where we are getting the data from.

Moreover, the visual design experience wasn't complex. It was easier, as usual. The overall experience is good. The user interface and everything are very intuitive, and we were able to easily consume all those services.

Logic Apps helped reduce complexity or development time. For example, if we get documents in the form of images, we can use Logic Apps to extract information from those images. This simplifies our efforts compared to originally using Microsoft APIs to do the same task.

The only thing is, sometimes, when we need a specific connector, it requires an enterprise or paid version. If it were possible to provide the most commonly used connectors for pulling data from different sources free of cost, that would be really nice.

For every connector, we have to pay. The cost factor is a problem. For every good connector, we're paying twice – once for the SQL Server connector and again for other data source connectors. It would be concerning if I had to pay for every connector I need. Microsoft can do something about that.

I have been using it for two years. 

It's stable if the deployed application has proper resources.

We can scale the application as and when required. There are ways to scale when there are more rules. From a scalability point of view, it's easy to configure, and we can scale the application as needed.

We have around more than 1000 end users. We have several applications working together. During each process, we pull data from different applications, and those are very well integrated with both Azure services and Power Automate. We've also been using UiPath for certain operations.

So, Logic Apps support our needs for scaling workflows or applications.

The customer service and support are good. 

The initial setup is not complex. It was intuitive and straightforward. 

The deployment process is pretty straightforward. We just publish it, and it's easy, similar to how our Power Apps applications are deployed to production.

Deployment doesn't require many resources. We had a DevOps team taking care of it. We have 15+ taking care of it who collaborated with the development team to take care of it. 

It is worth it to use it. The product does a good job. 

For cloud, Logic Apps are good. I would rate it an eight out of ten. 

I always encourage people to use Logic Apps if the environment with Azure native because the development time is drastically reduced. 

Therefore, I always encourage people to explore Power Apps and Power Automate instead of going with native mobile application development or React Native application development.

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.

At our company, we validate certain configurations of the Microsoft Azure Logic Apps based on the security posture and some other factors. We check how Microsoft Azure Logic Apps are deployed and whether the configuration of the solution is appropriate as per the customer needs of our organization. At our company, we also check if Microsoft Azure Logic Apps are being configured as per the standard policies. 

Our organization oversees the architecture and provides consultation on whether the configuration of Microsoft Azure Logic Apps is correct and what changes or updates are needed. The use cases of Microsoft Azure Logic Apps depend upon the application design. In our company, we overview the architecture and check the functionality. Our organization checks whether the configurations and settings of the apps using Microsoft Azure Logic Apps are properly designed or not. 

For instance, suppose there is a Logic App that is used in one of the applications, and there is a diagnostic setting. For the aforementioned app, at our company, we need to check whether the workflow, runtime and diagnostic events are logged properly. As part of the app properties, our company often check whether a connection stream is being used and whether it's summoned by the Azure Key Vault or not. 

The Logic App's designer is one of the vital features of Microsoft Azure Logic Apps. The workflows and API connections are quite systematic using the solution, and designs can be easily implemented. The Logic App's designer is automated and easy to use. 

The product should integrate more APIs for embedding the overall solution with Azure functions. The API connections with different cloud versions should be easier to use. 

I have been using Microsoft Azure Logic Apps for a couple of years. 

I would rate the stability a nine out of ten. Stability-wise, our company hasn't faced any issues with the solution. 

I would rate the scalability a nine out of ten. The solution is highly scalable. In our company, as architects, we believe all cloud environments should be flexible and scalable, like Microsoft Azure Logic Apps, so that the product can be scaled up or down according to varying projects and cost factors. 

There are numerous internal and external users of the solution in our organization. In our company most of the customers for Microsoft Azure Logic Apps are enterprise businesses. 

Microsoft Azure Logic Apps has numerous useful documents and a resourceful knowledge base from Microsoft. In our company, we have solved multiple issues by only using the documentation from the product's vendor. 

I would rate the initial setup a seven out of ten. At our company, we deploy the solution, both on-prem and on the cloud, for internal and external customers based on the project and requirements. UAT and fine-tuning might be needed as part of the deployment process of Microsoft Azure Logic Apps; the complete deployment takes around five to ten working days. 

For deployment, a concept-building initiative is first taken to understand the client's requirement, and then the designing step arrives to decide where the logic app fits in and identify its purpose.

After the aforementioned deployment steps, the deployment phase arrives, during which the product can be tested with dummy datasets. The UAT is then performed in the staging environment, and once the architects feel confident about the solution, the UAT setup is moved to production.  

I would rate the pricing a six out of ten. 

The Logic App's designer feature of the solution assists you in implementing a workflow effortlessly. The designer feature allows a drag-and-drop interface with easy function creation to implement a workflow. At our company review, architects go through the workflows to obtain a fair idea of the app's parameters, including what is being called or how it's called and the data fetching or sending details. 

I would rate Microsoft Azure Logic Apps as eight out of ten. While automation is prevailing across the globe with the advent of AI, Microsoft Azure Logic Apps can help maintain security and efficiency. Overall, the product is fast, safe and reliable, with security controls and flexibility.

We never deter our organization's customers from using Microsoft Azure Logic Apps due to its efficiency. I would definitely recommend the product to other users. In approximately eight out of ten projects in our organization, Microsoft Azure Logic Apps are used. 

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.