We performed a comparison between Microsoft Azure App Service and Pega BPM based on real PeerSpot user reviews.
Find out in this report how the two Rapid Application Development Software solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The most valuable features of Microsoft Azure App Service are its vertical and horizontal scaling, along with its ability to throw a docker image."
"The program is stable and we've had no technical issues so far."
"The solution is very simple to set up."
"The solution overall is very good."
"This solution is easy to deploy."
"The product is scalable."
"I'm a decision-maker, not a technician. From my perspective, the most significant advantage is that Azure is a one-stop shop. Everything we needed was included in the Microsoft Agreement. During COVID, it was the most convenient and most straightforward decision."
"What I found most valuable in Microsoft Azure App Service is that it's a PaaS. I also like that it supports Docker and multiple frameworks so that you can work on Java, Ruby on Rails, PHP, and Python."
"The case management is great."
"The most valuable features of the solution are case management, routing, and low-code environment."
"The solution provides us with a very good dashboard."
"Pricing is a little on the high side."
"The ability to define processes, build reports, and get insights or analytics on data is most valuable. It is a powerful platform."
"The workflows are the most valuable features, particularly for us, because we were attempting to automate processes by utilizing workflows to provide a hands-off comparison between the bot and the human."
"The most valuable feature of Pega BPM is its architecture."
"The stability has been good. We haven't had any issues."
"I would like to see some improvement in the UI/UX design, to make navigation of this solution more user friendly. For example, it could contain more explicit information on each of the features."
"Having a surplus of tutorials from Microsoft, rather than relying solely on documentation or features from other sources like YouTube, can be beneficial."
"I want more transparency in billing. It would be better if we could understand and control the billing to customize it. Also, Microsoft should provide more guidance about the widgets and subsets of various products. The Microsoft portfolio is so huge that it's sometimes difficult to choose the correct option. There's always a chance we are paying more than necessary."
"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."
"The outbound connectivity is not great."
"Microsoft Azure App Service could improve by having better integration and connectivity with other platforms. The solution has good integration with other large companies' solutions but there are smaller service platforms companies where there could be integrated better."
"If you're on the cloud, you just get a web interface without much detail for additional configuration or the authority to configure the root or system-level configuration."
"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's pricing model or licensing model could be a little better."
"Pega should work on redefining their model and creating a demand for their skills."
"The workflow automation can be slow, so there is room for improvement there."
"I think there is room for improvement in the low code/ no code environment that they're promoting now. That needs to be aligned a little bit more. I still feel that it is not that friendly for a person who has no experience with Pega to just go in and try to create something."
"Its implementation in the public sector was a bit complex."
"It is scalable, but it also interacts with a lot of other systems. I think they thought that the interface to other systems, legacy systems, was its strength, but when problems do occur, quickly diagnosing those problems has been a challenge."
"If it could also be integrated with robotics, it could help with a lot of things, even if we don't have APIs, we could still talk to other applications. If it could invoke a bot, for example."
"Pega's technical support could be better."
Microsoft Azure App Service is ranked 8th in Rapid Application Development Software with 38 reviews while Pega BPM is ranked 7th in Rapid Application Development Software with 57 reviews. Microsoft Azure App Service is rated 8.4, while Pega BPM is rated 8.2. 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 Pega BPM writes "Fastens application development and has all the features to meet the requirements of our customers". Microsoft Azure App Service is most compared with Microsoft Power Apps, Oracle Application Express (APEX), ServiceNow, Appian and ServiceNow Now Platform, whereas Pega BPM is most compared with ServiceNow, Camunda, Appian, Microsoft Power Apps and Bizagi. See our Microsoft Azure App Service vs. Pega BPM 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.