AVD deployment portal
Deploys the AVD landing zone, one step at a time. Pasted output never leaves this browser.
Recording
Open and close the run (5 steps)
Choose a region ,
Pick the Azure region closest to your users. This page can measure it for you.
Takes about 20 seconds. Run it where your users work, off the VPN.
| # | Region | Geography | Median | Rating |
|---|
How regions are rated
Round-trip time from this browser, so run it where your users work, not from Cloud Shell or over a VPN. Under 100 ms is good for AVD, 100 to 150 ms is usable, above 150 ms feels sluggish. Each region gets a warm-up request and 5 timed ones; the median counts.
Size the host pool ,
Choose how many session hosts to run. One host and a 100 GiB profile share is enough to start.
How sizing works
It starts from the minimum viable kit: one memory-optimized E4as_v5 host and a 100 GiB profile share. Automatic sizes the hosts from how many people use them and how they work (Microsoft's multi-session guidance: light 6, medium 4, heavy 2, power 1 user per vCPU). It suggests memory-optimized E-series sizes, because hosts shared by many users run out of memory before CPU, and every host gets a Premium SSD OS disk.
Once you apply a sizing, the commands carry it: the pre-deployment preflight checks quota and availability for it, and deploy.sh deploys it. The next step prices it.
Cost ,
Hosts bill for the hours they run. These two settings decide those hours.
How the cost is worked out
Most of the cost is the hours the session hosts run. Both settings are deployed with the landing zone. The pre-deployment preflight prices the plan at Azure list prices for your region; after that, changing a setting here reprices it without running anything.
Pre-deployment preflight
Check that the subscription is ready. Nothing gets changed.
Deploy the landing zone
Deploy it once the preflight says Ready. It takes 30 to 45 minutes and keeps running in Azure if Cloud Shell disconnects.
Post-deployment setup
Finish what the deployment can't do on its own: admin consent, the Conditional Access exclusion and the profile share permissions.
Sign in
Open the desktop as a member of the users group.
Verify access , not checked
Check that this device can reach AVD, then open the desktop. Run it where people will connect from.
Can this device reach AVD?
| Host | Used for | Median | Result |
|---|
What this check proves
Open the desktop
Sign in as a member of the users group, and choose Yes when asked to allow the remote desktop connection.
What to expect
The prompt to allow the connection comes once for each session host (Microsoft Entra single sign-on). A stopped host starts on the first connection, which then takes a few minutes and isn't representative. To test the Windows App and its RDP path, open the Windows App and choose the same desktop. There's no direct Windows App link: its parameters aren't confirmed yet.