Microsoft Azure App Service Reviews

The typical use case for Microsoft Azure App Service is for our clients to utilize scalability and security. The clients are using the Microsoft Azure services for security reasons and highly scalable and reliable infrastructure. Most of the clients are using Azure services, as we developed our applications and host them on Azure for seamless operations.

The best features of Microsoft include Office 365, collaboration suites, MS Teams, and SharePoint. We are using SharePoint for collaboration across the entire organization and to share documentation with our clients. We are also using infrastructure through Microsoft Azure, so our own websites are hosted on the Cloud, including Web Application Firewall, Azure clusters, and Kubernetes.

The best features of Microsoft Azure App Service are its capacity for scalability, security, and basic support functionalities.

Microsoft Azure App Service's automatic scaling and load balancing features are inbuilt capabilities within the application. There are two types of applications: Kubernetes for load balancing and the virtual scale set. We are using load in certain applications that automatically scale; these features are present in Azure, and at the front end, we are using load balancers.

Regarding the built-in security features, such as authentication and SSL certificates, each web request passes through the Web Application Firewall and the SSH, SSL certificate, and Secure Socket Layer certificate. Each authentication integrates with Microsoft Identity Access Management, as we create users on Azure Active Directory Azure ID to use for the applications.

I use Microsoft Azure App Service within my industry primarily for web app deployments. However, I don't use it extensively since I currently operate on an intranet system.

My organization has significantly improved operations using Azure App Service. Before integrating Azure, many applications were not cloud-based, leading to version control issues. Now, with everything integrated, these problems have been solved, thanks to Microsoft's good work.

I use Microsoft Azure App Service to create some applications personally, but not so much. I use the tool to try to learn a new language or upgrade to any new framework. I use similar tools to manage application components, but I don't do it so much.

A few weeks ago, I was trying to use a new web application with Microsoft Azure App Service. I thought it would be better to have a template to publish directly to Microsoft Azure App Service using GitHub because there were some documents related to Azure DevOps. If you use GitHub Actions, I would say that it is a little bit more complicated.

We primarily use web app services and Kubernetes. I mostly use Microsoft Azure App Service for bespoke applications hosted on web services.

The most valuable features in the context of development and deployment are the integration with SDKs and the infrastructure standpoint. I primarily use horizontal auto-scaling rather than vertical scaling.

I use the solution in my company for the applications we have on the on-premises part, and we want to convert them to SaaS or PaaS. We want to use Azure Kubernetes Service (AKS) with the solution, as there are areas that depend on both tools when we want to migrate something to the cloud.

The tool's most valuable feature is that we don't have to worry about the infrastructure. The cost or price of Azure is lower than that of the on-premises version, which is why we might want to implement our solutions in Azure.

I work with Microsoft Azure App Service Functions and Static Web Apps. I am searching for new applications and have been doing so for three or four months, approximately.

For purposes of using Microsoft Azure App Service, we have made an HTML page that performs various tasks, for instance, or a service bus for messaging to other applications.

Regarding the best advantages of Microsoft Azure App Service, we are still exploring, so we cannot determine what's most or least valuable as it's new for us.

Regarding functionalities or capabilities that I am using most frequently, I question what features are meant, whether it refers to applications.

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.

I am using Azure App Service as an end user.

Azure App Service has several features that are valuable, including its scalability and seamless integration with other systems, which support flexibility. 

Additionally, the platform provides certain advantages in its core functionalities and usefulness.