Azure App Service Scaling Features And Capabilities - Blogs

Azure App Service Scaling Features And Capabilities


In terms of web applications, underlying infrastructure plays a vital role in coping with application performance, complex logic, traffic surges, and long-running processor execution times. it is one of the most difficult jobs to calculate the specifications in terms of infrastructure for web applications, whether it is public-facing applications or for a particular company.  It is one of the most difficult jobs to calculate the specifications in terms of infrastructure for web applications.


In many cases, there is a high chance that there will be a requirement to upgrade infrastructure specifications after a certain threshold, or maybe resources are not utilized properly. This is another difficult job for developers, DevOps engineers, or even for management to upgrade those resources. It may results in application downtime, unstable or sometimes modifications in code level, as well as being quite expensive overall.


Scaling in Azure App Service

Scale-Up and Scale-Out are two primary workflows for Scaling.


Scale-Up (Vertical scaling)

In this scaling option, we can modify the instance power in terms of CPU, memory, disk space which directly impact the cost. This scale-up is done by changing the pricing tier of the app service plan. Additionally, based on the pricing tier, different useful features are available with the azure app service like custom domains and certificates, staging slots, autoscaling, instances, daily backups, and many more.

Scaling is quite easy to do in azure, I prefer from the portal,

Simply log in to the portal, open your app service then you will see the following options for scaling:



In the scale-up, we can see the distinct categories:

  • Dev/Test
  • Production
  • Isolated



As the name suggests, this category is used for development and testing purposes of the applications with Azure App Service.

There are five separate pricing tiers in the Dev/Test category, as shown below:



F1(free one), D1, B1, B2 and B3

We can see from the above illustration that the resources as well as tentative cost per month based on these pricing tiers.



F1 Pricing tier(Free Tier)

  • No feature
  • Share Infrastructure 1GB Memory/1GB Storage
  • 60 minutes/day compute


D1 Pricing Tier

  • Custom domain feature
  • Share Infrastructure 1GB Memory
  • 240 minutes/day compute

There is no SLA provided for this service plan and is metered on a per-app basis.


Basic Service Plan(B1,B2 and B3)

This plan is for low-traffic applications where we don’t need auto-scaling and traffic management features. Built-in network load balancing support automatically distributes traffic across instances.


B1 Hardware

  • 100 total Azure computing units
  • 1.75 GB Memory and 10 GB disk storage
  • A-series computing equivalent

B2 and B3 have the same features as B1, however, hardware contents are different.



As the name suggests, this category for the production workloads of the applications. Again, there are two types under this category: standard and premium pricing tiers.