App Service plans and pricing tiers in Azure - Step-by-Step Execution

Process Flow - App Service plans and pricing tiers

Choose App Service Plan

↓

Select Pricing Tier

↓

Allocate Resources

↓

Deploy Web App

↓

App Runs with Selected Tier Features

↓

Scale or Change Tier if Needed

↓

End

This flow shows how you pick an App Service plan, select a pricing tier, allocate resources, deploy your app, and optionally scale or change the tier.

Execution Sample

Azure

1. Create App Service Plan named 'MyPlan'
2. Select 'Standard' pricing tier
3. Deploy Web App to 'MyPlan'
4. App runs with Standard features
5. Scale up to 'Premium' tier if needed

This example shows creating a plan, choosing a tier, deploying an app, and scaling the plan.

Process Table

Step	Action	Pricing Tier Selected	Resources Allocated	App Behavior
1	Create App Service Plan 'MyPlan'	None	None	No app yet
2	Select 'Standard' pricing tier	Standard	Medium CPU, Memory, Storage	Ready for deployment
3	Deploy Web App to 'MyPlan'	Standard	Medium CPU, Memory, Storage	App runs with Standard features
4	App runs	Standard	Medium CPU, Memory, Storage	Supports custom domains, SSL, auto-scaling
5	Scale up to 'Premium' tier	Premium	Higher CPU, Memory, Storage	App gains more features and capacity
6	App runs with Premium tier	Premium	Higher CPU, Memory, Storage	Better performance and scaling
7	End	Premium	Higher CPU, Memory, Storage	Execution stops

💡 App Service plan is set and app is running with selected pricing tier features.

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 5	Final
App Service Plan	None	MyPlan created	MyPlan with Standard tier	MyPlan upgraded to Premium tier	MyPlan with Premium tier
Pricing Tier	None	Standard	Standard	Premium	Premium
Resources	None	Medium CPU, Memory, Storage	Medium CPU, Memory, Storage	Higher CPU, Memory, Storage	Higher CPU, Memory, Storage
App State	Not Deployed	Not Deployed	Deployed and Running	Running with Premium features	Running with Premium features

Key Moments - 3 Insights

Why does the app not run immediately after creating the App Service Plan?

Because the app is only deployed after selecting the pricing tier and deploying the web app, as shown in steps 2 and 3 of the execution_table.

What changes when scaling from Standard to Premium tier?

Resources like CPU, memory, and storage increase, and the app gains more features and better performance, as seen between steps 5 and 6.

Can you deploy an app without selecting a pricing tier?

No, selecting a pricing tier allocates resources needed for the app to run, so deployment happens after tier selection (step 2 then 3).

Visual Quiz - 3 Questions

Look at the execution_table, what is the pricing tier after step 3?

A Free

B Standard

C Premium

D None

💡 Hint

Check the 'Pricing Tier Selected' column at step 3 in the execution_table.

At which step does the app start running with Premium tier features?

A Step 4

B Step 5

C Step 6

D Step 2

💡 Hint

Look at the 'App Behavior' column for when Premium features appear.

If you skip scaling up, what resources does the app use after deployment?

A Medium CPU, Memory, Storage

B Higher CPU, Memory, Storage

C No resources allocated

D Low CPU, Memory, Storage

💡 Hint

Refer to the 'Resources Allocated' column after step 3 in the execution_table.

Concept Snapshot

App Service Plan defines the compute resources for your app.
Pricing tiers (Free, Shared, Basic, Standard, Premium) determine features and capacity.
Select a tier to allocate resources before deploying your app.
You can scale up or down by changing the pricing tier.
Higher tiers offer better performance, scaling, and features.

Full Transcript

This visual execution shows how to create an Azure App Service Plan, select a pricing tier, deploy a web app, and optionally scale the plan. First, you create the plan without resources. Then, selecting a pricing tier allocates CPU, memory, and storage. Deploying the app runs it with the selected tier's features. Scaling up increases resources and features. The execution table tracks each step's state, and the variable tracker shows how plan, tier, resources, and app state change. Key moments clarify common confusions about deployment timing and scaling effects. The quiz tests understanding of tier selection, app running state, and resource allocation. The snapshot summarizes the core concept for quick review.

Practice

1. What does an Azure App Service plan primarily define for your web app?

easy

A. The amount of computing resources like CPU and memory allocated

B. The programming language your app uses

C. The number of users who can access your app

D. The database type your app connects to

Solution

1. Step 1: Understand the role of an App Service plan

   An App Service plan defines the compute resources such as CPU, memory, and storage that your app will use.

2. Step 2: Differentiate from other app settings

   It does not control programming language, user count, or database type, which are separate configurations.

3. Final Answer:

   The amount of computing resources like CPU and memory allocated -> Option A

4. Quick Check:

   App Service plan = compute resources [OK]

Hint: App Service plan = resources your app runs on [OK]

Common Mistakes:

• Confusing App Service plan with app code or database
• Thinking it controls user access limits
• Assuming it sets programming language

2. Which of the following is the correct way to specify a Standard pricing tier in an Azure App Service plan using Azure CLI?

easy

A. az appservice plan create --name MyPlan --resource-group MyGroup --plan-tier Standard

B. az appservice plan create --name MyPlan --resource-group MyGroup --sku Standard

C. az appservice plan create --name MyPlan --resource-group MyGroup --pricing-tier Standard

D. az appservice plan create --name MyPlan --resource-group MyGroup --tier Standard

Solution

1. Step 1: Recall Azure CLI syntax for App Service plan creation

   The correct parameter to specify pricing tier is '--sku' followed by the tier name like 'Standard'.

2. Step 2: Verify other options

   Options using '--tier', '--pricing-tier', or '--plan-tier' are invalid parameters and will cause errors.

3. Final Answer:

   az appservice plan create --name MyPlan --resource-group MyGroup --sku Standard -> Option B

4. Quick Check:

   Use --sku to set pricing tier [OK]

Hint: Use --sku to set tier in Azure CLI [OK]

Common Mistakes:

• Using incorrect parameter names like --tier or --pricing-tier
• Confusing plan name with tier parameter
• Omitting the resource group

3. Given an App Service plan with pricing tier set to 'Basic', what will happen if you try to enable autoscaling for your app?

medium

A. Autoscaling is enabled by default on Basic tier

B. Autoscaling will work because Basic tier supports it

C. Autoscaling will work only during business hours

D. Autoscaling will fail because Basic tier does not support autoscale

Solution

1. Step 1: Understand autoscaling support by pricing tiers

   Autoscaling is supported starting from the Standard tier and above, not in Basic tier.

2. Step 2: Apply this to the Basic tier scenario

   Since Basic tier lacks autoscale support, attempts to enable it will fail or be blocked.

3. Final Answer:

   Autoscaling will fail because Basic tier does not support autoscale -> Option D

4. Quick Check:

   Basic tier = no autoscale support [OK]

Hint: Autoscale needs Standard or higher tier [OK]

Common Mistakes:

• Assuming Basic tier supports autoscale
• Thinking autoscale is automatic on all tiers
• Confusing Basic with Standard tier features

4. You created an App Service plan with the SKU 'F1' but your app is not accessible publicly. What is the most likely cause?

medium

A. You must assign a custom domain to make it public

B. F1 tier does not support public access by default

C. F1 is a Free tier and may have limited outbound network access

D. F1 tier requires manual SSL configuration before public access

Solution

1. Step 1: Understand the Free (F1) tier limitations

   The Free tier (F1) has restrictions including limited outbound network access and possible cold start delays.

2. Step 2: Relate these limits to app accessibility

   Limited network access can cause the app to be unreachable or slow, but public access is allowed.

3. Final Answer:

   F1 is a Free tier and may have limited outbound network access -> Option C

4. Quick Check:

   F1 tier = limited network, possible access issues [OK]

Hint: Free tier has network limits causing access issues [OK]

Common Mistakes:

• Thinking Free tier blocks public access
• Assuming custom domain is required for public access
• Believing SSL setup is mandatory for access

5. You need to host a production web app with high traffic, custom domains, SSL, autoscaling, and daily backups. Which App Service plan pricing tier should you choose?

hard

A. Standard (S1)

B. Basic (B1)

C. Free (F1)

D. Shared (D1)

Solution

1. Step 1: Identify required features for production app

   High traffic, custom domains, SSL, autoscaling, and backups require a tier with advanced features.

2. Step 2: Match features to pricing tiers

   Standard tier supports autoscaling, custom domains, SSL, and backups. Basic lacks autoscaling and some features. Free and Shared tiers are limited.

3. Final Answer:

   Standard (S1) -> Option A

4. Quick Check:

   Production needs Standard tier features [OK]

Hint: Standard tier supports autoscale and backups [OK]

Common Mistakes:

• Choosing Free or Shared for production needs
• Assuming Basic supports autoscale
• Ignoring backup requirements