Microsoft Azure App Service Reviews

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.

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.

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.

We have been using this solution for four years.

We have found this to be a fairly stable solution so far.

This is an easily scalable solution.

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.

Positive

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.

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.

I would rate this solution an eight out of ten.

I use this solution to learn about the application development technology and platform and be able to recommend it to my employer.

I'ts not being used yet.

I particularly appreciate that this is a very straightforward and easy solution to use.

I would like to see some significant improvement in the technical support provision for this solution. 

I have been working with this solution for around six months.

I have found this to be a mostly stable solution during my time using it.

This is a very easily scalable solution with practically unlimited growth potential.

The technical support for this solution is terrible.  I regularly experience delays in response times when I raise and issue, and have often had occasions when no response at all has been given.

Negative

The initial setup of this solution is very straightforward.

I implemented this solution myself, as it is for personal use.

I would recommend that potential users of this solution enroll in some kind of formal training, perhaps from a Microsoft partner. They should also be prepared to keep up with the regular changes applied to this platform.

I would rate this solution an eight out of ten.

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.

I use Azure App Service as an application deployment environment. It allows me to access the FTB directly in deployed applications and change certain rules and regulations like filtering of access management.

The best feature is scalability, which allows you to target potential clients worldwide by connecting the application to a local server. This makes the application readily accessible, and the response time will be much better.

If you're on the cloud, you just get a web interface without much detail for additional configuration or the authority to configure the root or system-level configuration. This is a weakness in the cloud version compared to desktop. In the next release, Microsoft should provide additional options for configuring the deployment environment.

I've been using this solution for three to four years.

This is a stable solution.

Scalability is one of this solution's strongest points.

Microsoft's technical support meets expectations - sometimes there's a bug on their side, and we have some downtime, but it's usually minimal. However, there are some issues with technical staff passing cases on instead of dealing with them.

Neutral

Azure App Service is expensive compared to its competitors, especially its cloud-only version. I would rate their pricing as two out of five.

I would rate Azure App Services as eight out of ten.

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. 

This solution is used for project management, source code and IT. It is used primarily for development purposes.

This solution is easy to deploy.

The cost management of this solution could be better. We only receive estimations.

This is a stable solution. 

This is a scalable solution. 

The initial setup of this solution is very easy.

The pricing and cost of this solution depends on the use and needs of a business.

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. 

We wanted to build a web application, so we started exploring whether we should do it on-premise or on cloud. We already had an Azure subscription and then we decided to do it on Azure. I like the solution because if you want to do something, even if it is a simple proof of concept, you can use a daily subscription. You can do it within minutes and it makes things move a lot faster compared to traditional data center models.

With this solution, it takes less time to deploy something. So in terms of timelines and user satisfaction, the users are happy. 

I like that you can see everything once you log on to the portals. You can see everything including the pricing of the solution. You know how much it's going to cost your client, how much it is going to cost you monthly or daily and you can even control the usage so that you pay even less. So you have better control over things. 

I would like to see faster adoption and maybe they can give you some templates, so that we can deploy something and then modify the template. For instance, having templates for creating a website will make things faster and easier.

The program is stable and we've had no technical issues so far.

The program is very scalable and we plan to scale to 600 or 700 users.

We've tried many other options but the problem is we are using a product from a vendor and ideally, this functionality should be made available in that product. But we're using Azure App Service and then give users a temporary solution because we don't want to change the product that they are using because their mobile devices are very old. It's going to be a waste of money when they will any replace it in a year's time. It is more expensive to upgrade that product than developing something cheap on Azure App Service.

The initial setup is very straightforward. Deployment is fast if you just want to create a roadmap and the database, but that is if you know what you're doing. If the deployment is too complex, you might want to use an expert to help you. I'm not familiar with the technology and I haven't done web development myself. But I just followed some articles and then did everything myself. So it's not difficult at all. You can also go to Azure's web portal and follow their instructions. 

Azure doesn't cost as much as other services. If you want to create something, you can create it all on Azure, simple and quick. If you have to do it on-premise, you have to follow some steps. And you have to pay for providing virtual machines and buy licenses for all the products you are going to use, like Windows or SQL. But on Azure, you can use a trial account so that you can see how it works, or you can use your day subscription, which is a lot cheaper. 

We didn't try many other options because we already had an Azure subscription. So it was a very easy decision to make and we didn't explore other options. Our version is a little bit outdated, so we plan on upgrading soon. The next version has all the functionality we are looking for. Our main concern is speed, and that is one of the features we like about Azure.

My advice to others would be to occupy the use cases from businesses to see if this works for you. It is really easy. I give this solution a nine out of ten. In the future, I would like to have a template for development, though.

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.