Creating a web app in Azure - Visual Walkthrough

Process Flow - Creating a web app

Start

↓

Choose App Name

↓

Select Resource Group

↓

Pick Runtime Stack

↓

Set Region

↓

Configure App Service Plan

↓

Review & Create

↓

Deployment

↓

Web App Running

This flow shows the main steps to create a web app in Azure, from naming to deployment and running.

Execution Sample

Azure

az webapp create --resource-group MyResourceGroup --plan MyPlan --name MyWebApp --runtime "DOTNET|6.0" --location EastUS

This command creates a web app named MyWebApp in the specified resource group and plan using .NET 6 runtime in the EastUS region.

Process Table

Step	Action	Input/Parameter	Result/State
1	Choose App Name	MyWebApp	App name set to MyWebApp
2	Select Resource Group	MyResourceGroup	Resource group MyResourceGroup selected
3	Pick Runtime Stack	DOTNET|6.0	Runtime set to .NET 6.0
4	Set Region	EastUS	Region set to EastUS
5	Configure App Service Plan	MyPlan (Standard S1)	App Service Plan MyPlan configured
6	Review & Create	Confirm settings	Settings validated
7	Deployment	Run az webapp create command	Web app MyWebApp created and deployed
8	Web App Running	Access URL	Web app is live and accessible

💡 Web app creation completes successfully and app is running.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	After Step 7	Final
AppName	null	MyWebApp	MyWebApp	MyWebApp	MyWebApp	MyWebApp	MyWebApp	MyWebApp
ResourceGroup	null	null	MyResourceGroup	MyResourceGroup	MyResourceGroup	MyResourceGroup	MyResourceGroup	MyResourceGroup
Runtime	null	null	null	DOTNET|6.0	DOTNET|6.0	DOTNET|6.0	DOTNET|6.0	DOTNET|6.0
Region	null	null	null	null	EastUS	EastUS	EastUS	EastUS
AppServicePlan	null	null	null	null	null	MyPlan (Standard S1)	MyPlan (Standard S1)	MyPlan (Standard S1)
DeploymentStatus	Not started	Not started	Not started	Not started	Not started	In progress	Completed	Completed

Key Moments - 3 Insights

Why do we need to select a resource group before creating the web app?

The resource group organizes related resources together. In the execution_table row 2, selecting the resource group ensures the web app is created in the right container for management.

What happens if the app name is already taken?

The creation command will fail because app names must be unique globally. This is implied in step 7 where deployment happens; if the name is taken, deployment stops.

Why do we specify a runtime stack like DOTNET|6.0?

The runtime stack tells Azure what environment to prepare for your app code. In step 3, setting runtime ensures the app runs correctly on the chosen platform.

Visual Quiz - 3 Questions

Look at the execution_table, what is the AppName variable after Step 3?

A MyWebApp

B null

C MyResourceGroup

D DOTNET|6.0

💡 Hint

Check variable_tracker row for AppName after Step 3 column.

At which step does the deployment of the web app start according to the execution_table?

A Step 5

B Step 6

C Step 7

D Step 8

💡 Hint

Look at the 'Action' column in execution_table for deployment start.

If the region was changed to WestEurope at Step 4, what would change in the variable_tracker?

A AppName would change to WestEurope

B Region would be WestEurope after Step 4 and onwards

C ResourceGroup would be WestEurope

D No change in any variable

💡 Hint

Check the Region variable values across steps in variable_tracker.

Concept Snapshot

Creating a web app in Azure involves:
- Choosing a unique app name
- Selecting a resource group
- Picking a runtime stack (e.g., DOTNET|6.0)
- Setting the region
- Configuring an App Service Plan
- Deploying the app
The app runs live after deployment.

Full Transcript

To create a web app in Azure, you start by choosing a unique name for your app. Then, you select a resource group to organize your resources. Next, pick the runtime stack your app will use, such as .NET 6.0. After that, set the region where your app will be hosted. Configure the App Service Plan which defines the compute resources. Review all settings and run the deployment command. Once deployed, your web app is live and accessible. Each step updates variables like AppName, ResourceGroup, Runtime, Region, and DeploymentStatus as shown in the execution table and variable tracker.