What advice do you have for others considering Microsoft Azure Logic Apps?

Microsoft Azure Logic Apps has a straightforward nature. The process is much simpler. This design is designed for seamless integration, making Logic Apps the preferred choice. Overall, I rate the solution a nine out of ten.

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.

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 is a low-code development. One can easily do the development and save the workflow. It is user-friendly, offering different connectivity with different services. It should be leveraged as much as possible. Overall, I rate the solution an eight out of ten.

I would rate the solution an eight of ten.

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.

I rate Microsoft Azure Logic Apps a nine out of ten. It works well for deployment and building connectors. It allows us to connect interfaces of two different platforms easily in a graphical way rather than using coding.

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 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.

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.

I would rate the product an eight out of ten. We have both medium and enterprise businesses as customers.

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

I'm an end-user. I've been using the latest version of the solution. We chose the product as it was easy to connect to on-premise services, especially an on-premise SQL database, which is pretty easy using Logic Apps. Companies should probably use it if they have the use case. It's an easy and cheap way to integrate with some on-premise services. Other ways are ultimately maybe easier, yet they are often very difficult to set up and a lot more expensive. I'd rate the solution nine out of ten. If you are a bit tech-savvy, you can just use it. It can do a lot, and it can do it easily.

I recommend the solution for integration providers and rate it a seven out of ten.

Overall, this is a good solution. More issues tend to appear when connecting in an on premises environment compared to the cloud. I would rate this solution a nine out of ten. It is flexible and user-friendly. The logic app is specifically easy to navigate.

Microsoft Azure Logic Apps is a PaaS application, and as it's in the cloud, there's no concept of versions. In the conventional world, you have a version 9, 10, or 11, for example, but in the cloud, it is a PaaS, and you're using that PaaS. Between seven to eight developers write the code for Microsoft Azure Logic Apps in my company, but these developers come and go, depending on the project. My advice to anyone who wants to use Microsoft Azure Logic Apps is to go with AWS Step Functions, for the cost and the security. It's also much easier to implement AWS Step Functions compared to Microsoft Azure Logic Apps. AWS Step Functions costs less when compared to Microsoft Azure Logic Apps. My rating for Microsoft Azure Logic Apps is seven out of ten. If anyone wants to use it, then no problem. My company is a Microsoft customer.

I rate Microsoft Azure Logic Apps a ten out of ten.

My advice to others is Microsoft Azure Logic Apps is easy to use compared to other services. You don't need hardcore development experience to use it. It's more of a UI-based, drag and drop, sort of logic-building capability. You don't necessarily require to have core developer skills to use it. You only need to be familiarized with some of the services and basic administration of Azure. Anyone can build applications based on Logic Apps. I rate Microsoft Azure Logic Apps a seven out of ten.

I would rate this solution 7 out of 10.

We're developing our solutions on three elements. One element is Logic Apps, and it represents our functionalities. The second element is Cosmos DB, which is the database and the persistence for our solutions. The third element is the storage account. Inside the storage account, you have a special folder called Web. You can put it inside this folder. You can put any single-page application, like Angular. In the Angular application, you have hosting of that application and application files for free. So, we put an Angular single-page application into this storage account, which is calling Logic Apps, for the functionalities and endpoints. In the backend, we had the Cosmos DB, which is the database for the whole thing. You can add elements from the outside to connect the customer's data center to Azure and this application you have made. Azure doesn't even have to know or have access to customer systems. In the end, you have a very scalable solution without the high risk of someone breaking it, and he will just know the data inside it. But he would not gain any access to the customer data center. On a scale from one to ten, I would give Microsoft Azure Logic Apps a nine.

Definitely, I would recommend it. Make sure that what you need can be done through Logic apps and not other alternatives, or not with other functions, and not with any other alternative system. You need to do the research and learn about the limitations or know what Logic Apps is designed for to ensure that it fits the use case that they're trying to do. This applies to all the services. At least properly plan or read about the service before going all-in and trying to have Logic Apps deliver something that's not meant to deliver. In summary, this is a good product but tThere is always room for improvement. I would rate Microsoft Azure Logic Apps an eight out of ten.

I don't recall which version I am using for the solution because it is based on what the latest version Azure has released at the time. We are actively trying to move all our solutions to ones in the cloud because of the cost of increasing infrastructure and it is also hard to maintain an in-house data center. I think Power Apps should be as user-friendly as possible, to allow more business-oriented people to utilize such things for their self-services needs rather than depending on IT resources. I rate Microsoft Azure Logic Apps a six out of ten.