We mostly use Microsoft Azure App Service for websites, such as content management systems, WordPress, and others, which are built on Azure Web Repair and App Services.
Azure Practice Leader at a computer software company with 5,001-10,000 employees
Good backup and restore, with vertical, horizontal, and DEV scaling options
Pros and Cons
- "I like that it's a ready-to-use, out-of-the-box solution that provides all of the necessary functions for customers, such as codes that can be quickly switched from the production version, or from test and DEV versions to production."
- "It would be fantastic if Microsoft morphed after my exit service, removing it from subscriptions and moving it to different regions, especially for that service."
What is our primary use case?
What is most valuable?
I like that it's a ready-to-use, out-of-the-box solution that provides all of the necessary functions for customers, such as codes that can be quickly switched from the production version, or from test and DEV versions to production.
Quote backup and restore vertical and horizontal scaling, and DEV scaling are all available. In this case, developers do not need to learn and spend their time on the configuration for the platform, just coding and asking to compute, which they need and that configuration, which platform provides them.
What needs improvement?
Price could be reduced.
Particularly with Azure Web Apps. According to their current architecture, moving services from one Azure subscription to another is difficult.
Customers can consume the Azure platform through a variety of subscriptions from various partners, financial visions, current political visions, and so on. Some services on the Microsoft Azure platform can be moved automatically from one subscription to another based on security and financial rules, while others cannot.
Azure Web Apps are the type of service that does not automatically move from subscription to subscription, and region to region. A lot of manual labor must be performed by their organization, customer, and engineers, if necessary.
They must pay too much attention to how to plan this, how to switch off, switch on, on which days, at what times, and so on. A lot of administrative work is done, but it's not very good.
It would be fantastic if Microsoft morphed after my exit service, removing it from subscriptions and moving it to different regions, especially for that service.
For how long have I used the solution?
I have used Microsoft Azure App Service for the last 12 months.
Because it is cloud-based, there is only one version.
Buyer's Guide
Microsoft Azure App Service
November 2024
Learn what your peers think about Microsoft Azure App Service. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
816,406 professionals have used our research since 2012.
What do I think about the stability of the solution?
Microsoft Azure App Service is stable. It's good enough. it's present here, but anyone can take it if it's needed. Especially now, Microsoft offers a very special support program in Ukraine. For example, if a customer needs to support their business processes, they can use any Azure solution for free until the end of the calendar year.
What do I think about the scalability of the solution?
Microsoft Azure App Service is a scalable solution.
How are customer service and support?
We are a technical support team, and we handle all of our support needs. We have not contacted technical support.
I am Microsoft-certified trained. This is why I don't require any additional support assistance; I train others. In other words, every Microsoft commercial partner receives direct Microsoft support. For example, Amazon provides additional information from the traditional partner channel, or by extra support, through premier support contracts. All of them must be present on a commercial basis in order to provide truly high-quality services to customers.
Which solution did I use previously and why did I switch?
I am a technical architect and I have some commercial partners. I work as a system integrator. It is a software, global company that specializes in delivering cloud software, solutions, and services. As for this, I have over 25 years of experience with all stacks, including Azure, AWS, Google GCP, Oracle Cloud, and others. I was very interested in the Zimbra and Microsoft Exchange compilation because, in my opinion, based on my experience and statistics, Zimbra is not widely used in our accounting and based installation. However, one commercial customer inquired about my thoughts on Zimbra in conjunction with Exchange. It was very unfamiliar to me, which is why I attempted to conduct independent research on Zimbra solutions. Who and how are relevant to that question. I don't think we'll implement Zimbra because it's outside of our stack, but it was very interesting to get some perspective on the questions, nothing special, just vision and experience and growth.
We use what our customers requested from the Microsoft stacks, which are mostly infrastructure as a service solutions. It is a very limited number of PaaS installations or implementations, such as Aurora or Microsoft SQL, Azure SQL as a service, web applications on Azure, and so on. Of course, SaaS, such as Office 365, is a good option, but I can't say what other options aren't because the Microsoft stack is our primary commercial platform for our sources. It's fantastic; it provides us with some commercial advantages.
We recently used Azure, virtual machines, virtual networks, and virtual storage, as well as Azure IaaS Stack, Azure Virtual Machines, and Azure Storage.
Because Azure Web Services is based on the Azure IaaS Stack, it is infrastructure as a service. It's a platform as a service that's based on IaaS for some purposes, but our customers don't need the services to bring ready-to-use apps because they don't have a lot of education and institutes. Overall, Qualys solutions are not widely used in Ukraine, for example, by schools, governments, and institutes, due to commercial issues and, in particular, our notice time.
We chose Microsoft Azure App Service because the customer inquired. We are a very commercial company, and if the market or the customer did not request it, we did not provide it. If the customer requests it, we will provide it.
How was the initial setup?
I don't recall any problems with the initial setup at the time because I believe it was adequate. I didn't hear anything about widespread or public knowledge of some issues in that area.
What was our ROI?
Most importantly, not too much. The customer has a high level of financial maturity to value DPI; they do not discuss ROI or other metrics. They simply book on current, can say spending, if current model spending is adequate.
What's my experience with pricing, setup cost, and licensing?
Price could always be cheaper.
It is not about the license fees, but rather about the pay-as-you-go services.
Customers consume varying amounts of quality services and pay roughly the same amount. Where there are different customer sizes, some customers consume $5,000 US dollars per month. I have some customers who pay and consume more than $20,000 US dollars per month, for example. It is determined by customer sizes and requirements, which vary from month to month.
What other advice do I have?
I would advise paying closer attention to the architecture of the solutions. If the architecture is well designed, this will be a very good placement on cloud solutions; otherwise, it will be placed incorrectly. It's a common situation, and owing too much money as it should be.
I would rate Microsoft Azure App Service a nine out of ten.
We are a Microsoft partner.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclosure: My company has a business relationship with this vendor other than being a customer: partner
Specialist Advisor (Data Custodian) at a energy/utilities company with 1,001-5,000 employees
Highly customizable and reliable
Pros and Cons
- "The most valuable feature of Microsoft Azure App Service is customization. It provides the building block from its modularity. You can add what you need with the appropriate code."
- "Microsoft Azure App Service could improve by having better integration and connectivity with other platforms. The solution has good integration with other large companies' solutions but there are smaller service platforms companies where there could be integrated better."
What is our primary use case?
We are using Microsoft Azure App Service in the government sector.
What is most valuable?
The most valuable feature of Microsoft Azure App Service is customization. It provides the building block from its modularity. You can add what you need with the appropriate code.
What needs improvement?
Microsoft Azure App Service could improve by having better integration and connectivity with other platforms. The solution has good integration with other large companies' solutions but there are smaller service platforms companies where there could be integrated better.
For how long have I used the solution?
I have been using Microsoft Azure App Service for approximately seven years.
What do I think about the stability of the solution?
The Microsoft Azure App Service platform is stable. We have a business continuity plan and we need our services to be always on.
I rate the stability of Microsoft Azure App Service a nine out of ten.
What do I think about the scalability of the solution?
Microsoft Azure App Service is scalable.
I rate the scalability of Microsoft Azure App Service a nine out of ten.
How was the initial setup?
The initial setup of Microsoft Azure App Service was easy. There was a logical path in how to do it. I have a development environment because I'm using Dynamics 365.
I rate the initial setup of Microsoft Azure App Service a five out of ten.
What's my experience with pricing, setup cost, and licensing?
The pricing model of Microsoft Azure App Service could be made more clear. There is a scale and range and it can be complicated and convoluted. Some simplification is needed.
I rate the price of Microsoft Azure App Service a seven out of ten.
What other advice do I have?
I would recommend this solution to others.
I rate Microsoft Azure App Service an eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Microsoft Azure App Service
November 2024
Learn what your peers think about Microsoft Azure App Service. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
816,406 professionals have used our research since 2012.
Technical Lead at a tech services company with 1,001-5,000 employees
A multi-tenant environment where customers can load and run applications
Pros and Cons
- "The most valuable feature is the ability to scale the application."
- "The outbound connectivity is not great."
What is our primary use case?
Our primary use case for this solution is hosting web applications which can be Linux or Windows-based. Microsoft Azure App Service is a multi-tenant environment where customers can load and run the application. It is similar to a platform as a service.
What is most valuable?
The most valuable feature is the ability to scale the application. It scales dynamically and comes with two features. If you can find a fabulous feature in the Azure Functions app, it allows you to scale, so you don't need to worry about manually scaling or setting any scaling parameters. Then it automatically does the scaling on its own.
The other feature comes with VNet integration. So we can connect the Microsoft Azure App Service to a VNet so that it can privately communicate with other resources within Azure with a private IP. It also comes with the CDN feature, which can automatically load in some of your configuration files and use it instead of going back to storage to pick that up. It also has awesome features like backup, so you don't need to set up a recovery service, as it automatically does that. So you can back up the existing state of your application in case of any loss. In a nutshell, it has dynamic tools.
What needs improvement?
The outbound connectivity is not great but can be improved because, on virtual machines, the Microsoft Azure App Service uses four or five outbound IPs. So basically, if you want to communicate with an external source, you can use outbound IPs. For example, you must whitelist the outbound IP when communicating with an SQL database externally. However, because it's a multi-tenant environment and other customer applications are being shared on a skills tab, there are always limitations in the smart port. So each customer has a particular allocated smart port, which they should exhaust. It helps to work with the code. Regardless of features like a firewall where they have a hub and an environment they have features like a front door which can increase the smart port's limits to about 64,000. Hence, it will be good to have one IP without needing to add any other infrastructure.
Additionally, they can improve scaling the typical environment in terms of scalability. I believe the limit for the multi-tenant environment is about 20 to 30 maximum on the PV3. So if they can increase that, other than having these significant scaling limits for the Microsoft Azure App Service environment, which is about 200, that will also help.
Also, dedicating one outbound IP for App Service will go a long way.
For how long have I used the solution?
We have been using this solution for approximately three years.
What do I think about the stability of the solution?
The solution is stable.
What do I think about the scalability of the solution?
The solution is scalable.
How are customer service and support?
They have a good support team. We don't think the front-end support is of concern because the front end has to talk to the internal respective application engineering team. Sometimes the core platform issues may take about two months or more. They can answer your queries, and they can help you do investigations.
Additionally, depending on your support package, if you have a premium plan, you get the best because you have support engineers who are intelligent. But you get different services with the pro-direct support plan. There's miscommunication between the front end and the application engineering team. I think that's something that they need to improve. On a premium plan, you get excellent support. I rate support for pro-direct a six out of ten and premium support an eight out of ten.
How would you rate customer service and support?
Positive
How was the initial setup?
The initial setup is easy. You can set it up through the portal, a template, or Terraform. It integrates with other features like Docker so if you have your image in Docker Hub or ECR, you can select the image, and it pulls those images in and runs your application.
It has many features, and other deployment methods like Bitbucket, FTP, DevOps, and GitLab can integrate these things into Microsoft Azure App Service. It is easy to set up because you don't need to start building servers. We also don't need to complete any maintenance.
What's my experience with pricing, setup cost, and licensing?
The price of this solution is competitive. It works as an App Service plan so you can have multiple App Services that are part of a plan. So, for example, you can have about 10 App Services in an App Service plan. It's like a VM, where you have different applications running and you are not charged for all of the applications. However, you are being charged for the plan, so I think it's worth having that setup. At the same time, you need to plan how your costs will be and their ranges of variations. As we call it, SKU is where you can easily factor in so it is okay in terms of price.
One of the best products is the Functions app, which comes with serverless computing in the sense that it gives you about a million transactions for free every month. That is one of the cheapest. So you don't need to worry about how long your function triggers, just that if it scales more than that and performs more transactions, you get charged for it. The exact cost depends on the SKUs.
What other advice do I have?
I rate the solution an eight out of ten.
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Technical Architect at a construction company with 10,001+ employees
Feature-rich, fantastic technical support, and debugging is easier with Application Insights
Pros and Cons
- "Debugging using Application Insights is a valuable feature."
- "Initially, there were some rare instances when the server went down because it was deployed on Linux."
What is our primary use case?
We have our application on Azure and it does a REST call through the App Service, which in turn connects to our on-premises database.
We are using Tomcat and Java in conjunction with this service.
This product is user-friendly and the customization is good.
How has it helped my organization?
We wanted an application that we can use on the cloud to expose services outside of our premises. Azure provides a good platform and the integration is very strong, as well as scalable. You don't have to worry about procuring a server or maintaining it. You simply write the code, deploy it, and Azure takes care of the scaling and everything else.
What is most valuable?
There are a lot of features, such as scaling up and scaling down.
Debugging using Application Insights is a valuable feature.
What needs improvement?
Initially, there were some rare instances when the server went down because it was deployed on Linux. There are some features that are not available on the Linux-based deployment, yet are available on Windows. This is something that I think Microsoft has now caught up.
For how long have I used the solution?
I have been using the Azure App Service for the past year.
What do I think about the stability of the solution?
We haven't had any issues with respect to stability.
What do I think about the scalability of the solution?
It scales very well and in the case of our environment, it is good. We have approximately 20,000 people who are using the application.
How are customer service and technical support?
The technical support is fantastic. We have calls with Microsoft every couple of weeks and they have been very helpful in giving us insights.
Which solution did I use previously and why did I switch?
We were using Oracle prior to Azure, but that was on-premises. When we made the transition to the cloud, the company opted for Azure.
How was the initial setup?
The initial setup is simple.
What's my experience with pricing, setup cost, and licensing?
We have no complaints about the pricing.
What other advice do I have?
Everything looks good and we are happy with this product. It seems to have everything that we need and I haven't seen any limitations. My advice to anybody who is looking at it is that it's a good platform to start building your integrations.
I would rate this solution a ten out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Azure DevOps and Cloud Lead at a consultancy with self employed
Is ideal for lifting and shifting monolithic applications to the cloud but deployment needs improvement
Pros and Cons
- "The most valuable feature is that it's an ideal solution when it comes to lifting and shifting monolithic applications from on-premises to Azure Cloud. It allows for a quick shift into the cloud without having to analyze and design very specific infrastructure and services for monolithic applications hosted primarily on-premises. Let's say that the team does not want to really redesign monoliths in a microservices-based application and that they want to make a quick move towards adopting the cloud tech stack. Then, Microsoft Azure App Service is probably the best option."
- "In terms of room for improvement, ease of deployment would be an area that needs some focus. Azure does provide out-of-the-box deployment features, but I found that deploying to an App Service instance can be better in terms of more tools that could be available to perform a deployment."
What is our primary use case?
One use case was to host the Azure Bot logic code. The Bot logic was hosted on an App Service instance. The other use case was a POC where we were lifting and shifting a monolithic application, a .NET monolithic application, onto the cloud.
What is most valuable?
The most valuable feature is that it's an ideal solution when it comes to lifting and shifting monolithic applications from on-premises to Azure Cloud. It allows for a quick shift into the cloud without having to analyze and design very specific infrastructure and services for monolithic applications hosted primarily on-premises. Let's say that the team does not want to really redesign monoliths in a microservices-based application and that they want to make a quick move towards adopting the cloud tech stack. Then, Microsoft Azure App Service is probably the best option.
What needs improvement?
In terms of room for improvement, ease of deployment would be an area that needs some focus. Azure does provide out-of-the-box deployment features, but I found that deploying to an App Service instance can be better in terms of more tools that could be available to perform a deployment.
For how long have I used the solution?
I've been using this solution since 2020.
It is deployed on a virtual network on Azure.
What do I think about the stability of the solution?
It is stable, but it really depends on the workload that is being shifted and the base service plan that is selected. Because though it is a platform as a service, you do have the option to design a service plan that is adequate for your applications, performance needs, and overall traffic that hits your applications. In terms of it being a platform-as-a-service feature, it is quite stable.
What do I think about the scalability of the solution?
It is scalable. The user base for the Bot service application was about 400 to 500 users worldwide.
How are customer service and support?
The technical support is average, and I would give them a six out of ten.
How would you rate customer service and support?
Neutral
How was the initial setup?
The initial setup is easy and can be done quickly depending on the number of applications being deployed. A single application should not take more than a couple of minutes to deploy.
What's my experience with pricing, setup cost, and licensing?
The cost depends on the App Service plan that you choose. There are a number of tiers available.
What other advice do I have?
If you have a standard enterprise application, for example, for the sake of simplicity, a single server with 50 requests per second, trying to do a lift and shift to App Service is probably a good idea. Bot framework solutions generally tend to use App Service for custom Bot logic, for hosting the custom Bots and the custom logic for Bots. App Service is probably a bit easier in terms of implementation compared to that of other options.
However, for high performance applications that have a heavy load on them and are expected to perform at a certain level of response time, a pure lift and shift to App Service will not work well. You would probably need to choose a higher tier of App Service with a good App Service plan with a certain number of underlying host servers that are servicing it.
Overall, I would rate Microsoft Azure App Service at six on a scale from one to ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
IT Head at Nova Futura
App building service that is used to host and support project management for IT development
Pros and Cons
- "This solution is easy to deploy."
- "The cost management of this solution could be better. We only receive estimations."
What is our primary use case?
This solution is used for project management, source code and IT. It is used primarily for development purposes.
What is most valuable?
This solution is easy to deploy.
What needs improvement?
The cost management of this solution could be better. We only receive estimations.
What do I think about the stability of the solution?
This is a stable solution.
What do I think about the scalability of the solution?
This is a scalable solution.
How was the initial setup?
The initial setup of this solution is very easy.
What's my experience with pricing, setup cost, and licensing?
The pricing and cost of this solution depends on the use and needs of a business.
What other advice do I have?
This is a good solution for those who want to start small looking for a data center that is cloud based.
I would rate this solution a nine out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Enterprise Architect at Prinzhorn IT
A scalable, highly stable solution with easy deployment and competitive pricing
Pros and Cons
- "The most valuable features of this solution are the easy deployment, the scalability, and the Azure maintenance."
- "There is always room for improvement price-wise."
What is our primary use case?
We use this solution for small rep services. We are using it currently for three or four small use cases and it is a perfect fit for all of them, which is why we chose it.
What is most valuable?
The most valuable features of this solution are the easy deployment, the scalability, and the Azure maintenance.
What needs improvement?
There is always room for improvement price-wise.
For how long have I used the solution?
We have been using this solution for about three or four years.
What do I think about the stability of the solution?
I have found this solution to be highly stable.
What do I think about the scalability of the solution?
The scalability of the solution is awesome.
How was the initial setup?
The deployment of this solution is easy.
What was our ROI?
On a scale of one to five, I would rate the ROI of this solution as a three.
What's my experience with pricing, setup cost, and licensing?
On a scale of one to five, with one being expensive and five being competitive, I would rate this solution as a four.
What other advice do I have?
I would rate this solution as a nine out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Expert Architect / Development Leader at Viewnext
Easy to deploy, great for testing, and offers a free version
Pros and Cons
- "The solution overall is very good."
- "There are no issues with the solution."
What is our primary use case?
We’ve used the solution for deploying several applications. We use it for testing purposes. It’s used for testing web apps and developing some proof of concepts.
What is most valuable?
It's easy to deploy web apps through Common Line or Visual Studio Editor, which is useful as I can deploy container solutions.
It is scalable.
The solution overall is very good.
The implementation process is easy. It’s also fast.
It’s stable.
What needs improvement?
There are no issues with the solution. I’m happy with the product.
For how long have I used the solution?
We’ve been using the solution for three years.
What do I think about the stability of the solution?
It's a stable solution if you select the standard sizing. There are no bugs or glitches. It doesn’t crash or freeze.
What do I think about the scalability of the solution?
The solution can scale well.
How are customer service and support?
Technical support is rapid and extremely helpful. Whenever I have questions, they provide feedback very fast.
How was the initial setup?
The product is straightforward to set up and quick to deploy.
What's my experience with pricing, setup cost, and licensing?
I’m using the free version of the solution. I do not pay for licensing.
What other advice do I have?
I’m using the latest version of the solution. I’m an end-user of the product.
I’d recommend this solution. You can start to use App Service immediately. You only need to have a subscription. If you would like to test App Service, then you only need to deploy in a free sizing version, and you can get going.
I’d rate the solution ten out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclosure: My company has a business relationship with this vendor other than being a customer: partner
Buyer's Guide
Download our free Microsoft Azure App Service Report and get advice and tips from experienced pros
sharing their opinions.
Updated: November 2024
Popular Comparisons
Xamarin Platform
Magic xpa Application Platform
Temenos Quantum
Apple Xcode
IBM MobileFirst
Buyer's Guide
Download our free Microsoft Azure App Service Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- Would you choose Microsoft Azure App Service or PowerApps?
- Do you recommend Microsoft Azure App Service?
- When evaluating Mobile Development Platforms, what aspect do you think is the most important to look for?
- What do you look for in a mobile development platform?
- What mobile development platform do you recommend?
- Do you recommend Appium?