Skip to main content
TrustRadius
Azure App Service

Azure App Service

Overview

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

Awards

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

Pricing

View all pricing

Shared Environment for dev/test

$9.49

Cloud
per month

Basic Dedicated environment for dev/test

$54.75

Cloud
per month

Standard Run production workloads

$73

Cloud
per month

Entry-level set up fee?

  • No setup fee
For the latest information on pricing, visithttps://azure.microsoft.com/en…

Offerings

  • 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

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(169)

Attribute Ratings

Reviews

(1-4 of 4)
Companies can't remove reviews or game the system. Here's why
Score 7 out of 10
Vetted Review
Verified User
Incentivized
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.

Platform-as-a-Service (11)
80%
8.0
Ease of building user interfaces
100%
10.0
Scalability
100%
10.0
Platform management overhead
40%
4.0
Workflow engine capability
50%
5.0
Platform access control
100%
10.0
Services-enabled integration
100%
10.0
Development environment creation
100%
10.0
Development environment replication
100%
10.0
Issue monitoring and notification
80%
8.0
Issue recovery
60%
6.0
Upgrades and platform fixes
50%
5.0
  • When workload was medium-low and medium-high it escalated and performed in a very good way. We saved a lot of time and a specialized role for managing it. Also, compared to an IaaS solution, was reasonably expensive.
  • Many platform issues on 2020 caused problems with our business. Downtime was reimbursed, but some customers were lost and churn grew.
  • Using AppServices and Web Apps as a Big Data processing platform was not a good idea, specially when data volumes grew and every escalation in resources was 2x of the previous stage cost.
AppServices that's easier to manage than its competitors, specially if you have everything in Azure. But also that's the most expensive service when you escalate or start using it for massive data processing. It would be an excellent containers platform if were easier to deal with its costs.
Regarding Apache and AKS, also I must mention the required level of manual maintenance that's a key point. If you wont have internally or via consulting a specialized role, AppServices that's the best choice.
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.
  • It provides Built-in security
  • Very easy to use, Anyone can use it with little guidelines.
  • Support of multiple programming languages , frameworks etc
Platform-as-a-Service (11)
78.18181818181819%
7.8
Ease of building user interfaces
80%
8.0
Scalability
90%
9.0
Platform management overhead
90%
9.0
Workflow engine capability
80%
8.0
Platform access control
90%
9.0
Services-enabled integration
90%
9.0
Development environment creation
90%
9.0
Development environment replication
N/A
N/A
Issue monitoring and notification
80%
8.0
Issue recovery
80%
8.0
Upgrades and platform fixes
90%
9.0
  • Cost saving
  • Time saving
  • Limited control
  • High performance
Azure is some what easy to use and we can learn the azure platform easily. And mainly for students they are giving free credits. So by using the credits we can learn or deploy using that credit
Filmora, Microsoft Office 2016 (discontinued), Brave
Score 8 out of 10
Vetted Review
Verified User
Incentivized
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.
  • Auto scaling.
  • Azure Kubernetes.
  • CI/CD pipelines for DevOps development.
Platform-as-a-Service (11)
87.27272727272727%
8.7
Ease of building user interfaces
80%
8.0
Scalability
100%
10.0
Platform management overhead
90%
9.0
Workflow engine capability
80%
8.0
Platform access control
80%
8.0
Services-enabled integration
90%
9.0
Development environment creation
80%
8.0
Development environment replication
100%
10.0
Issue monitoring and notification
80%
8.0
Issue recovery
90%
9.0
Upgrades and platform fixes
90%
9.0
  • 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.
In terms of deploying your apps, Azure App Service provides a solid foundation. You may use either the Azure command-line interface or the Web Portal to administer these apps. As a whole, I find You may easily deploy your apps to Azure App Service to be a really difficult platform for novices to get their feet wet. First and foremost, I'd look at Heroku's user interface and the way it abstracts compute units.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
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
  • ON demand (and planned) scalability
  • easy Azure devops integration
  • easy configuration (for experimented azure dev) including Azure CDN linking
Platform-as-a-Service (11)
79.0909090909091%
7.9
Ease of building user interfaces
80%
8.0
Scalability
100%
10.0
Platform management overhead
80%
8.0
Workflow engine capability
N/A
N/A
Platform access control
90%
9.0
Services-enabled integration
100%
10.0
Development environment creation
90%
9.0
Development environment replication
100%
10.0
Issue monitoring and notification
70%
7.0
Issue recovery
80%
8.0
Upgrades and platform fixes
80%
8.0
  • deployment time reduction
  • infrastructure management costs reduction
  • site performance/availability improved
We didn't use other App services because we use Azure as our cloud provider and our first experience was with Azure App Service
Return to navigation