We performed a comparison between Microsoft Azure App Service and Microsoft PowerApps based on our users’ reviews in five categories. After reading all of the collected data, you can find our conclusion below.
Comparison Results: PowerApps is the winner in this comparison. According to its reviewers, it is flexible and easy to use. In addition, it has a proven ROI.
"The solution can scale."
"It's very easy to use. That's one of the advantages for the business, that you don't need to struggle to configure your website and your app service. Microsoft made sure to make it stable and very easy to configure."
"The most valuable feature of Microsoft Azure App Service is autoscaling and resource grouping. Additionally, the integration works well, it is easy to do."
"This solution is easy to deploy."
"Enroll in some kind of formal training, not from Microsoft, but from a partner, and keep up with the change because the Azure platform changes a lot."
"App Service's best features are that it can be scaled easily and it includes Kudu."
"The most valuable feature of Microsoft Azure App Service is customization. It provides the building block from its modularity. You can add what you need with the appropriate code."
"The feature I find most valuable is the 'Diagnose and Solve problem' function. This not only allows us to fix a problem, but also to generate analytics on why the issue occurred."
"We particularly like the workflow connectors in the forms, for information introduction purposes."
"The initial setup is not complicated."
"Creating a PowerApp is very easy. All I do is link and share the result with my colleagues. Deployment is very fast."
"The solution is excellent at figuring how to build an application in three months. It makes it very quick and easy."
"The most valuable feature of this solution is the Model-driven or Canvas application-making platforms. The power of the two gives us exactly what we are looking for."
"The product is very user-friendly."
"The most valuable feature is the time-to-market because you can make apps pretty fast."
"There are a lot of different applications; you can connect PowerApps, or Flow, or Power BI to many different types of applications to interchange data."
"If you are not using the product properly, then it can cost you a lot of money. Hence, you need to make sure that you choose the services wisely. You need to make sure that you have a budget and have some alerts associated with it. The tool's cost can easily go high if you don't consider these things properly. You need to review your existing subscription."
"Customers love it when a solution is affordable, but with Microsoft Azure App Service, you can start and stop it, and when you stop it, it won't be reachable and it won't be available, yet you're still being charged for it. You'll still be charged even if the solution isn't accessible because Microsoft Azure App Service runs on a shared virtual machine that keeps on running, so if there's a way to work this out, it'll be a great improvement to only pay for what you use. The solution should have no hidden cost and no extra charge when it's stopped. This is what needs improvement in Microsoft Azure App Service."
"I am new to the intervention and I find it difficult to find my way around the user interface. I have my own learning tool. However, it could be simpler for new users."
"Can be improved by increasing the number of data centres worldwide."
"It would be fantastic if Microsoft morphed after my exit service, removing it from subscriptions and moving it to different regions, especially for that service."
"The solution is quite expensive. If you need more features, you need to pay for them."
"Extended uptime and improved speed would be beneficial for both development purposes and the free tier of the service. Currently, the uptime is limited to a few hours per day, which could be increased to provide more continuous and efficient usage."
"The solution needs better integration capabilities on the network side."
"The notion people have is that no code equals no knowledge, and that's simply not true. Even though you don't have to write codes, you still have to know what you're doing."
"It has to improve the threshold limit where it can handle data beyond 5000 items."
"One area where the solution lacks is the limited size of the database it offers its users."
"Microsoft PowerApps is not intended for customizing what's generated in a major way."
"I have heard from developers that there is documentation missing in the reporting."
"In some cases, PowerApps would have some limitations in terms of the data, the number of transactions, and so on, but for a normal solution, it would be enough."
"Can be improved to cater to complex developments."
"One of the major problems with it is what PowerApps calls the delegation warning. Regardless of what platform, data source, et cetera, that you're using, you can't retrieve more than 2000 records."
Microsoft Azure App Service is ranked 8th in Rapid Application Development Software with 38 reviews while Microsoft Power Apps is ranked 1st in Rapid Application Development Software with 77 reviews. Microsoft Azure App Service is rated 8.4, while Microsoft Power Apps is rated 7.8. The top reviewer of Microsoft Azure App Service writes "A solution with great server management and helps improve performance". On the other hand, the top reviewer of Microsoft Power Apps writes "Low-code, low learning curve, and reduces manpower". Microsoft Azure App Service is most compared with Oracle Application Express (APEX), ServiceNow, Pega BPM, Appian and ServiceNow Now Platform, whereas Microsoft Power Apps is most compared with Oracle Application Express (APEX), Mendix, ServiceNow, Appian and OutSystems. See our Microsoft Azure App Service vs. Microsoft Power Apps report.
See our list of best Rapid Application Development Software vendors.
We monitor all Rapid Application Development Software reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.