Microsoft Azure App Service Reviews

I primarily use Microsoft Azure App Service to deploy Python-based applications. It was majorly used for deployment purposes only. When you buy a virtual machine, you need to do lots of configuration, but using Azure App Services gives you lots of flexibility. It's easy - you just upload the code and do a few clicks.

Deployment is really quick, which eliminates the need for a separate team dedicated solely to deployment. A simple software engineer can handle it, making live updates seamless and reducing the need for thinking cycles.

The ability to deploy applications directly from my Visual Studio Code without needing to access Azure is helpful. Additionally, scalability is straightforward, and you can quickly adjust the resources to meet demand.

The interface is a bit complicated and not straightforward. Documentation is not well-organized, making it difficult to find current and relevant information. 

The logging process using stream is not always accurate, and the pricing is quite high, often twice the price of virtual machines. 

Additionally, in terms of scalability, they do not offer the option to have two different virtual machines with separate configurations.

I have been using Microsoft Azure App Service for more than a year now.

I have never faced any stability issues in my last year of usage, so I would rate its stability nine out of ten.

Scalability is easy and helps improve application performance. However, there is no option to configure different virtual machines with various configurations, like one with eight GB of RAM and another with 16 GB.

I have had poor experiences with customer service. Although I have rarely required support, whenever I created a ticket, I never received an answer. I would rate their support one or two out of ten.

Negative

I used Amazon AWS virtual machines before. However, Azure App Service is much better, although it's costly.

The setup is quick and easy, taking a maximum of five minutes if you know which resources to choose.

The pricing is very high. It's approximately twice the cost of AWS virtual machines. While the deployment feature is convenient, the costs make it unaffordable for many in the industry.

I recommend Microsoft Azure App Service because it is easy to deploy. However, the pricing could be a deterrent for many users who might prefer manual configurations at a cheaper rate.

I'd rate the solution seven out of ten.

The main use cases for Microsoft Azure App Service are mostly related to creating front-end applications, which would connect with a document bot we were developing.

Regarding its automatic scaling and load balancing features, those capabilities are really effective. Certain philosophies are inspired from Kubernetes as well, which makes these features essential and beneficial.

In terms of handling traffic spikes and maintaining optimal performance, it has been highly effective.

I have used its integration capabilities with Azure Functions and Azure databases, specifically Redis, and the integration process was straightforward.

I am familiar with its built-in security features such as authentication and SSL certificates. We use NVA and have integrated it with most of our in-house applications. We are also planning to use NVA for our product where we are trying to offer our product as a PaaS offering.

I evaluate the effectiveness of Microsoft Azure App Service's monitoring tools and diagnostic capabilities as good. Though as an architect, I wouldn't recommend any kind of vendor lock-in, if you are comfortable with the budget, Azure Insight is beneficial as it comes with all monitoring capabilities out of the box.

Microsoft Azure App Service could be improved if it had AI-based integration, which would be much more beneficial. Currently, there's a trend toward prompt-based deployment where one can create a pipeline based on simple English prompts. The system should handle all the setup, allowing users to review and complete the deployment. This kind of integration is available in GCP, but I'm unsure about its availability in Azure, though it should be there.

The price is an issue relevant only for Azure Firewall because until we figured out the policies, there were issues. Once we determined the required policies, we were able to budget the pricing and set up alerts on the pricing part.

For Microsoft Azure App Service, we did not have the same pricing issues. App Service is straightforward, and most of our usage was related to smaller applications, primarily POCs. We didn't encounter pricing issues because we had the option to start the application. For production-based applications, fine-tuning might be necessary, and pricing-related conflicts might arise.

We have not used the hybrid and multi-cloud capabilities of Microsoft Azure App Service to deploy applications across different environments.

Overall, Microsoft Azure App Service is a very effective tool. On a scale of 1-10, I rate this solution a 10.

We have been using Microsoft Azure App Service to host small apps. We have either hosted applications on VM directly or we use Microsoft Azure App Service to host our applications. We have various applications for sales, service, and other purposes where we're using Microsoft Azure App Service.

Within one Microsoft Azure App Service, we can have multiple applications hosted. We thought that it would help save costs instead of using VM, as we can use Microsoft Azure App Service to host multiple applications.

We use Microsoft Azure App Services extensively. It is easy to integrate with other services through simple drag and click functionality.

We have been successfully integrating it with SQL databases and Azure Functions.

Auto-scaling is helpful for Microsoft Azure App Service. However, recently, we are seeing that Microsoft Azure App Service is consuming a lot of resources. We plan to evaluate whether we should switch to containers or use AKS instead.

For Microsoft Azure App Service, they need to make it less resource-intensive or less costly, because from a cost perspective, we are seeing that it is proving more expensive for us.

We have been working with Microsoft Azure App Service for two to three years.

The scaling ability for Microsoft Azure App Service is satisfactory, warranting an eight out of ten rating. However, if we were to switch to containers, that would be better as we could scale much faster and easier.

Support for Microsoft Azure App Service varies in quality. Because we have premium support, we get responses quickly. However, many times we have observed that they send someone who cannot solve the issue immediately and takes some time. An expert typically arrives after three or four hours to work on the problem. On a scale for support, this warrants a six or seven out of ten.

The setup process for Microsoft Azure App Services is simple.

I have not tried other products, but I think Google or AWS would have good competitors for Microsoft Azure App Service.

We have been integrating Microsoft Azure App Service with SQL databases and Azure Functions. Based on our experience, we rate Microsoft Azure App Service a 7 out of 10.

The use case that we have is that we have multiple different APIs that we expose externally for one of our products. We deploy those APIs into these app services.

The product is easy to maintain and deploy.

I do not have notes for improvements.

I have used the solution for around five years.

The customer service is pretty good. I have talked to them a couple of times, and they were able to resolve issues.

Positive

I did use this solution as well in my previous job.

The initial setup is straightforward. They have pretty good documentation.

You don't need people for the implementation team. You can automate the process.

If I compare this solution to AWS, it's cheaper, so it's better.

I personally prefer Azure. I haven't used much of AWS, but Microsoft made it kind of more simple. AWS is kind of complex, frankly. The reason is that AWS is more mature. They have a lot of other things.

I would rate the product ten out of ten.

We primarily use the solution for MDM management. 

We primarily use the solution for application deployment. It is very easy to use. 

The solution is very simple to set up. 

It is stable and reliable. 

The solution can scale.

Pricing is moderate.

So far, it has been good. We haven't used it for that long and haven't had any issues. 

The pricing is average. It could be lower.

There are still some improvements that could be leveraged in the future to make it even better.

The response time could be better.

We've used the solution for about one year. We've used it quite often.

This is a stable, reliable product. We haven't had issues. There are no bugs or glitches, and it doesn't crash or freeze. I'd rate stability ten out of ten. 

We have 600 people using the solution.

It is a scalable product. I'd rate scalability ten out of ten. 

I've never contacted technical support. I'm not sure how helpful they would be.

I did not previously use a different solution. We chose this solution to help improve the daily management of mobile users. 

The initial setup and implementation have been quite straightforward. It is not complex. I'd rate the ease of setup ten out of ten. It's very easy. 

The deployment process was very good. It took maybe a few hours, including lead time. 

We have 500 people deploying and maintaining the solution. 

We've witnessed ROI while using the solution. It's worth the purchase. 

The pricing is decent. It's not overly expensive. I'd rate the affordability five out of ten. The pricing is average. 

We may have looked at other options as well. We did also look into Office 365. 

We are end-users and customers. 

I'd rate the solution six out of ten. 

It's useful for companies that use iPads. 

I am using Microsoft Azure App Service for running web applications.

The most beneficial aspect of Microsoft Azure App Service is its automated DevOps deployment, which includes configurations that ensure secure connections to key vault and database resources.

Extended uptime and improved speed would be beneficial for both development purposes and the free tier of the service. Currently, the uptime is limited to a few hours per day, which could be increased to provide more continuous and efficient usage.

I used Microsoft Azure App Service within the last 12 months.

Microsoft Azure App Service is highly stable.

I rate the stability of Microsoft Azure App Service a ten out of ten.

The solution is scalable. 

We have approximately 20 people using the solution.

Microsoft Azure App Service offers multiple tiers that can be scaled out as per the specific requirements of the developer or team. Choosing the appropriate tier depends on the performance and load requirements of the website.

I rate the scalability of Microsoft Azure App Service an eight out of ten.

Often, the team responsible for supporting a particular solution may have biases towards it and may encourage customers to use it, even if it may not be the optimal solution for their needs. Additionally, the support attempt to upsell solutions that are not desired.

I rate the support of Microsoft Azure App Service an eight out of ten.

Neutral

I have previously used WebLogic, Tomcat, Red Hat, and JBoss. There are a lot of application servers, which we used to run on-premise. We switched from these solutions to a cloud offering. Many companies are moving to the cloud.

The initial setup of Microsoft Azure App Service is straightforward and easy. It is helpful to read the documentation. It takes a few minutes to deploy.

I rate Microsoft Azure App Service an eight out of ten.

One person is able to do the deployment.

We received a return on investment using  Microsoft Azure App Service.

As you move up the license tiers it becomes expensive.

I rate the price of  Microsoft Azure App Service a seven out of ten.

The solution requires one person for maintenance. Some of their responsibilities are updating the code and deploying the web app.

If you need to quickly set up and run an application without incurring any setup costs, this is the way to go. With this approach, you don't need to install or run anything on-premise. Simply create the application and start using it - the setup process is straightforward and fast.

I rate Microsoft Azure App Service a ten out of ten.

The most valuable features of Microsoft Azure App Service are its vertical and horizontal scaling, along with its ability to throw a docker image.

Microsoft Azure App Service needs some improvement in the scaling area. The solution should also be able to easily host apps that don't have an HTML front end.

I have been using Microsoft Azure App Service for ten years.

I rate Microsoft Azure App Service ten out of ten for stability.

Around 1,000 users use Microsoft Azure App Service in our organization.

I rate Microsoft Azure App Service a nine out of ten for scalability.

The solution's initial setup is pretty simple. I rate Microsoft Azure App Service an eight out of ten for the ease of its initial setup.

Microsoft Azure App Service's deployment is very quick and could take minutes since it is on an app-by-app basis. The solution's deployment requires minimal staff.

I rate Microsoft Azure App Service a seven out of ten for pricing.

Before choosing Microsoft Azure App Service, we evaluated AWS. Ultimately, we decided to go with Microsoft Azure App Service because it natively works much better with dot net applications than AWS. Not that AWS does it badly, but Microsoft Azure App Service is much more up-to-date.

Microsoft Azure App Service is deployed on-cloud in our organization.

I advise users to think about the types of applications they want to host on the cloud and adapt it for the cloud instead of doing a lift and shift.

Overall, I rate Microsoft Azure App Service an eight out of ten.

We are using Microsoft Azure App Service in systems, such as government, credit loan, and app services.

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. 

In an upcoming release, mobile device usage could be a better experience.

I have been using Microsoft Azure App Service for approximately five years.

The solution is highly stable.

I rate the stability of Microsoft Azure App Service a ten out of ten.

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.

The initial setup of Microsoft Azure App Service is simple. 

The price of the support could improve. It is expensive.

I rate the price from Microsoft Azure App Service a one out of ten.

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.

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.