We compared Microsoft Azure and Google App Engine based on our user's reviews in several parameters.
In summary, Microsoft Azure is praised for its scalability, reliability, customer service, pricing, and return on investment. On the other hand, Google App Engine is appreciated for its scalability, easy deployment process, infrastructure, customer service, pricing, and return on investment. The main difference lies in Azure's extensive range of services and flexibility, while App Engine could benefit from improvements in scalability and performance optimization.
Features: Microsoft Azure is highly praised for its scalability, versatility, reliability, and extensive range of services. In contrast, Google App Engine stands out for its easy deployment process, strong infrastructure, automatic scaling, and efficient datastore. It also seamlessly integrates with other Google services.
Pricing and ROI: The setup cost for Microsoft Azure is praised for its ease and simplicity, according to user feedback. Users find the licensing terms flexible and varied. On the other hand, Google App Engine has minimal and straightforward setup cost, making implementation easy. Its pricing is considered cost-effective and well-suited for users' needs., Microsoft Azure has been praised for its cost savings, improved efficiency, and scalability. It offers a diverse range of services and tools. On the other hand, Google App Engine is known for its positive ROI, increased efficiency, and seamless integration with other Google products. Users also reported time and resource savings.
Room for Improvement: Microsoft Azure users have provided feedback on areas that require improvement, while Google App Engine users have suggested enhancements in scalability, performance, resource allocation, latency issues, flexibility in configuration, and deployment options.
Deployment and customer support: Microsoft Azure users have provided varying feedback on the time required for deployment, setup, and implementation phases, with some mentioning a three-month deployment period and an additional week for setup. Other users mention a one-week timeframe for both deployment and setup. Careful evaluation of the context is crucial for accurately assessing implementation duration. Similarly, users of Google App Engine also reported different timeframes for deployment, setup, and implementation. Some mentioned three months for deployment and an extra week for setup, while others reported one week for both. Considering the specific context is essential to evaluate the duration of each phase accurately., In terms of customer service, Microsoft Azure receives positive feedback for its responsiveness and expertise. Users appreciate the prompt and helpful assistance in resolving technical issues, as well as the availability of comprehensive documentation. On the other hand, Google App Engine also has highly regarded customer service, with users appreciating the responsiveness, effectiveness, and reliability of the support team. They find the promptness in addressing queries and the knowledgeable guidance offered by customer service representatives to be satisfactory.
The summary above is based on 27 interviews we conducted recently with Microsoft Azure and Google App Engine users. To access the review's full transcripts, download our report.
"Seurity features - unauthorized individuals are unable to access certain applications."
"I've found that all of the features are valuable, especially the shared drive and the ability for multiple people to use their documents at the same time."
"The initial setup is okay. It's not too complex. Deployment took about one day."
"Its ability to integrate with most devices helps users who have different or old devices."
"The WhatApp feature is the most valuable."
"It is simple to use. It is much simpler than AWS. It is also very powerful."
"Google App Engine's most valuable feature is self-management. You do not have to manage the infrastructure underneath where all the functions are happening, such as load balancing deployment and version management, they are managed by the system itself."
"The solution is serverless, so we don't have to operate it."
"Feedback and error messages make much more sense in Azure than in AWS."
"It was very user-friendly when setting up the virtual machines and console. It was an easy task for my team to create virtual servers and start replications."
"The solution has enabled us to provide advanced indicators and analytics to the client on their data."
"Technical support has been good over the years."
"The data factory feature."
"We are using Microsoft Azure because our organization uses a lot of Microsoft solutions. We have used Microsoft technology for a long time and we have internal engineers with great capability that understand the technology. This is why Azure is the best for us."
"We are going to use Microsoft Azure to move some on-premise servers into the cloud so that our data can be held there."
"Microsoft Azure is easy to use."
"I would like a simpler deployment tool on laptops. It is a bit complicated at the moment. We know how to do it, but it could be easier to deploy it on laptops."
"The support for the Indian region is not as good as compared to the support that is offered to the regions in Europe."
"Some features of runtime don't work well in App Engine."
"I think there's still a lot that can be done with Google Meet and the video conferencing part of it. It could be more dynamic in terms of what can be done with it."
"I am limited to sending a photo to five people. I want to be able to send a photo to many people, not just five."
"The product's price is an area of concern where improvements are required."
"There needs to be more directions in terms of how to use the solution."
"Difficult to assess how pricing is managed."
"Sometimes performance takes a hit on a slow network."
"Due to the pandemic, I haven't been able to utilize their full resources. This has made it complicated to scale up. I hope this will be resolved after the pandemic."
"Technical support needs improvement."
"Because it has a lot of features, a person just coming into Microsoft Azure might feel that it is a bit complex."
"The solution needs to offer more data analysis services."
"The quality of some components of Microsoft Azure is not that great. For example, Microsoft has not fixed issues in Microsoft Teams for many years. There are well-known issues that are submitted by customers two years ago and they still are not fixed."
"Performance could be improved."
"We have faced some issues on the pricing side, but it has improved lately. We are trying to adjust to the new pricing methods that they are using now. It should be better from now on."
Google App Engine is ranked 11th in PaaS Clouds with 23 reviews while Microsoft Azure is ranked 1st in PaaS Clouds with 299 reviews. Google App Engine is rated 8.2, while Microsoft Azure is rated 8.4. The top reviewer of Google App Engine writes "Simplifies app development process for businesses". On the other hand, the top reviewer of Microsoft Azure writes "Promotes clear, logical structures preventing impractical configurations and offers seamless integration ". Google App Engine is most compared with Amazon AWS, Heroku, IBM Cloud Private, IBM Public Cloud and Amazon Lightsail, whereas Microsoft Azure is most compared with Google Firebase, Amazon AWS, Oracle Cloud Infrastructure (OCI), Pivotal Cloud Foundry and Salesforce Platform. See our Google App Engine vs. Microsoft Azure report.
See our list of best PaaS Clouds vendors.
We monitor all PaaS Clouds 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.