Azure App Service
Azure App Service
Overview
Recent Reviews
Reviewer Pros & Cons
View all pros & consVideo Reviews
Leaving a video review helps other professionals like you evaluate products. Be the first one in your network to record a review of Azure App Service, and make your voice heard!
Pricing
View all pricingEntry-level set up fee?
- No setup fee
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting / Integration Services
Would you like us to let the vendor know that you want pricing?
2 people want pricing too
Alternatives Pricing
Features Scorecard
No scorecards have been submitted for this product yet.Start a Scorecard.
Product Details
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 API Apps, allowing developers to use popular frameworks including .NET, .NET Core, Java, Node.js, Python, PHP, and Ruby.
Azure App Service Technical Details
Operating Systems | Unspecified |
---|---|
Mobile Application | No |
Comparisons
View all alternativesCompare with
Frequently Asked Questions
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 API Apps, allowing developers to use popular frameworks including .NET, .NET Core, Java, Node.js, Python, PHP, and Ruby.
What is Azure App Service's best feature?
Reviewers rate Support Rating highest, with a score of 10.
Who uses Azure App Service?
The most common users of Azure App Service are from Enterprises (1,001+ employees) and the Information Technology & Services industry.
Reviews and Ratings
(116)
Reviews
(1-6 of 6)- Popular Filters
Companies can't remove reviews or game the system. Here's why
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.
August 24, 2021
scalable and secured cloud Apps within Azure
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
June 10, 2021
Azure - More Money, But Better Service
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
April 29, 2021
Azure serves well in long-term!
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 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.
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).
November 27, 2019
Azure App Service, a great platform - yet a bit complex interface
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.