Azure App Service and Scaling

Sharing is caring!


Azure App Service is the integration of multiple components to support connectivity between application components that communicate with many different client devices, browsers or B2B endpoints.  App service is a fully-managed Platform-as-a-Service (PaaS) offering with minimal administrative overhead and tight integration with Azure’s existing DevOps tooling.

The Azure App Service consists of the following services:

Web Apps: Web application hosting that is scalable to your resource needs and compatible with enterprise virtual networks.

Mobile Apps:Dynamic mobile application data hosting integrated with authentication, push notifications and custom endpoints.

API Apps: API application hosting that uses open-source frameworks for API metadata and connectivity.

Logic Apps:Automated business process workflows that can integrate existing SaaS applications or your custom API Apps from on-premise or the cloud.

Azure Web App instance can host web applications written in many languages including:

ASP.NET, Ruby, Python, Java

Web Apps also support extended features that will be discussed in this module including:

Extensions, Live Debugging and Live Log Tracing, Continous Deployment, WebDeploy Deployment, Local Git Repository, Web Jobs, Backup/Restore, Autoscale


App Service Plans represent an assignment of features and capacity for multiple services within App Service.  Each Mobile, Logic, Web or API App must be associated with an App Service Plan which dictates both the features available, capacity available and billing for the services. An app in App Service can be associated with only one App Service plan at any given time.

Both apps and plans are contained in a resource group. A resource group serves as the life-cycle boundary for every resource contained within it. Resource groups enable you to manage all the pieces of an application together.

App service plan can be Basic tier, Standard or Premium 


Web Apps can be scaled in both the horizontal and vertical directions:

Horizontal: Web Apps can be scaled to multiple instances by either manually changing the instance count or by using an autoscale algorithm in the App Service Plan.  By default a Standard App Service Plan has 2 instances implemented using autoscale and a metric that measures CPU Percentage.

Vertical: Web Apps can be scaled to have more memory or CPU time by change the App Service Plan tier.  For example, the Standard S1 App Service Plan has 1 reserved CPU core and 1.75 GB of RAM.  If you need 4 cores and 7 GB of RAM you can scale up to the Standard S3 Service Plan.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.