What is your primary use case for Microsoft Azure App Service?

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.

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.

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.

It simplifies the deployment of applications, including those built with technologies like .NET or UCS, making it particularly valuable for microservices applications. It streamlines the deployment process, allowing developers to easily deploy and manage their applications without requiring dedicated DevOps engineers.

Our clients use Microsoft Azure App Service for running their websites. The tool also has Azure Functions, which work in coordination with App Service. Azure Functions and Azure Logic Apps are different objects in Azure, but they all work together. I don't know details about how Microsoft Azure App Service works.

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

We primarily use the solution for MDM management.

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

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

We use Azure App Service for several web services and websites hosted on the Azure cloud. It was a COVID-driven decision because we serve hundreds of colleges and schools that are part of our industry. All the services hosted in-house had to be scaled and made accessible over the cloud. Azure was the easiest available option at that time. We have around 80,000 users on our Azure Cloud applications and about three admins.

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

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

We're working on the premium, dynamic, and standard price sharing on Microsoft Azure App Service, and most of our APIs are hosted on Microsoft Azure App Service. We're also using the platform for API calls and security management. We're not currently using Microsoft Azure App Service for any static web. We have a lot of API calls daily that try to access services because our applications are interconnected with either Coupa or Microsoft Dynamics 365.

Our primary use case for this solution is hosting web applications which can be Linux or Windows-based. Microsoft Azure App Service is a multi-tenant environment where customers can load and run the application. It is similar to a platform as a service.

Our primary use case for this solution is for hosting web apps so people can deploy this application and host it on an app service.

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.

We have used App Services to integrate a lot of solutions, to bring content from a different domain or maybe a different data source. We were using a lot of Microsoft Azure services to build. We were also leveraged to deploy non-SAP solutions like Python Machine Learning IOTs, using these App Services to bring solutions into SAP. We were doing one POC for one of the last customers where we had to integrate mobile solutions and IoT. We were using App Services to build those IOT components, retrieve data, and integrate with SAP. We were using some temperature readings for our supply chain logistics company. Once we read temperatures, we'll push it to the App Service, and App Service will internally push it to the digital twins. From there, we get the events and consume those events into a function, and then whatever the functions read will be pushed into the DB.

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

We mostly use Microsoft Azure App Service for websites, such as content management systems, WordPress, and others, which are built on Azure Web Repair and App Services.

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.

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 primarily use the solution to create a website. Azure will provide infrastructure without any servers and can provide service to host the websites of the company.

Our primary use case of the solution is for ETL. We're slowly moving everything over to Azure, so I think this will be our expected hub for the near future. I'm the chief analytics officer and we are a Microsoft partner.

The primary use case has been pretty vague so far. Right now, my scope is on DevOps. I'm looking at it from the point of view of having a DevOps platform. We already have a team foundation server and are working from the cloud.

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.