The Microsoft Azure App Service is a PaaS that enables users to build, deploy, and scale web apps and APIs, a fully managed service with built-in infrastructure maintenance, security patching, and scaling. Includes Azure Web Apps, Azure Mobile Apps, Azure API Apps, allowing developers to use popular frameworks including .NET, .NET Core, Java, Node.js, Python, PHP, and Ruby.
$9.49
per month
Google Cloud Platform
Score 8.9 out of 10
N/A
Google Cloud Platform is a suite of cloud computing services used to build apps or take advantage of cloud infrastructural services, achieve legacy infrastructure modernization, or manage enterprise data and analytic needs.
$0
(25+ apps are currently available at no cost)
Microsoft Azure
Score 8.4 out of 10
N/A
Microsoft Azure is a cloud computing platform and infrastructure for building, deploying, and managing applications and services through a global network of Microsoft-managed datacenters.
$29
per month
Pricing
Azure App Service
Google Cloud Platform
Microsoft Azure
Editions & Modules
Shared Environment for dev/test
$9.49
per month
Basic Dedicated environment for dev/test
$54.75
per month
Standard Run production workloads
$73
per month
Premium Enhanced performance and scale
$146
per month
No answers on this topic
Developer
$29
per month
Standard
$100
per month
Professional Direct
$1000
per month
Basic
Free
per month
Offerings
Pricing Offerings
Azure App Service
Google Cloud Platform
Microsoft Azure
Free Trial
Yes
Yes
Yes
Free/Freemium Version
No
Yes
Yes
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
Free and Shared (preview) plans are ideal for testing applications in a managed Azure environment. Basic, Standard and Premium plans are for production workloads and run on dedicated Virtual Machine instances. Each instance can support multiple applications and domains.
—
The free tier lets users have access to a variety of services free for 12 months with limited usage after making an Azure account.
More Pricing Information
Community Pulse
Azure App Service
Google Cloud Platform
Microsoft Azure
Considered Multiple Products
Azure App Service
No answer on this topic
Google Cloud Platform
Verified User
Engineer
Chose Google Cloud Platform
We also use AWS and Azure in the setup, but went as far as GCP because it scales data workloads. BigQuery made complex analytics so fast and painless. The fact that it plays nicely with other Google tools means a better fit for how our teams work. GCP offered us more reliable …
I feel that Microsoft Azure typically outperforms Google Cloud Platform in hybrid cloud capabilities, integration aspects, and, primarily, security compliance features. Azure offered superior integration with Microsoft's enterprise software ecosystem, and it's second to none in …
You may easily deploy your apps to Azure App Service if they were written in Visual Studio IDE (typically.NET applications). With a few clicks of the mouse, you may already deploy your application to a remote server using the Visual Studio IDE. As a result of the portal's bulk and complexity, I propose Heroku for less-experienced developers.
When most of our stuff is in Google Cloud Platform, it works great to integrate and cross/share data that is all in Google Cloud Platform or BigQuery. It has simplified things from a permissions perspective as well. I'd say it is less appropriate when trying to test something quickly locally, or when half your stuff is in AWS or another provider.
Azure is particularly well suited for enterprise environments with existing Microsoft investments, those that require robust compliance features, and organizations that need hybrid cloud capabilities that bridge on-premises and cloud infrastructure. In my opinion, Azure is less appropriate for cost-sensitive startups or small businesses without dedicated cloud expertise and scenarios requiring edge computing use cases with limited connectivity. Azure offers comprehensive solutions for most business needs but can feel like there is a higher learning curve than other cloud-based providers, depending on the product and use case.
Microsoft Azure is highly scalable and flexible. You can quickly scale up or down additional resources and computing power.
You have no longer upfront investments for hardware. You only pay for the use of your computing power, storage space, or services.
The uptime that can be achieved and guaranteed is very important for our company. This includes the rapid maintenance for security updates that are mostly carried out by Microsoft.
The wide range of capabilities of services that are possible in Microsoft Azure. You can practically put or create anything in Microsoft Azure.
You may wind up putting a lot of eggs in one basket--not necessarily a con but something to keep in mind (most of your data will likely be managed and processed through Microsoft products/services if you fully commit to Azure App Service).
Learning new technology. If you're moving from on-premises to Azure App Service (or any cloud solutions), you'll likely have to rethink how things are done to achieve the same end results (and/or resources may become expensive quickly).
The UI is so confusing. The console is good, but it is like a maze. There are too many menus and settings, and things do not work as expected. It takes time to get friendly, and it is not friendly for new users.
Support experience: Sometimes, you get a great engineer, but other times, it's very difficult to talk with them as they are unable to respond as expected and solve issues late.
Region and zone are issues, as not all services are available in all regions, which is lacking when deploying something in the same region or zone.
The cost of resources is difficult to determine, technical documentation is frequently out of date, and documentation and mapping capabilities are lacking.
The documentation needs to be improved, and some advanced configuration options require research and experimentation.
Microsoft's licensing scheme is too complex for the average user, and Azure SQL syntax is too different from traditional SQL.
Moving to Azure was and still is an organizational strategy and not simply changing vendors. Our product roadmap revolved around Azure as we are in the business of humanitarian relief and Azure and Microsoft play an important part in quickly and efficiently serving all of the world. Migration and investment in Azure should be considered as an overall strategy of an organization and communicated companywide.
I have given this rating because Azure App Service performs very well in terms of speed, reliability, and reducing overhead, and improves overall team productivity, with a little scope for improvement in complex testing scenarios and configurations, scalability concerns in a large setup, and similar tracking and audit needs.
The Google Cloud Platform console is pretty slick for BigQuery especially. I have liked the visibility I get from using that and the way to integrate and see what's in our data lake. The logging console for tracking GKE jobs isn't quite as great, which is why it doesn't get a full 10.
As Microsoft Azure is [doing a] really good with PaaS. The need of a market is to have [a] combo of PaaS and IaaS. While AWS is making [an] exceptionally well blend of both of them, Azure needs to work more on DevOps and Automation stuff. Apart from that, I would recommend Azure as a great platform for cloud services as scale.
Microsoft has always been known for providing a high standard in terms of customer support and Azure App Service (and as a matter of fact the whole Azure Platform) is no exception. Azure App Service never caused us any issues and we only contacted their customer support for questions regarding server locations and pricing. I feel pretty satisfied with how they treat their customers.
We were running Windows Server and Active Directory, so [Microsoft] Azure was a seamless transition. We ran into a few, if any support issues, however, the availability of Microsoft Azure's support team was more than willing and able to guide us through the process. They even proposed solutions to issues we had not even thought of!
As I have mentioned before the issue with my Oracle Mismatch Version issues that have put a delay on moving one of my platforms will justify my 7 rating.
When we chose it, we did so because of its integration with Microsoft applications; now we need to integrate with AI, and Azure doesn't offer a good integration. That is the main reason to change it. It is still great to develop Windows- and Microsoft-based applications, but if we need to integrate with AI, Google wins by far.
Google Cloud Platform is release later than Amazon web service, I think that why Google Cloud Platform can learned and optimized the Dashboard and some features that make it easy to use and can be cheaper than amazon web service.
As I continue to evaluate the "big three" cloud providers for our clients, I make the following distinctions, though this gap continues to close. AWS is more granular, and inherently powerful in the configuration options compared to [Microsoft] Azure. It is a "developer" platform for cloud. However, Azure PowerShell is helping close this gap. Google Cloud is the leading containerization platform, largely thanks to it building kubernetes from the ground up. Azure containerization is getting better at having the same storage/deployment options.
Deployment of ASP.NET apps at the organization has been sped up.
An option to offer access to the version control system on a third platform so that we could easily deploy our apps.
Because of Azure App Service's scalability capabilities, the costs of running the services are kept to a minimum. As a result, we may save hundreds of dollars each month compared to the expenses of traditional servers by using fewer resources during slack periods.
It allows us to focus our efforts on other, more important items at hand
It gives us an affordable option letting me know it's available to all users, not just the largest scale ones out there
The customer service is always helpful and reliable, along with the service itself which lets me focus on my work instead of worrying about the service.
For about 2 years we didn't have to do anything with our production VMs, the system ran without a hitch, which meant our engineers could focus on features rather than infrastructure.
DNS management was very easy in Azure, which made it easy to upgrade our cluster with zero downtime.
Azure Web UI was easy to work with and navigate, which meant our senior engineers and DevOps team could work with Azure without formal training.
