Azure App Service Reviews and Ratings

Use Cases and Deployment Scope

Coming from a background of manual deployment using the CD drive and USB to deployment using AWS tools like CodeDeploy, we primarily use Azure App Service to prepare our servers to run automated tests and ensure the same configuration is deployed across all prod and non-prod servers. At a high level, we can achieve greater consistency, reliability, faster releases, and lower manpower overhead.

Likelihood to Recommend

Well-suited for rapid deployment of apps and API. Less suited and needs improvement for setups requiring runtime customization or complex testing scenarios.

Use Cases and Deployment Scope

We discontinued the use of the Azure App. Microsoft is behind in its AI integration. Google took the spot with the new Gemini integration, and we replaced Azure with the Google suite. So, no, I wouldn't recommend it for anyone anymore. There are better solutions for app deployment around, and Microsoft is dropping the ball.

Likelihood to Recommend

Microsoft AI is one of the worst in the market, in my experience. I don't know if they are using an old GPT build, but it is better to use other tools to develop an app than to use Azure. Sure, you have the integration with Azure, but that's it. If you are using AZWS or Google Cloud, it is just not worth it.

Use Cases and Deployment Scope

I have been using Azure App Service to modernize customer's .NET applications into a modern Platform As A Service (PaaS) and cloud-native application architecture platform. App Service allows me to provide a fully-managed environment and allow the customer to offload their administrative overhead for application infrastructure, while at the same time providing them with infrastructure monitoring, backup, scalability and service redundancy.

Likelihood to Recommend

The best-suited usage scenario for Azure App Service is for modernizing existing .NET apps and thus re-designing them to fit the requirements but also make the most out of the benefits of a truly PaaS service. Therefore, any apps that must be quickly moved to the Azure cloud by the lift and shift method, i.e. without significant refactoring, are not good candidates for Azure App Service but for IaaS (Azure VMs).

Use Cases and Deployment Scope

We use Azure Web Apps for our Front End and some big data processing needs: for the monolith and some microservices. Also we host APIs over them. Web Apps offer an easy to use platform for creating and modifying our code in a seamless way across different stages of our data ingestion-processing-and offering for the customers.

Likelihood to Recommend

For a mid size front end, with a good budget to pay for resources escalation. Also for test environments and debug of Web Apps. It hosts great Function Apps, together with Web Apps. Spending in bundled in firewall, that's a good platform for e-payments and complies with all http / web standards, so you wont have surprises with Chrome and Chromium.

It comes with a good IP filter, that you would use starting in S1 (basic production) plan, but if you want a true firewall with DoS protection, it comes as an "additional". Both perform well.

Production plans have built-in backup and advanced networking support, also if spend limits are not so low, that's great to integrate your website in a private network.

Use Cases and Deployment Scope

We used it to teach the students who bought the course how to use the web app and where to use. We helped them to deploy the projects on Azure. Also we helped them to get the student packs and Azure credits so it may be helpful for them to deploy their projects without the need of credit cards!

Likelihood to Recommend

So based on our experience Azure is giving some API development, that is best thing. Also Azure is giving streamlined workflow for DevOps. It is supporting some popular programming languages like java, .net , javascript etc that make it easy to develop and deploy application in the platform and monitor it.

Use Cases and Deployment Scope

The ASP NET Core apps were deployed using Azure App Service. Multiple programs were installed and utilized by the entire company. Having the ability to launch our apps directly from Visual Studio was a huge time-saver. The Azure site or the Azure command-line interface allowed us to make the necessary adjustments.

Likelihood to Recommend

You may easily deploy your apps to Azure App Service if they were written in Visual Studio IDE (typically.NET applications). With a few clicks of the mouse, you may already deploy your application to a remote server using the Visual Studio IDE. As a result of the portal's bulk and complexity, I propose Heroku for less-experienced developers.

Use Cases and Deployment Scope

We use Azure App Service for our full cloud-based website's new version. We use it to deploy both production and QA versions of the site, so that we don't have to manage website infrastructure, including on-premise web servers and security equipment. We use it alongside other Azure services, including storage, CDN, DB...

Likelihood to Recommend

Azure App Service is well suited in our case :

<ul><li>Our website is developed by our tech partner in a full Microsoft Azure cloud based environment.</li><li>We gave them specific access rights and the CI / CD integration helped a lot for updates and improvements deployment.</li><li>Most of the infra issues we had with our website weren't coming from App Service</li></ul>

Use Cases and Deployment Scope

I used it to host our organization website, which is written by PHP. As the website is our main product, it plays very important role in our company. We used Azure's app engine for several months, mostly for our testing purpose. But we never rolled out our production to Azure because of some issues.

Likelihood to Recommend

If you are a large organization where you have a lot of traffics, Azure is good for you. If your scenario is something like, you sometimes have high traffic, and sometimes low traffic, and you got enough money, Azure is good for scaling up to your need. Azure is definitely not for you if your budget is low. Not suitable for low budget people AT ALL.

Use Cases and Deployment Scope

Azure App is being used to host our .NET applications. Runtime stack for these are .NET 2.1. Azure has good support for .NET applications. So we prefer using Azure for .NET.

It is integrated will with Azure DevOps. So we use piplelines to deploy code.

Likelihood to Recommend

Azure App Service is suited well for .NET runtimes. We don't need to do any IIS configuration. It is well integrated with DevOps so CI/CD pipelines can be configured.

Multiple applications cannot be hosted on the same Service. So it can get expensive for smaller apps.

Use Cases and Deployment Scope

We use Azure App Service to build full-fledged custom web-based software solutions for small and medium-sized businesses in a variety of markets. The Azure App Service coupled with .NET, Entity Framework, and other Azure features (storage, tables, etc.) make it easy to quickly build fully-functional apps, and we're able to do so so much quicker than when we were using the LAMP stack (Linux, Apache, MySQL, and PHP). Plus, we can scale resources with a click instead of needing to migrate to different servers and manually handle load balance, etc.

Likelihood to Recommend

Azure App Service is great if you're starting a new web project and need an infrastructure that is fast, stable, secure, and scalable. The service has a very high up-time, and it supports a variety of languages and technologies (though it really shines with the .NET stack - C#, ASP.NET, Entity Framework, etc.). If you're thinking about porting an existing app over, it may wind up being expensive as far as resources go if the software isn't properly optimized to utilize cloud resources efficiently, so that's something to keep in mind.