It's very easy to use, and it's blazing fast. The best thing about Logic Apps is actually its ability to create a solution in a matter of hours. It doesn't need any kind of provisioning, and you don't need any kind of hardware. You can create very small elements like these Logic Apps, and you can build a whole solution from those very simple and small elements.
I also like that they are completely incorporated with your existing active directory. You can use user groups directly from the active directory inside Azure and access it from the Logic Apps.
You don't need to do anything special, and you just have access. You can just check if the user is, for example, allowed to do some action. Normally it would take you some additional steps and some additional calls to check it. You have to come back to the active directory to make this possible. In Logic Apps, you just have it, and you can use it.
I think that there's this concept of logging and recall to the Logic App. It shows you every single step, every single product, and the result it's returning to the next step. It also has an amazing debugging feature.
You can rerun some calls and see if, after a correction of the Logic App, for example, you get the correct results. So, it's almost like it's alive. It's like you make a change, poof it, and it's in production, and it's working. The speed of the composition of the problem and creating a real solution for it is extremely fast with this solution. It's extremely fast in creation.
The documentation could be better. I think that's the only thing that was causing a normal level of problems. In terms of the documentation, it came from Cosmos DB and an additional product from Microsoft Azure.
I have been using Microsoft Azure Logic Apps for more than a year.
Microsoft Azure Logic Apps is scalable.
It's very cheap, but it comes with pluses and minuses. The positive thing is that it's very cheap, but on the other hand, it's extremely hard to tell how much it will cost.
At the start of the project, it's almost impossible to tell how many times you will be calling some kind of Logic App function. You cannot state how much of the internet transfer you will use or how much data your will use.
We're developing our solutions on three elements. One element is Logic Apps, and it represents our functionalities. The second element is Cosmos DB, which is the database and the persistence for our solutions. The third element is the storage account. Inside the storage account, you have a special folder called Web. You can put it inside this folder. You can put any single-page application, like Angular.
In the Angular application, you have hosting of that application and application files for free. So, we put an Angular single-page application into this storage account, which is calling Logic Apps, for the functionalities and endpoints.
In the backend, we had the Cosmos DB, which is the database for the whole thing. You can add elements from the outside to connect the customer's data center to Azure and this application you have made. Azure doesn't even have to know or have access to customer systems.
In the end, you have a very scalable solution without the high risk of someone breaking it, and he will just know the data inside it. But he would not gain any access to the customer data center.
On a scale from one to ten, I would give Microsoft Azure Logic Apps a nine.