We performed a comparison between Appian and Microsoft Azure App Service 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 technical support is excellent."
"We appreciate the drag and drop functionality and the easy to access plug and play features."
"Since implementing we have had a faster time to solution, with fewer resources needed."
"It reduces development time in half making us more efficient."
"Technical support is helpful."
"The most valuable feature is business automation."
"The setup is easy."
"Write to Data Store Entity - Saving data in SQL databases is done easily using entities. Entities (CDTs in Appian terminology) define relationships and target schema tables via XSD files."
"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 user interface and the ability to quickly develop are the two main advantages of Microsoft Azure App Service. You can develop anything without having any coding experience and it is not complex and the components are easily customizable."
"The solution can scale."
"Azure data factory is a good tool."
"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."
"Debugging using Application Insights is a valuable feature."
"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."
"The most valuable feature is that it's an ideal solution when it comes to lifting and shifting monolithic applications from on-premises to Azure Cloud. It allows for a quick shift into the cloud without having to analyze and design very specific infrastructure and services for monolithic applications hosted primarily on-premises. Let's say that the team does not want to really redesign monoliths in a microservices-based application and that they want to make a quick move towards adopting the cloud tech stack. Then, Microsoft Azure App Service is probably the best option."
"Appian could improve their customer-facing initiatives."
"Authoring tool is slow to use resulted in limitations on how quickly solutions can be built."
"It would be useful if they could create an academy or forum in the future to help active users answer questions they have about the solution."
"One of the areas that Appian is working on is to improve its UI capabilities and give more flexibility to the UI."
"I would like to see more features for enterprises. They would also benefit from adding documentation and training on their site."
"Appian could include other applications that we could reuse for other customers, CRM for example."
"There are four areas I believe Appian could improve in. The first is a seamless contact center integration. Appian does not have a contact center feature. The second is advanced features in RPA. The third would be chatbot and email bot integration—while Appian comes with chatbot and email bot, it's not as mature as it should be, compared to the competition. The fourth area would be next best action, since there is not much of this sort of feature in Appian. These are all features which competitors' products have, and in a mature manner, whereas Appian lacks on these four areas. I see customers who are moving from Appian to Pega because these features are not in Appian."
"Lacks business rules management as part of the solution."
"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."
"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."
"App Service sometimes becomes very slow to respond, and it can be difficult to find the issue causing this."
"Microsoft Azure App Service needs some improvement in the scaling area."
"The solution is quite expensive. If you need more features, you need to pay for them."
"The outbound connectivity is not great."
"Can be improved by increasing the number of data centres worldwide."
Appian is ranked 6th in Rapid Application Development Software with 57 reviews while Microsoft Azure App Service is ranked 8th in Rapid Application Development Software with 38 reviews. Appian is rated 8.4, while Microsoft Azure App Service is rated 8.4. The top reviewer of Appian writes "Low resource consumption, easy setup, and stable". On the other hand, the top reviewer of Microsoft Azure App Service writes "A solution with great server management and helps improve performance". Appian is most compared with Microsoft Power Apps, OutSystems, Camunda, ServiceNow and Pega BPM, whereas Microsoft Azure App Service is most compared with Microsoft Power Apps, Oracle Application Express (APEX), ServiceNow, Pega BPM and ServiceNow Now Platform. See our Appian vs. Microsoft Azure App Service 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.