My use case for Microsoft Azure App Service is to deploy web solutions faster and easier online. Rather than setting up my servers and worrying about the need to set up the infrastructure, the OS, and the run time, I use Microsoft Azure App Service for faster deployment and to get my solutions to the market at a faster rate.
Cloud Engineer at Tek Experts
Can run a function faster and more frequently, is easy to utilize, and only requires minimal setup
Pros and Cons
- "I've used Microsoft Azure App Service quite a lot, and what I like best about it is that it's a serverless HAM, which is a feature that can run a function, a single function, but faster and more frequently without needing any other assistance. This has been what I found most valuable in Microsoft Azure App Service, the serverless option that's very easy to utilize, and you only need a minimal setup to use this and to enjoy the functionalities required, so the solution gives me a lot of comfort whenever I'm using it."
- "Customers love it when a solution is affordable, but with Microsoft Azure App Service, you can start and stop it, and when you stop it, it won't be reachable and it won't be available, yet you're still being charged for it. You'll still be charged even if the solution isn't accessible because Microsoft Azure App Service runs on a shared virtual machine that keeps on running, so if there's a way to work this out, it'll be a great improvement to only pay for what you use. The solution should have no hidden cost and no extra charge when it's stopped. This is what needs improvement in Microsoft Azure App Service."
What is our primary use case?
What is most valuable?
I've used Microsoft Azure App Service quite a lot, and what I like best about it is that it's a serverless HAM, which is a feature that can run a function, a single function, but faster and more frequently without needing any other assistance. This has been what I found most valuable in Microsoft Azure App Service, the serverless option that's very easy to utilize, and you only need a minimal setup to use this and to enjoy the functionalities required, so the solution gives me a lot of comfort whenever I'm using it.
What needs improvement?
Customers love it when a solution is affordable, but with Microsoft Azure App Service, you can start and stop it, and when you stop it, it won't be reachable and it won't be available, yet you're still being charged for it.
You'll still be charged even if the solution isn't accessible because Microsoft Azure App Service runs on a shared virtual machine that keeps on running, so if there's a way to work this out, it'll be a great improvement to only pay for what you use. The solution should have no hidden cost and no extra charge when it's stopped. This is what needs improvement in Microsoft Azure App Service.
For how long have I used the solution?
I've been using Microsoft Azure App Service for four years now, but professionally, this is my second year to use it.
Buyer's Guide
Microsoft Azure App Service
October 2024
Learn what your peers think about Microsoft Azure App Service. Get advice and tips from experienced pros sharing their opinions. Updated: October 2024.
814,649 professionals have used our research since 2012.
What do I think about the stability of the solution?
Microsoft lives up to its word. For example, the SLA it promised is 99.7%, and to the best of my knowledge, Microsoft Azure App Service has been able to reach that percentage without any global outage from any of the services and underlying infrastructure that power it. The solution is available 100% throughout its lifetime.
What do I think about the scalability of the solution?
Microsoft Azure App Service is very scalable, and it's built in such a way that it encourages flexibility in scaling. You can grow from a single instance to thirty instances, and you can increase from 5GB RAM to over 30GB RAM.
Microsoft Azure App Service is designed so you can start small and expand as your customer base grows. It's built around that ideology and it's been living up to that ideology. The solution is defined scalability-wise, and it's practical in both approach and usage.
How was the initial setup?
The setup for Microsoft Azure App Service is very straightforward. All you have to do is navigate to the portal, search for the App Services, curate one, give it a name, select a location, region, and resource group, then customize the number of RAM you want. Do you want a disk to be attached to it? Do you want to do some modern networking parameters which are not requirements?
The basic requirements for setting up Microsoft Azure App Service are very straightforward, so anyone who can power his computer can get started with.
You also have several deployment options to choose from for Microsoft Azure App Service which would make life easy. You can deploy from your existing repository, or you can upload your code directly, so for me, the setup is quite easy for the solution.
How long Microsoft Azure App Service deployment usually takes depends on the content, specifically the size of the content you want to deploy to it. At most, if you have a one-page website, the solution takes less than five minutes to deploy, which is quite fast, so you can get your sites up and running in less than twenty minutes with the setup and deployment, so the process is considerably okay.
What's my experience with pricing, setup cost, and licensing?
The pricing for Microsoft Azure App Service is per hour, and you're billed per hour, and it depends on the plan you're using. Each plan can host up to a minimum of four to eight applications at a time, so the pricing is quite okay with how I use Microsoft Azure App Service currently, but with the little testing I've done, I saw that some other regions tend to be costlier than others. If the same SLE is delivered for all services, there should be a way to make the prices parallel across regions. Having more transparent pricing for Microsoft Azure App Service would give customers more comfort.
What other advice do I have?
Microsoft Azure App Service can be used by a lot of people, but either the cloud engineer or the infrastructure engineer should be in charge of it because the solution relates to a lot of infrastructures and other resources such as storage, databases, networking, firewalls, and it can even relate to APIs and other resources outside the cloud environment. A lot of people can work on Microsoft Azure App Service, but it's best handled by the cloud engineer who has an understanding of how to implement the relationship with other resources.
I've worked on Microsoft Azure App Service for four years, and I have enough experience to orchestrate, manage, and maintain it.
My advice to anyone looking to use Microsoft Azure App Service is that you should try it and see the power of getting your applications out at a faster rate. It can get your application to speed up in less than twenty minutes, and it can handle between thirty to fifty thousand users at a time. You can try Microsoft Azure App Service while you're starting, then you can keep scaling until you need more resources or more solutions that can help you with your workload. Try Microsoft Azure App Service out, so you can see for yourself what it can give you. This is the best way to enjoy its features and benefits.
My rating for Microsoft Azure App Service is nine out of ten.
My company is a partner of Microsoft Azure App Service.
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
DevOps Consultant at Deloitte
A complete solution, with a large number of features that are easy to use, but require some prior learning to fully benefit from
Pros and Cons
- "The feature I find most valuable is the 'Diagnose and Solve problem' function. This not only allows us to fix a problem, but also to generate analytics on why the issue occurred."
- "I would like to see some improvement in the UI/UX design, to make navigation of this solution more user friendly. For example, it could contain more explicit information on each of the features."
What is our primary use case?
We use this solution in a very large number of areas, such as for functional apps, web apps, to trigger HTTP requests, for web API integration. This solution has a vast array of features.
What is most valuable?
The feature I find most valuable is the 'Diagnose and Solve problem' function. This not only allows us to fix a problem, but also to generate analytics on why the issue occurred.
I also find the application insight feature to be essential for use in our production environment.
What needs improvement?
I would like to see some improvement in the UI/UX design, to make navigation of this solution more user friendly. For example, it could contain more explicit information on each of the features.
There should also be some development on the architectural flow of this product, to show application dependencies across the network. This would help with fixing issues that may impact other areas.
For how long have I used the solution?
We have been using this solution for four years.
What do I think about the stability of the solution?
We have found this to be a fairly stable solution so far.
What do I think about the scalability of the solution?
This is an easily scalable solution.
How are customer service and support?
The technical support for this product is very good, with SLA's provided for when issues are raised. There is also a lot of online support available through the Microsoft community pages, forums, and downloadable guides.
How would you rate customer service and support?
Positive
How was the initial setup?
The initial setup of this solution isn't complex, but it is time consuming. There is a lot of documentation to go through before implementing this solution, to ensure that it is fit for purpose once deployed.
What's my experience with pricing, setup cost, and licensing?
The pricing for this solution is set in tiers, with the overall cost depending on the features that are required. I would advise organizations to have a detailed look at the functions they need, to ensure that they are in the correct pricing tier.
What other advice do I have?
I would rate this solution 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: My company has a business relationship with this vendor other than being a customer: Partner
Buyer's Guide
Microsoft Azure App Service
October 2024
Learn what your peers think about Microsoft Azure App Service. Get advice and tips from experienced pros sharing their opinions. Updated: October 2024.
814,649 professionals have used our research since 2012.
Chief Executive Officer at PROJECT MOONSHOT
Beneficial application grouping, highly reliable, and effective autoscaling
Pros and Cons
- "The most valuable feature of Microsoft Azure App Service is autoscaling and resource grouping. Additionally, the integration works well, it is easy to do."
- "Microsoft Azure App Service has a lot of complexity because there are a lot of options and functionality. It is simple to become confused, there are many technical elements to learn before you can utilize the solution. If they could make the solution easier to use it would be a benefit."
What is our primary use case?
We are using Microsoft Azure App Service in systems, such as government, credit loan, and app services.
What is most valuable?
The most valuable feature of Microsoft Azure App Service is autoscaling and resource grouping. Additionally, the integration works well, it is easy to do.
What needs improvement?
Microsoft Azure App Service has a lot of complexity because there are a lot of options and functionality. It is simple to become confused, there are many technical elements to learn before you can utilize the solution. If they could make the solution easier to use it would be a benefit.
In an upcoming release, mobile device usage could be a better experience.
For how long have I used the solution?
I have been using Microsoft Azure App Service for approximately five years.
What do I think about the stability of the solution?
The solution is highly stable.
I rate the stability of Microsoft Azure App Service a ten out of ten.
What do I think about the scalability of the solution?
With all the deployments we have in many companies there are only a few users that use it.
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 is simple.
What's my experience with pricing, setup cost, and licensing?
The price of the support could improve. It is expensive.
I rate the price from Microsoft Azure App Service a one out of ten.
Which other solutions did I evaluate?
I did compare this solution with Amazon AWS and Amazon and Amazon EC2. They are all comparable solutions. What stands out the most in Microsoft Azure App Service is the speed. Selecting the best solution will also depend on the use case.
What other advice do I have?
We utilize Azure Cosmos DB, which has a distinct architecture compared to other services. Initially, we were concerned about the high costs associated with it since every document incurs charges due to Azure's containerization of every collection. However, we discovered that running it in a single container eliminates this cost.
I rate Microsoft Azure App Service a nine out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Azure App Service Technical Supprt Engineer at Tek Experts
A great solution for hosting web apps, and it is very easy to use
Pros and Cons
- "It is the best because it's easy to use, and there's a plan for every type of workload."
- "Sometimes customer service and support can be challenging."
What is our primary use case?
Our primary use case for this solution is for hosting web apps so people can deploy this application and host it on an app service.
What is most valuable?
We have found the scalability feature most valuable. When you host an application on Microsoft Azure App Service and have a lot of users, there are times that there will be high traffic. High traffic is when many people try to access the Microsoft Azure App Service simultaneously. So Microsoft Azure App Service can scale up to meet the demand of those trying to access it. It has been at approximately 98% availability, and if any maintenance is required, it will notify you. You can find an alternative solution and use multiple instances to mitigate the downtime.
What needs improvement?
For now, I don't think there are any improvements to highlight.
For how long have I used the solution?
We have been using this solution for approximately a year and a half.
How are customer service and support?
We have had a fun experience with customer service and support, but sometimes customer service and support can be challenging. However, all the challenges we face are related to technology.
How was the initial setup?
There are two options for setting up the CLI shop and the portal. In terms of the portal, you can easily create an app service from the Azure portal. Some people are comfortable using the CLI shop, and some don't like going to the portal and creating the app service. I believe Azure did very well in that aspect.
What's my experience with pricing, setup cost, and licensing?
The pricing is quite fair because of its scalability. Before you choose the type of plan you want, you should look at the workloads that the apps have and what your organization needs. For example, if you have minimal traffic, you can use the basic plan. There's a plan for every type of workload which determines the subscription cost.
What other advice do I have?
I rate this solution nine out of ten. The solution is good. If somebody is considering using Microsoft Azure App Service, it is the best because it's easy to use, and there's a plan for every type of workload. Some features can give you certificates for the domain. If you already have an existing domain, you can bring it in to do it from Azure. Additionally, you can buy your domain and bind it to Azure, but if you already have an existing third-party domain, you can also use it with Azure.
Disclosure: My company has a business relationship with this vendor other than being a customer:
DevOps Engineer at Naxxum
A user-friendly platform that streamlines the development and hosting of various web and mobile applications
Pros and Cons
- "The primary and standout feature is ease of deployment."
- "Having a surplus of tutorials from Microsoft, rather than relying solely on documentation or features from other sources like YouTube, can be beneficial."
What is our primary use case?
It simplifies the deployment of applications, including those built with technologies like .NET or UCS, making it particularly valuable for microservices applications. It streamlines the deployment process, allowing developers to easily deploy and manage their applications without requiring dedicated DevOps engineers.
What is most valuable?
The primary and standout feature is ease of deployment.
What needs improvement?
Having a surplus of tutorials from Microsoft, rather than relying solely on documentation or features from other sources like YouTube, can be beneficial.
What do I think about the stability of the solution?
It offers excellent stability capabilities.
What do I think about the scalability of the solution?
It offers configurability through the Azure portal. Adjusting resources such as CPU or memory is a straightforward process, making it easy to scale up or down based on your requirements. We manage multiple projects. Each project, whether it's a toll-free initiative or any other, typically involves three or four developers who contribute to the content and development processes.
What about the implementation team?
Deployment is a straightforward process: after coding, you package the application into a folder, compress it into a ZIP file, and execute a command line with the ZIP file's path. This command includes the ZIP file's location, and Azure App Service takes care of running the application and exposing it without any further complexities. I can handle the deployment on my own.
What's my experience with pricing, setup cost, and licensing?
The cost is reasonable.
What other advice do I have?
Overall, I would rate it 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.
Enterprise Architect at Tata Consultancy Services
Flexible, configurable, and easy to use
Pros and Cons
- "The cost is reasonable."
- "From an IoT use case perspective, we're all good, however, we should have additional plugins."
What is our primary use case?
We have used App Services to integrate a lot of solutions, to bring content from a different domain or maybe a different data source.
We were using a lot of Microsoft Azure services to build. We were also leveraged to deploy non-SAP solutions like Python Machine Learning IOTs, using these App Services to bring solutions into SAP.
We were doing one POC for one of the last customers where we had to integrate mobile solutions and IoT. We were using App Services to build those IOT components, retrieve data, and integrate with SAP.
We were using some temperature readings for our supply chain logistics company. Once we read temperatures, we'll push it to the App Service, and App Service will internally push it to the digital twins. From there, we get the events and consume those events into a function, and then whatever the functions read will be pushed into the DB.
What is most valuable?
The best feature is the latency is significantly less. The functions which are provided in this App Services app work very fast, and there are no latencies that we see. The realistic data allow us to configure analytics on top of it, and it is very fast.
It is easy to set up.
The cost is reasonable.
We've found the product to be stable.
What needs improvement?
Recently, we have used some scheduling and event management. From an IoT use case perspective, we're all good, however, we should have additional plugins.
For how long have I used the solution?
We started using the solution in 2021.
What do I think about the stability of the solution?
It is stable so far. We have not received any challenges during our implementation.
What do I think about the scalability of the solution?
Azure was very fast in doing scalability from a user management perspective. Whenever you add a new user, it automatically aligns, and then the license gets adjusted automatically.
We have a few thousand users. Pretty much everyone uses it.
Which solution did I use previously and why did I switch?
We began using the solution due to the fact that digitalization is becoming normal now, and we have to integrate a lot of non-SAP solutions. App Services gives a lot of flexibility for us to bring data from any data source and push it to enterprise services, which we want to consume.
How was the initial setup?
The solution is easy to set up. It's very easy. it's not complex at all.
It only takes about a week to deploy a bare-bones product. To have an end-to-end solution, it only takes 20 to 30 days.
What's my experience with pricing, setup cost, and licensing?
From a licensing cost perspective, Microsoft Azure, compared to other cloud services providers, is competitive and reasonable from an implementation point of view.
The Azure license is based on usage. It's pay as you. We pay for what we consume.
What other advice do I have?
We are partners with Microsoft.
I'm not sure what version of the solution we're using.
I'd advise users to try out the product.
I would rate it eight out of ten. It is flexible and easy to use. Configuring and deploying are also quick and easy.
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Cloud Engineer at Tek Experts
A solution with great documentation and the ability to scale out infrastructure
Pros and Cons
- "It allows you to host your App Service on Azure and provides the ability to bypass online."
- "Can be improved by increasing the number of data centres worldwide."
What is our primary use case?
Our primary use case for this solution is hosting applications such as function apps, web apps or API. The solution is deployed on cloud.
What is most valuable?
The ability to scale the App Service is very valuable. It allows you to host your App Service on Azure and provides the ability to bypass online. Additionally, it offers the ability to autoscale. That ability to scale out the infrastructure or the instances hosting the application is also a very good advantage in Azure which is cost-effective.
What needs improvement?
The solution can be improved by increasing the number of data centres worldwide.
For how long have I used the solution?
We have been using this solution for approximately two 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. Approximately 1,000 people are currently using it across major sites.
How are customer service and support?
We have had a good experience with customer service and support. I rate the service provided a ten out of ten.
How was the initial setup?
The initial setup is neither easy nor difficult. However, it is simplified because documentation is provided to guide you. The documentation instructs how to host the applications and manage operations. In addition, the documentation aids in training and familiarizing people with the platform's requirements.
What's my experience with pricing, setup cost, and licensing?
There are different licensing options available, and we use the pay-as-you-go option. A student subscription is available with its requirements, other payment plans, and additional support. A free trial option is available to try out the platform and see how it works before subscribing.
Which other solutions did I evaluate?
We chose this solution because we support Microsoft Azure.
What other advice do I have?
I rate this solution a ten out of ten. The solution is good but can be improved by increasing the number of data centres worldwide. I advise future users to understand how to use the platform and utilize the documentation provided online, which offers guidance.
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
A scalable solution with user-friendly Power Apps
Pros and Cons
- "The Logic Apps and Azure functions are very robust."
- "The setup is complex if you have no experience."
What is our primary use case?
We use this solution for everything I do. We use it on e-commerce platforms and for business activities. Currently, we're using the latest version of the App. However, we used the e-commerce version between 2019 and 2020.
What is most valuable?
The most valuable feature is the Power Apps because it is very user-friendly. In comparison, the Logic Apps and Azure functions are very robust.
What needs improvement?
I can't pinpoint a specific feature that can be included in the next release because Microsoft is making new changes to the app every day. Currently, everything works perfectly.
For how long have I used the solution?
We have been using this solution for five years. I am a Cloud Solution Architect with TCS, primarily on the Azure front. I research different types of Power Apps. I focus on POCs and deal with architecture data.
What do I think about the stability of the solution?
This solution is stable as we haven't faced problems working with it yet.
What do I think about the scalability of the solution?
This solution is scalable.
How are customer service and support?
I can't comment on my experience with the customer service and support team because we connect directly with Microsoft whenever we have any issues.
How would you rate customer service and support?
Positive
What's my experience with pricing, setup cost, and licensing?
It is easy to set up if you have experience and knowledge working with it, but the setup is complex if you have no experience.
Regarding pricing, I can't comment on pricing because I don't deal with issues related to pricing.
What other advice do I have?
I rate this solution an eight out of ten. My advice would be to gain experience, get an MSN license and practice before working in production environments.
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: October 2024
Popular Comparisons
Microsoft Power Apps
Pega Platform
Oracle Application Express (APEX)
ServiceNow Now Platform
Oracle Visual Builder Cloud Service
Xamarin Platform
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?