Microsoft Azure Logic Apps Reviews

The primary use case for Microsoft Azure Logic Apps in my system is mainly API Gateway; it serves as an interface between the external world and our entire ERP landscape. Any request which flows in our environment or goes outside from our environment touches the API Gateway. It handles transformation, request creation, transformation of the payloads, request payloads, and asynchronous flows, along with topics or message queues, which are the tools we utilize for asynchronous flows.

Assessing the ease of connecting disparate systems using Microsoft Azure Logic Apps connectors is simple because we have a Standard Operating Process. If we want to use Logic Apps, we just reserve the instances as per our requirement.

Even for Blob storage, we use tokenized endpoints that give us access to this storage account, making it secure. At API Gateway, we have policies that help us implement encryption and decryption. Request parameters are mapped automatically, converted to SOAP, XML, or JSON as needed in different formats.

We utilize its monitoring capabilities; Event Grids are used for logging events. Additionally, we have implemented a retry mechanism and are using Azure Monitor for end-to-end request tracing.

My experience with their pricing indicates that pricing is complicated to understand and costly. There should be some cost reduction.

Currently, I don't have any use case beyond what the readily available adapters provide for generating email or connecting with a backend database. Those facilities are readily available, and my requirement is just that much.

Our organization is utilizing that platform, and I am a customer.

I have been working with Microsoft Azure Logic Apps for more than three years.

I am not working with other IBM products; previously, I worked on IBM API Gateway. Instead, we switched to Azure Integration Services, AIS.

I am using it myself as I am a technical architect, so I have my team. We guide them to use the components as per the requirement, and then they develop the software or the integrations, whatever is needed.

I am working with an application infrastructure now, specifically Business Process Management. We don't have BPM, and we don't have any requirement for BPM currently.

My experience with Microsoft Azure products is great; they have many tools that support synchronous and asynchronous calls. We have a hybrid setup, with some things on cloud and the rest on our own infrastructure, so it helps us to implement the solutions as per our requirement.

I am mostly working with Microsoft Azure products such as API Gateway, Logic Apps, and then storage, specifically Blob storage. I use Logic Apps for collaboration through Azure DevOps, which helps us to automate the deployments.

At the infrastructure level, we typically monitor metrics using alerts for server monitoring. If a request is getting failed, we are monitoring based on error codes. We utilize error codes to write the logic for the retry mechanism.

We have a basis requirement for how Microsoft Azure Logic Apps integration with Office 365 has enhanced our business processes. For example, if some keys expire, we implement the Azure Key Vault. We use Logic Apps to trigger messages to regenerate the key or any public certificate close to expiring, which we have stored in Key Vault or other static parameters as per security guidelines. We configure those triggers or system-level alerts, and Logic Apps triggers the mail because it has a ready adapter for Office 365, ensuring the concerned L1 and L2 teams receive the necessary notifications to handle the errors.

On a scale of 1-10, I rate Microsoft Azure Logic Apps a seven out of ten.

We develop and sell Microsoft Azure Logic Apps, so we are users of this solution.

The main use cases for Microsoft Azure Logic Apps are workflow management, some part of orchestration, and integration along with Service Bus.

The ROI with Microsoft Azure Logic Apps comes from the business process automation, and my customers have measured the value they get from the product.

The actions and Visual Designer in Microsoft Azure Logic Apps reduce the development time the most.

The most useful features of Microsoft Azure Logic Apps are the workflow part and the orchestration of services.

Scalability and reliability are benefits in Microsoft Azure Logic Apps.

The biggest advantage of Microsoft Azure Logic Apps is the workflow automation. Workflow automation and no-code, low-code development are its key benefits.

State management is the main challenge I have faced with Microsoft Azure Logic Apps during this period of time.

The issues I am facing with state management in Microsoft Azure Logic Apps arise because when you work with a state management tool elsewhere, such as a state machine, it is not easy to develop a state machine on Microsoft Azure Logic Apps. Though people say it can be developed, the state machine kind of requirement cannot be developed exactly with Microsoft Azure Logic Apps. It's an alternate tool. It's not the tool to be used for state management and state machines.

Better debugging capabilities within Microsoft Azure Logic Apps could be improved or additional features could be added.

Terraform template support should be available for Microsoft Azure Logic Apps.

For the last three to four years, I have been working with Microsoft Azure Logic Apps.

For a simple requirement regarding Microsoft Azure Logic Apps, deployment takes around three to four days. It majorly depends on the amount of complexity involved there.

Stability-wise, Microsoft Azure Logic Apps is not a problem. It's quite stable.

Premium support is available for Microsoft Azure Logic Apps. The normal support window doesn't help, as it requires premium support.

I would rate the support for Microsoft Azure Logic Apps a seven out of ten when using premium support.

Positive

The setup complexity for Microsoft Azure Logic Apps is medium.

On a scale from one to ten, where ten means a very easy setup, I would rate it a six for Microsoft Azure Logic Apps.

That depends significantly for Microsoft Azure Logic Apps. You can't generalize it because it depends on how many connectors you use, how many workflows you build, what scalability is required, and the amount of data to be ingested. There are many factors that affect the ROI.

Regarding the cost, I find Microsoft Azure Logic Apps to be reasonable; it is not expensive.

I recommend Microsoft Azure Logic Apps to those people who are planning to use it.

We are exploring AI-based applications with Microsoft Azure Logic Apps, though we have not implemented any currently.

I would recommend Microsoft Azure Logic Apps because it is a mature product. Though it has some limitations, it is stable and has evolved over the last 10 years. It's very much scalable and reliable.

In terms of industries, my customers include manufacturing, CPG, and retail when using Microsoft Azure Logic Apps.

The customers for Microsoft Azure Logic Apps are enterprise businesses.

On a scale of 1-10, this solution receives a rating of 7.

Positive

Microsoft Azure Logic Apps is an integration platform used for enterprise application integration and building APIs.

Azure Logic Apps has influenced cost savings by approximately seventy to eighty percent in many cases and is generally 30% to 40% cheaper than any comparable services in this space.

The workflow in Logic Apps enables integrating multiple applications. There are many connectors that help easily connect to all those systems.

The business rules engine is still not fully developed, and it would be very helpful to see improvements here.

I have around ten to twelve years of experience working with this solution.

The stability is high. I would rate it a ten. I have never seen it misperforming.

It is quite easy to scale. It's just clicks away, and you can also set it up as auto-scaling, so you don't have to worry about that.

It is easy to reach out to Microsoft for support if needed, so I would give customer service a rating of ten.

Positive

I have worked on multiple platforms in this space, like MuleSoft, Oracle, Intel, Microsoft, and Dell Boomi. However, Azure Logic Apps is the easiest and most transparent in terms of its operations, licensing cost, and scaling. Being in Azure, the use of the Azure ecosystem becomes quite native with Logic Apps.

The initial setup is very easy. It is one of the easiest to onboard and start working on.

The pricing is very clean and transparent. You can start small and pay only for what you use. There are no upfront licensing costs or contracts you are bound to.

I recommend Azure Logic Apps because it is the easiest and most transparent platform I have worked on in this space. The licensing cost, scaling, and integration within the Azure ecosystem are automated and easy.

I'd rate the solution nine out of ten.

We host our application in Azure App Services and use Logic Apps to monitor everything within. We can schedule or trigger emails in case of any failures.

Every company needs their live transaction data in digital format. We never directly interact with the live database, regardless of the company's domain. Instead, we take snapshots of the live database, which act as separate reporting databases. It's a separate database; we call it a reporting database.

Once the data is within the reporting database, we do massaging by combining more than one table and some information to make it a beautifully presented or required report. A job is needed to do all this kind of activity. So, as a program, what we do is build a program and keep it simple. It's a console-based application at the option. Someone has to trigger that between month-end or during month-end or late at night, non-office hours, non-business hours, maybe in between.

In Logic Apps, what we do is have these kinds of applications as an EXE to be triggered at a particular point in time, period of time. Then, the final output, we want to drive it to the next level, to the block storage. So, in the storage block, we have another Logic App. It's like a chain of Logic Apps. We can train multiple applications. Once the final output is successfully maintained in another location or block storage, we use Logic Apps to trigger the application in general.

I deal with all the projects built under the .NET and .NET Core frameworks. I think Logic Apps is good for helping us run our access on a cloud environment like Azure. It's much easier, more reliable, and better to maintain. 

If the server is shut down, the app may not trigger, but Azure Logic runs in a cloud environment. So there's no point where the server is down. Even if there is downtime, we have high availability, like 99.999%. 

So, in a fraction of a second, our server can be brought up, and the Logic App can trigger and run. The failure rate of Logic Apps is very low, and the success rate is high.

Supports complex workflows:

It runs behind Azure services, on top of Azure. We have our tenant as a domain under our project subscription. Based on our license and overall requests, Logic Apps provides the best performance. You can have single or multi-chain trigger points within one Logic App function. You can also have nested ones. For example, if job one succeeds, it goes to job two; if not, it goes to job three. You can do this kind of conditional execution based on the success rate.

Keeping up with AI:

Currently, AI mostly plays with data, such as Cosmos DB and Azure Integration Apps. When a customer wants to fetch information out of this data, we can implement AI on the database side. Logic Apps are more for in-house requirements, like generating jobs, presenting jobs, generating reports, saving information into databases, or saving information into block storage. It's a triggering point where manual intervention is not required every time; a one-time configuration is enough.

One of the key features is the on-premise service, which we call a scheduler or task manager. However, Logic Apps is not just on-premise. It's capable of triggering Azure Functions, which are purely serverless actions. 

For example, if you want to monitor partition consumption in gigabytes without manually going to the Azure portal and selecting the partition view, Logic Apps simplifies this process. You can easily get Azure metrics information and store it somewhere. So, you can automate many tasks using Logic Apps. It's a part of Azure, and we use it mainly to automate our daily tasks and trigger large processes.

Integration capabilities of Azure Logic Apps:

To trigger apps with Logic Apps, you need to know either Python or .NET Core. There are limitations since it's designed and maintained by Microsoft. You must use Microsoft apps to ensure the EXE runtime is automatically managed by Logic Apps. There are boundaries we have to follow to make the Logic event successful. Since it's a Microsoft product, the EXE should be within the Microsoft environment. Python works fine as well.

When Logic Apps triggers something, the runtime must be supported by Azure App Services. If you want to run an EXE built with .NET, it will work. However, if it's built with Java, it won't know how to run it. You need to inform it that the runtime is different from Microsoft. I've mainly used Microsoft services to run Logic Apps, and it works well.  

In Logic Apps, it supports AJAX and jQuery as commands to filter out to input the parameter. But regular expressions in general aren't supported well. So, I recommend that Logic Apps could be enhanced by supporting regular expressions (RegEx) more comprehensively . That would be a great improvement.

RegEx expressions are useful when running an EXE, and you must provide parameters, like running it for June 2024. You need to feed some information to Logic Apps. I want to tell the program to take the current month and year. For that, you need to use date functions. Using regular expressions in general is also possible by manipulating strings, which is currently missing.

I have been using it for one year. 

It is a stable product. I would rate the stability a nine out of ten. 

It is a scalable product. I would rate it a nine out of ten. 

Because it's Microsoft support, when we raise a ticket, it will take a week or a couple of weeks to get back to us. So they are normally busy.

We have experts supporting our Azure services to make it better. If we badly need Microsoft, then we rely on Microsoft and raise a ticket. We know that it's going to take much time for them to get back, at least two to three days. 

And then, from there, it will take a week to get the solution, either successfully or to determine if what we are trying to do is not workable. The turnaround time is very high.

The main issue is with the time. So, the support could be faster. There are many people opting for new cloud services, so the support from them to the customer is always low.

Neutral

I have also used Cosmos DB and Azure Synapse Analytical Database.

One should have an awareness of the Azure portal. Then, the user will find it very easy to use Logic Apps.

I would rate my experience with the initial setup a nine out of ten, with ten being very easy. Because we need to have some knowledge for regular expressions. Otherwise, it can be done easily.

Deployment time:

It does not take a long time to deploy. Only the task you want to achieve needs to be made as an EXE, and that takes time. But configuring it into a Logic App to run based on the given timeline is very easy. It's a one-time configuration. You must have Azure privileges. If not, you won't be able to at least create or trigger the Logic Apps. You must have the privilege.

The licensing is cheaper because, compared to other services, Azure services are much cheaper and affordable. Any medium to large-scale company can easily afford them. They can scale up and scale down as needed. The charges incurred by Microsoft are within a limit that companies can afford.

If there is a repeated manual job or visiting a portal, downloading something, or manually doing something within the Azure apps, I would recommend using Logic Apps to automate it. It will make lives easier.

Overall, I would rate it a ten out of ten. 

I use the solution in my company as a part of the centralized landscape where we have it for the internal connectivity before any traffic comes in, so we use it for a safe API management gateway. Microsoft Azure Logic Apps is the main tool for API management. It is used to manage our main workflow.

The reason for using the tool is that our company has not restricted itself to one tool. We have an integration board that decides based on the use cases because we have multiple technologies. Earlier, MuleSoft was used, and now we have Azure and OpenText, depending on the use case. If the use case involves file mover, then we move that piece of integration to file mover part. If there are any workflows or any processing required, any business logic is involved, and if there is any real-time stuff involved, then we go for Microsoft Azure Logic Apps. If there is a batch processing part, we go for real-time services again within Microsoft.

In MuleSoft, some set views help in transformation, which is very user-friendly and easy to use. In Microsoft Azure Logic Apps, we use Liquid templates, and I feel it can be improved as it does not support all the features that our company wants to use during any complex mapping when we might have to go for custom coding.

I have been using the tool for a year.

It is a stable solution. Stability-wise, I rate the solution a nine out of ten.

Depending on the kind of scalability that my company wants, I would say that that product supports any kind of scalability feature. Scalability-wise, I rate the solution a nine out of ten.

There are more than 50 end users or developers of the tool.

There are some delays in response from the solution's technical support. I rate the technical support an eight out of ten.

Positive

From a development point of view, MuleSoft is good, but from what I know I would say that it is costly. MuleSoft is pretty much easier for new developers to onboard because you can quickly learn and start using it. In Microsoft Azure Logic Apps, there is not much need for any grooming if someone wants to efficiently work on the tool.

The product's initial setup phase is something that I don't think is complex because once we start using it, it becomes simple. If the user, our developer, is doing it for the first time, then he or she might need to understand the architecture in terms of closing and those things. Otherwise, it is simple. We have two types of deployments there, containers and no servers thing, where we have an App Service plan similar to the vCores concept we have in MuleSoft.

The solution is deployed on the cloud.

Compared to the prices of Mulesoft, the price of Microsoft Azure Logic Apps is low.

I am not much aware of the infrastructure part because I am from the development side. The other team has taken care of the infrastructure part.

Right now, as I said, we are into Azure Integration Services, so we use services like Logic Apps, Azure Functions, and Service Bus for messaging. Different services are used for different purposes depending on different use cases.

Microsoft Azure Logic Apps is quite similar to NetApp. It does most of the functionality in terms of process transformations and connectors or where we connect to the end systems. We have all out-of-the-box connectors to connect to any system, like SAP or whichever systems are available.

Critical functions of the tool are associated with the workflow area. The tool helps in fulfilling our company's requirements.

There is AI available for the tool, but I haven't used the solution.

Under some conditions, we can recommend the tool to other users or if someone wants to upgrade from an existing Microsoft legacy migration to App Logic since we can reuse much of the functionality of the other tool in it. I would recommend the tool to others. If you are starting from scratch, then we can go with MuleSoft, provided some other factors are good.

I rate the tool an eight out of ten.

Azure comes into the picture when the client is already using Azure and they are migrating PeopleSoft to the Oracle XCM Cloud. They wanted to utilize the existing system, as they already have Azure as a middleware. Thus, they preferred to continue with Azure rather than adopt another platform. In this scenario, we used Azure Logic Apps to transform their requests and facilitate the interaction within their cloud journey from PeopleSoft to Oracle and vice versa. 

We employed Azure Logic Apps as middleware since the client was already utilizing Azure for various platforms. We used Azure Logic Apps for integration purposes, including calling REST services, short services, transferring DB calls, and handling data load into tables based on the design. Most of our clients are already using Azure, and they tend to choose it for cost considerations as they already have licensing for Azure or AWS. So we seek solutions that can be cost-effective while integrating with other SaaS services like Oracle SaaS. That's how we handle integration in such scenarios.

There are many good features of Microsoft Azure Logic Apps, and that's why customers are using it. For instance, we have SaaS event processing, timer-based processing, data ingestion, and business process automation. 

Another essential feature is ISE (Integration Service Environment) for content-based routing, data transformation, and enrichment. These capabilities address various business use cases effectively. Azure Logic Apps provide the functionality required to achieve these scenarios.

In terms of improvement, it would be helpful to have more descriptive documentation. Since we work in a hybrid cloud model with Azure, AWS, and Oracle, there are instances where we need to interact between different platforms, like Oracle to AWS features, Oracle to Azure, or Azure to Oracle. In such cases, the information available is often limited, and we need to refer to different documentation sources like Azure's API documents or others. 

It would be beneficial to have scenario-based documentation that helps us understand the integration process more easily. For example, one of my team members had to work on integrating with Azure Blob for data storage. We had to call the Azure REST APIs for that, but the documentation was not clear, making it a bit complicated. We tried multiple REST services, performed trial and error, and eventually got it working. However, having a proper and detailed explanation document would have made it much smoother. Instead of providing everything in one place, having some standard use case documents would be helpful.

I have been working with it for around three years.

The solution is stable. Its stability depends on Azure's cloud services. Our cloud solution is stable. However, the stability of specific scenarios and solutions provided to the client depends on the architecture design. 

From an application point of view, as a cloud service provider, it is stable. To achieve the goals and requirements, it mostly depends on the design of the architect who is working on the solution. The solution's stability relies on the solution architect's design.

It is a scalable solution. It is not difficult to scale. We have worked with good-sized companies, including large enterprises. Some of our reputed customers are from the US and UK.

The customer service and support are good. But everything has its limitations. For example, being more responsive and providing clearer documentation would be helpful. Standard documents are fine, but in certain situations, when facing specific errors or issues, partners or consumers expect customized solutions rather than just links to existing documents. 

If a customer encounters an error while using the cloud services and developing something for their client, they would prefer tailored solutions to resolve it rather than generic URLs to past documents. This is a challenge for all cloud service providers, including Azure, AWS, and Oracle. Improving in these areas would be beneficial and greatly help the users.

Positive

The initial setup is easy. Generally, most cloud platforms provide easy installations. The cloud service provider itself takes care of most of the tasks. It's not challenging.

Deployment does not take much time. It can be done within hours. For deployment, one to two persons are enough. It depends on the number of integrations and the complexity of the plan. 

However, deployment is not a one-go task. We don't deploy 80 applications at once. It's done in a concurrent manner. We develop one, go through testing and business testing, and then migrate it to production. So, on average, one to two persons are sufficient for deployment. 

For maintenance, on average, if we have ten applications running with ten integrations in the environment, we generally follow the 30:1 rule for monitoring purposes. Maintenance is again conditional, depending on the number of integrations, changes, tasks, deployment time, SLAs, and other factors. But for monitoring, one person can handle monitoring of around thirty integrations.

The pricing is not expensive. I would say it's quite reasonable and average. It's on a yearly basis. Our client has a yearly licensing.

If you are using Oracle SaaS, it's a good decision to use Oracle Integration Cloud (Oracle Pass) for better compatibility. Otherwise, other platforms like Azure Logic Apps can also be used. But when it comes to Oracle-to-Oracle interactions, it's easier and more convenient since it's the same vendor-to-vendor interaction, ensuring security and responsiveness.

Microsoft Azure Logic Apps is a good solution. It's easy to use, and it's stable. It's not very challenging. If you prefer programming over drag-and-drop solutions, then Azure Logic Apps would be a suitable option for you.

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

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.

I use the solution in my company for some of our internal projects. We have some workflows defined for which we felt Microsoft Azure Logic Apps would be the best suited because it requires an approval process. Once the approval is given, some keys are given to the users, and those are temporary keys, after which Microsoft Azure Logic Apps makes sure that after a certain period of time, maybe a few days, those keys are removed from the system.

The most valuable feature of the solution is the entire workflow that we get. We can keep it in suspended motion. We can restart it, resume Microsoft Azure Logic Apps again, and build it easily. There are multiple instances in which the same Microsoft Azure Logic Apps can run.

Microsoft Azure Logic Apps is good for certain types of workloads, but it doesn't offer many customization options. Considering the current features of the tool, one area I could think of is probably a spot where you can run some kind of script, a task that will just run a script since if it is provided in the tool, one can do much more than what one does currently.

In the future, I would like the product to provide a particular task for running scripts.

I have been using Microsoft Azure Logic Apps for four years. I am an end-user of the tool.

It is a very stable solution. Stability-wise, I rate the solution a ten out of ten.

My company hasn't really tried out the scalability part associated with the product.

The product can be recommended for businesses depending on their use cases and the company's size. If it fits your use case, you can use it. If it doesn't, it doesn't matter whether it's the company's smaller, medium, or large.

I don't remember contacting the solution's technical support team.

The product's initial setup phase is simple.

The solution is deployed on the cloud-based model.

Microsoft Azure Logic Apps is a little bit expensive, and that is why you use it only for certain types of scenarios.

My company did not test the integration capabilities of the product since we did not have to deal with such use cases.

I haven't used any AI feature with Microsoft Azure Logic Apps.

I can recommend the product to others.

I rate the product an eight out of ten.

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.