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.

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.

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.

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. 

We have developed multiple integrations using the solution. We mainly used it to integrate SAP, ServiceNow, and different third-party APIs with the front end. There were different use cases for Microsoft Azure Logic Apps.

The solution provides multiple connectors, which are very useful. If we don't have a suitable connector, we can create one ourselves. With Microsoft Azure Logic Apps, we need not go into how to draft the code and how to structure the classes. We just need to focus on the logic. It's a quick solution for the coding part. It includes coding, but not that much.

The solution should include more connectors. In one of my projects, we faced issues with SAP connectivity. The connector needed to connect the SAP was not compatible with our architecture. We had to create our custom connector for that.

Microsoft Azure Logic Apps needs to be enhanced to make it more personal to the integration area. They are moving towards development but not that much towards the integration services part. It should be easier to connect to different third-party services.

Microsoft Azure Logic Apps is a stable solution.

More than 50 users are using the solution in our organization.

The solution's initial setup is not that time-consuming.

In my experience, Microsoft Azure Logic Apps is not a cheap solution. A few of my projects got delayed because of the charges. The pricing depends on whether an organization can handle all the costs because the tool has a pay-as-you-go policy. Whatever you use and the complex integration you create should be chargeable based on their iteration.

Microsoft Azure Logic Apps is deployed on the cloud in our organization. It is easier to use the tool, but it should be enhanced towards the connectivity area. You can create the logic by having the subscription and resource group. If you want to create a complicated solution, Logic Apps goes hard towards it because of their mapping functionalities.

I would recommend the solution to other users because it is a good product in terms of security and B2B integrations. It is easy for somebody to learn to use Microsoft Azure Logic Apps for the first time.

Overall, I rate the solution an eight or nine 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.

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. 

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.

With Microsoft Azure Logic Apps, we can orchestrate and pull event-based triggers. We can use the solution to schedule a workflow based on any new record inserted into our database.

The solution's best feature is that it is compatible with the cloud and has many connectors and third-party adapters. You can connect it with almost every system.

We have lots of other systems. When we raised a complaint with Microsoft, they asked us not to use the solution for a particular purpose. We wanted to use Microsoft Azure Logic Apps, but we faced a timeout. We had a call with Microsoft regarding one of the issues. The support person with whom I was discussing was also not very comfortable with that question.

I have been using Microsoft Azure Logic Apps for the last one year.

We are working on the same technology in our company. Approximately 40 to 50 people on our team use Microsoft Azure Logic Apps.

The solution's customer support depends on the type of partner you are. If you are a gold partner, they will reply immediately. However, if you have a lower level of collaboration with Microsoft, they will take some time. The technical support team does fix issues, but they take time.

The initial setup of the solution would be a bit difficult if you are using CI/CD. CI/CD, container integration, and container deployment are one-time processes. Setting them up once makes the rest of the deployment easier. If you don't do it initially, you have to copy and paste, which will take time. I suggest you invest time in creating a CI/CD to avoid the later dependencies or consequences of not using CI/CD.

You will be charged too much if you are unaware of the solution's cost. Initially, when I was doing my development and POCs, one day, I forgot to close the connection or the artifact I created. The next morning, I learned that INR 40,000 had been deducted from my credit card.

Some companies use the solution for monetary benefits. Other companies upgrade their technology to compete with other technologies. In my current organization, everything is working fine, but they must also upgrade their technology. They were not saving money with the tool but had to upgrade themselves in technology.

You should be aware of the solution's configuration. You don't have to write any code, even for your basic work needs. However, you do have to configure some things and be aware of the triggers and actions. There is also a lot of help available on Google and YouTube to do it.

We have to write the code in such a manner that the next person who is using it or visiting that particular code should be aware. If you don't write properly what type of work you are doing inside a particular code, it'll be very difficult to identify what you have done. If I pick one particular action, the action should be very clear about what I'm doing in that action.

Otherwise, it will be very messy. If you use the default naming structure, it will be like one, two, or three variables. If you do not write the proper name of that variable, it'll be very difficult to identify what type of work you were doing inside that scope, function, or action.

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

Microsoft Azure Logic Apps is a fantastic suggestion, especially for those who may not have extensive coding knowledge but understand the requirements well. It provides an easy way to create an auto-response solution. For instance, if you have services running in Azure and want to generate an alert, it allows you to integrate seamlessly. You can trigger tasks based on alerts, creating multi-layered tasks with loops, conditions, and more. It will enable you to perform multiple actions.

I have an example where I automated a business process using Logic Apps and even published an article on the same solution. The customer is required to monitor their NSGs. In the Logic App flow, I designed an alert system if any deny event occurred. It created an HTML-formatted alert identifying the request details, such as the user, specific server, and port that were denied. This alert was then sent to the respective admin users, allowing them to enable the request. If enabled, the request would go back to the system, triggering a script to enable it; otherwise, it would remain disabled.

In another experience, I created an internal application for the purchase order department using Power Apps and Microsoft Azure Logic Apps. I utilized it to gather data from an Azure SQL database and generate a PDF report. This report was then sent to the relevant stakeholders.

Using connectors in the product is quite straightforward and user-friendly. The platform provides a list of connectors, and users can easily search for the specific connectors they need. 

An area of improvement I've encountered is related to the number of connectors available in Logic Apps. While there are many connectors, I found that the "send email" connector may not work as expected, and one has to rely on Office 365 plugins or other alternatives. This could enhance user experience, especially when considering the additional overhead and licensing requirements associated with Office 365. It also needs to improve security features. 

I rate the solution's stability an eight out of ten. 

The tool's scalability is managed by the backend service itself, as it is a managed service.

The tool's tech support is good and customer-friendly. 

The tool's deployment is straightforward. The deployment time can vary and is not necessarily due to the complexity of the product itself. Instead, the time taken depends on the specific requirements of the integration. Factors such as the complexity of the requirement, the number of conditions, and the need for multiple tests can influence the deployment time. Correctly connecting the suitable connectors, using the appropriate syntax, and implementing loops, among other considerations, may contribute to the overall time spent on deployment. However, it's important to note that the solution, as a service, is not inherently complex.

I rate the overall product an eight out of ten. For anyone looking to automate processes, tasks, configuration, application execution, script execution, or data extraction from databases without extensive coding knowledge, I would recommend using Microsoft Azure Logic Apps.

The solution can be integrated with many services. It can integrate with Azure Automation, Azure Defender, web apps, and essentially anything for which a connector is established.