Microsoft Azure App Service Reviews

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.

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.

I've been using this solution since 2020.

It is deployed on a virtual network on Azure.

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.

It is scalable. The user base for the Bot service application was about 400 to 500 users worldwide.

The technical support is average, and I would give them a six out of ten.

Neutral

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.

The cost depends on the App Service plan that you choose. There are a number of tiers available.

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.

Microsoft Azure App Service is primarily used to host web-based applications.

Microsoft Azure App Service could improve by having better integration with on-premise solutions.

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

The stability of Microsoft Azure App Service is good.

Microsoft Azure App Service is scalable.

We have customers with 20,000 employees and others with 100,000 employees using this solution.

The support from Microsoft Azure App Service has been supporting my clients.

The setup of Microsoft Azure App Service is easy. The Microsoft Azure App Service can be created within seconds.

The cost of the solution is based on usage. It is less expensive than other solutions.

I would recommend this solution to others.

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

Our primary use case for this solution is hosting applications such as function apps, web apps or API. The solution is deployed on cloud.

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.

The solution can be improved by increasing the number of data centres worldwide.

We have been using this solution for approximately two years.

The solution is stable.

The solution is scalable. Approximately 1,000 people are currently using it across major sites.

We have had a good experience with customer service and support. I rate the service provided a ten out of ten.

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. 

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.

We chose this solution because we support Microsoft Azure.

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.

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.

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.

There are a lot of features, such as scaling up and scaling down.

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. 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.

I have been using the Azure App Service for the past year.

We haven't had any issues with respect to stability.

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.

The technical support is fantastic. We have calls with Microsoft every couple of weeks and they have been very helpful in giving us insights.

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.

The initial setup is simple.

We have no complaints about the pricing.

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.

We use Azure App Service for both app development and deployment. Sometimes, we use it for testing, and we also have several products running in production on the platform.

One valuable feature of Azure App Service for us is its integration with Azure DevOps, which we heavily rely on in our development process. It is user-friendly once you understand how it works, although getting to that point can be a challenge. Additionally, Azure App Service offers excellent integration with Microsoft infrastructure and developer solutions.

In terms of improvement, the technical support could be better.

I have been working with Microsoft Azure App Service for almost six years.

We have faced reliability issues due to configuration issues on our end, not the technology itself. While Azure App Service provides information on problems, sometimes it is not sufficient, and resolving issues can be time-consuming.

In terms of scalability, we haven't encountered any issues with Azure App Service. 

The support I have received, mostly from individuals in India, hasn't been very helpful. They tend to send long emails with lots of links, which often don't directly address my specific issue. This can be frustrating and time-consuming, as it doesn't efficiently solve the problem at hand. Azure App Service might offer better support with higher-priced plans, but those might be too costly for smaller external companies like ours. I would rate the support as a three out of ten.

Negative

I have used SolarWinds along with Azure App Service for web application development.

Installing Azure App Service has been challenging at times. Whether deploying through Azure pipelines or directly from Azure, the process can be time-consuming due to configuration complexities. We have encountered instances where resolving issues took days or even two to three weeks to complete the deployment.

Microsoft offers various pricing plans and licensing options, which initially seem reasonable, especially for small companies like ours. However, as we grow, the pricing can become less flexible. We pay for Azure monthly, while some licenses, like the Action Pack, are paid annually.

Overall, I would rate Azure App Service as an eight out of ten. It is a good tool but could be more user-friendly.

We are a reseller of Microsoft services and deliver this product to our customers. 

It is for hosting web and mobile applications and data. When we are integrating different applications, we need to connect them with Microsoft Azure services for integration.

We like that it's a close environment where we can do a lot of things. It integrates well across Microsoft products. 

It's stable. Microsoft recently announced it will be adding a local cloud into the UAE.

The solution can scale.

They need to be more transparent in terms of the scalability of the product. It's not clear how many users can use it in tandem. The non-functional information about the platform should also be readily available. 

Unlike AWS, which has many offerings, Microsoft's choices are more limited. AWS also has manuals and videos in order to clarify how things work. Microsoft needs more of that. 

Jordan and Saudi Arabia do not yet have local in-country clouds. 

The solution is somewhat expensive. They have a lot of competition from open-source rivals and need to make their offering more competitive somehow. 

My background is in Microsoft technology, and I have been working with Microsft for five years and with this particular solution for almost three years. 

It's extremely stable and reliable. There are no bugs or glitches, and it doesn't crash or freeze. 

We haven't had any issues with scaling just yet. I haven't hit any limitations. We work with both SMEs and enterprises, and it has met the needs of both. 

I handle pre-sales of software and therefore do not deal with technical support. 

It is moderately easy to deploy. A company would require some technical help or know-how. There's maybe 50% complexity in general. Half is hard, half is easy. 

Our support team is able to assist clients in setting up the solution. 

The price is relatively high compared to other platforms. I can't speak to the exact pricing, however. 

There may be some ancillary services that may cost more. They don't have a comprehensive plan, yet they charge for everything. 

We're a partner.

I'd rate the solution eight out of ten. 

We are using Microsoft Azure App Service in the government sector.

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.

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

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.

Microsoft Azure App Service is scalable.

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

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.

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.

I would recommend this solution to others.

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

One of our reasons to use the product is its cloud service. Our usage is mainly on the cloud and we like the benefits that we can get from the cloud. You can easily do the literal shift of your application easily. You can jump into the cloud very quickly. 

If you are not using the product properly, then it can cost you a lot of money. Hence, you need to make sure that you choose the services wisely. You need to make sure that you have a budget and have some alerts associated with it. The tool's cost can easily go high if you don't consider these things properly. You need to review your existing subscription.  

I have been working with the product for more than two years. 

The product is quite stable. 

The solution is scalable both vertical and horizontal. You should be specific about the Linux or Windows environment. 

The tool's support is good. Sometimes, you need to make sure of the people who are supporting you. Microsoft support can get delayed easily. You need to be in regular contact with the account managers of your account on the Microsoft side so that you can escalate things. Typically, we don't use support and use it only for production issues which require urgency. 

Neutral

The tool's setup is easy since there is a lot of free documentation from Microsoft available. You need to be part of the training as well. The tool's deployment is super quick and gets completed in five minutes. 

The solution is worth its money. 

I would rate the product's pricing a five out of ten and is subscription based. 

I would rate the product an eight out of ten. I would advise people to go with the trial version since you can use most of the functionality in the trial version.