Skip to main content
Azure App Service

Azure App Service


What is Azure App Service?

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…

Read more
Recent Reviews
Read all reviews


Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards

Reviewer Pros & Cons

View all pros & cons
Return to navigation


View all pricing

Shared Environment for dev/test


per month

Basic Dedicated environment for dev/test


per month

Standard Run production workloads


per month

Entry-level set up fee?

  • No setup fee
For the latest information on pricing, visit…


  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services

Starting price (does not include set up fee)

  • $9.49 per month
Return to navigation

Product Details

What is Azure App Service?

Azure App Service Technical Details

Deployment TypesSoftware as a Service (SaaS), Cloud, or Web-Based
Operating SystemsUnspecified
Mobile ApplicationNo

Frequently Asked Questions

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.

Azure App Service starts at $9.49.

Reviewers rate Development environment replication highest, with a score of 10.

The most common users of Azure App Service are from Enterprises (1,001+ employees).
Return to navigation


View all alternatives
Return to navigation

Reviews and Ratings


Attribute Ratings


(1-8 of 8)
Companies can't remove reviews or game the system. Here's why
Rudolph Pereira | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
Azure App is being used to host our .NET applications. Runtime stack for these are .NET 2.1. Azure has good support for .NET applications. So we prefer using Azure for .NET.
It is integrated will with Azure DevOps. So we use piplelines to deploy code.
  • It has options to deploy using CI/CD.
  • It has great integration with Azure Devops
  • It has all the common runtimes, so we don't need to install softwares.
  • Some times our .NET API Service crashes and it is hard to find the root cause.
  • Quick Links to frequently used pages will help
  • PHP 8 is not supported yet.
Azure App Service is suited well for .NET runtimes. We don't need to do any IIS configuration. It is well integrated with DevOps so CI/CD pipelines can be configured.
Multiple applications cannot be hosted on the same Service. So it can get expensive for smaller apps.
Score 7 out of 10
Vetted Review
Verified User
We use Azure Web Apps for our Front End and some big data processing needs: for the monolith and some microservices. Also we host APIs over them. Web Apps offer an easy to use platform for creating and modifying our code in a seamless way across different stages of our data ingestion-processing-and offering for the customers.
  • Extremely easy to deploy and update from Visual Studio
  • It integrates seamlessly with other Azure PaaS resources
  • It has an in-depth integration with AppInsights, so you can understand errors and their root cause easily.
  • Easy to create and delete, what is not the same case in a IaaS resource
  • It escalates based on CPU workload and some other resource variables.
  • Configuration changes are almost immediate
  • Offers an excellent abstraction from hardware backend of the platform
  • That's updated very often, saving time and the risk of a self-performed update over a IaaS
  • That's really easy to develop for Web Apps
  • It supports Function Apps and Web Apps into the same "cost black box"
  • Irrationally expensive
  • High latency and poor response times in heavy workloads
  • Some updates lead to failures and crashes of hosted apps
  • Tech support starts defending Microsoft rather than helping you to get rid of a production failure
  • That's easy to have a peak cost with automatic resources escalation.
  • Lacks of spent money limits for escalation
  • Unnecessary deprecation of runtimes that makes the platform less interesting for complex applications that can't be updated periodically
  • Every single minor feature that's an spending. For example, a basic firewall.
For a mid size front end, with a good budget to pay for resources escalation. Also for test environments and debug of Web Apps. It hosts great Function Apps, together with Web Apps. Spending in bundled in firewall, that's a good platform for e-payments and complies with all http / web standards, so you wont have surprises with Chrome and Chromium.
It comes with a good IP filter, that you would use starting in S1 (basic production) plan, but if you want a true firewall with DoS protection, it comes as an "additional". Both perform well.
Production plans have built-in backup and advanced networking support, also if spend limits are not so low, that's great to integrate your website in a private network.

Vinay H | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
We used it to teach the students who bought the course how to use the web app and where to use. We helped them to deploy the projects on Azure. Also we helped them to get the student packs and Azure credits so it may be helpful for them to deploy their projects without the need of credit cards!
  • Very simple and easy development process
  • Azure provide the built-in security for the web apps
  • The application can handle the high traffics
  • The Azure is providing little less amount of data centers, so they can increase the data centers.
  • Customized development; Azure needs to provide some more options to customize
  • Some of the essential things about the viewers and logs must be provided. Currently I feel they are putting limit on monitoring.
So based on our experience Azure is giving some API development, that is best thing. Also Azure is giving streamlined workflow for DevOps. It is supporting some popular programming languages like java, .net , javascript etc that make it easy to develop and deploy application in the platform and monitor it.
Score 8 out of 10
Vetted Review
Verified User
The ASP NET Core apps were deployed using Azure App Service. Multiple programs were installed and utilized by the entire company. Having the ability to launch our apps directly from Visual Studio was a huge time-saver. The Azure site or the Azure command-line interface allowed us to make the necessary adjustments.
  • Visual Studio makes it an easy to deploy an app.
  • The Azure CLI and the Azure Portal are the two most convenient ways to interact with the cloud.
  • There's no need to worry about server upkeep. We could simply increase our capacity by changing a few gateway settings.
  • Like Heroku's dynos, abstraction of computing resources.
  • The total size of the Azure Portal has a negative impact on the management of Azure App Service apps.
  • The cost of making large transitions in the size of a resource is high.
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.
Score 8 out of 10
Vetted Review
Verified User
We use Azure App Service for our full cloud-based website's new version. We use it to deploy both production and QA versions of the site, so that we don't have to manage website infrastructure, including on-premise web servers and security equipment. We use it alongside other Azure services, including storage, CDN, DB...
  • scalability works very well
  • integration with other Azure services
  • highly secured
  • the learning curve can be tough (just like other azure services)
  • the UX/UI could be more intuitive (just like other azure services as well)
  • monitoring can be hard to understand
  • Microsoft's learning resources are hard to understand
Azure App Service is well suited in our case :
  • Our website is developed by our tech partner in a full Microsoft Azure cloud based environment.
  • We gave them specific access rights and the CI / CD integration helped a lot for updates and improvements deployment.
  • Most of the infra issues we had with our website weren't coming from App Service
Score 7 out of 10
Vetted Review
Verified User
I used it to host our organization website, which is written by PHP. As the website is our main product, it plays very important role in our company. We used Azure's app engine for several months, mostly for our testing purpose. But we never rolled out our production to Azure because of some issues.
  • Auto scaling
  • Good management dashboard
  • Fast setups
  • Learning curve
  • Web Interface
  • A mobile app
If you are a large organization where you have a lot of traffics, Azure is good for you. If your scenario is something like, you sometimes have high traffic, and sometimes low traffic, and you got enough money, Azure is good for scaling up to your need. Azure is definitely not for you if your budget is low. Not suitable for low budget people AT ALL.
Drew Harrison | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
We use Azure App Service to build full-fledged custom web-based software solutions for small and medium-sized businesses in a variety of markets. The Azure App Service coupled with .NET, Entity Framework, and other Azure features (storage, tables, etc.) make it easy to quickly build fully-functional apps, and we're able to do so so much quicker than when we were using the LAMP stack (Linux, Apache, MySQL, and PHP). Plus, we can scale resources with a click instead of needing to migrate to different servers and manually handle load balance, etc.
  • Super quick & easy to deploy new apps in visual studio
  • Easy scaling to help reduce costs during off-hours
  • The powerful Azure ecosystem offers a lot of functionality that ties in well with Azure App Service
  • Jumps between resource sizes can get expensive
  • 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).
Azure App Service is great if you're starting a new web project and need an infrastructure that is fast, stable, secure, and scalable. The service has a very high up-time, and it supports a variety of languages and technologies (though it really shines with the .NET stack - C#, ASP.NET, Entity Framework, etc.). If you're thinking about porting an existing app over, it may wind up being expensive as far as resources go if the software isn't properly optimized to utilize cloud resources efficiently, so that's something to keep in mind.
Score 8 out of 10
Vetted Review
Verified User
During my time at the company, Azure App Service was used to deploy ASP NET Core applications. It was used throughout the whole organization and we had multiple applications deployed there. It was pretty useful since we could deploy our applications directly from Visual studio, never leaving our code editor environment. We could modify the settings from the Azure portal or with the Azure command-line interface.
  • Simple app deployment from Visual Studio.
  • Easy interfaces: Azure CLI and Azure Portal.
  • No server maintenance. We could scale easily by just modifying some settings in the portal.
  • Abstraction of computing resources like Heroku does with dynos.
  • Azure Portal overall is pretty bloated and that affects managing Azure App Service applications.
If your application is developed in Visual Studio IDE (usually .NET applications), it will be extremely easy to deploy your applications to Azure App Service. Visual Studio IDE already has the functionality to deploy there with very few clicks.

Due to the complexity and bloatedness of Azure Portal, I would recommend less complex platforms like Heroku for less-experienced developers.
Return to navigation