What you'll build
- A user signs in through Windows App or a browser and gets a full Windows 11 desktop.
- Every new session host appears in Intune > Devices > Windows within minutes, ready for compliance and configuration policies.
- The VM stays off unless someone connects, so the lab costs a few euros a month, or nothing while the Azure free credit lasts.
Build time: about 2 hours the first time, 30 minutes once you know it.
Full walkthrough: build it step by step
An 11-minute narrated walkthrough of the whole lab, recorded from a real build: resource group and budget, Entra groups, network, host pool, the session host with Entra join + Intune enrolment, roles, cost controls, checks in Entra and Intune, signing in as a user, and the three real problems we hit along the way.
Architecture and design
The user connects through the AVD service; the session host only makes outbound connections, so no inbound ports are open. While the VM is built it joins Entra ID and enrols in Intune, then picks up Settings catalog policies through the AVD-SessionHosts group.
| Design decision | Lab choice | Why |
|---|---|---|
| Identity | Microsoft Entra joined (no domain controller) | Cheapest and simplest; enables automatic Intune enrolment |
| Host pool type | Pooled, Windows 11 Enterprise multi-session | Several users share one VM |
| Session hosts | 1 × Standard_D2s_v5 | Smallest size Microsoft lists for a light workload |
| User profiles | Local profiles (no FSLogix) | Lab users don't need roaming profiles; saves a storage account |
| Network | One VNet, no public IP, no inbound NSG rules | AVD uses outbound reverse connect only |
| Management | Intune, Settings catalog policies | Templates and update rings don't apply to multi-session |
Cost plan: run it for almost nothing
You pay only for Azure compute and disk; the AVD service and the Windows licence are covered by eligible Microsoft 365 licences. The biggest saving is keeping the VM deallocated (stopped) except when it's in use.
| Cost item | Lab choice | What you pay |
|---|---|---|
| AVD service + Windows 11 multi-session licence | Microsoft 365 E3, E5 or Business Premium | 0 |
| Intune + Entra ID P1 | Included in Microsoft 365 E3 | 0 |
| Azure subscription | Azure free account: USD 200 credit for 30 days (Microsoft) | 0 while credit lasts |
| Session host VM | 1 × Standard_D2s_v5, Start VM on Connect + auto-shutdown | Per running hour only, roughly €0.10–0.15 (approximate) |
| OS disk | 127 GB Standard SSD | Charged even when the VM is off, roughly €8–10 / month (approximate) |
| Network | VNet, subnet, NSG, no public IP | 0 |
- Create a budget alert at €10 on the subscription before anything else.
- Use one session host; add a second only to demo load balancing.
- Turn on Start VM on Connect and a nightly auto-shutdown.
- Between uses, delete the session host VM and its disk; recreate it in 15 minutes from the host pool.
Prices are approximate and change by region; check the Azure pricing calculator before you build.
Prerequisites and licences
Most tenants with Microsoft 365 E3 already meet every item except the Azure subscription; check each one before you start.
| Requirement | Why | How to check |
|---|---|---|
| Eligible user licence: Microsoft 365 E3, E5, Business Premium, or Windows Enterprise E3/E5 (licensing) | Right to use AVD and Windows 11 Enterprise multi-session | Admin center > Billing > Licenses |
| Intune licence | To enrol and manage the session hosts | Included with the licences above |
| MDM user scope = All | Lets Entra-joined VMs enrol automatically | Intune > Enrollment > Automatic Enrollment |
| Users may join devices to Entra | Session hosts join Entra ID | Entra > Devices > Device settings |
| Azure subscription in the same Entra tenant as Intune | Entra join only joins VMs to the subscription's own tenant (Microsoft Learn) | To create, signed in as your tenant admin |
| Owner, or Contributor + User Access Administrator | To create resources and assign roles | Subscription > Access control (IAM) |
| Test user with an eligible licence | To sign in to the desktop | Create [email protected] |
Phase 1 · 20 min
Tenant and Intune preparation
- Check automatic enrolment. Intune admin center > Devices > Enrollment > Windows > Automatic Enrollment: MDM user scope = All.
- Check device join. Entra admin center > Devices > Device settings: Users may join devices to Microsoft Entra = All.
- Create the user group
AVD-Lab-Users(security, assigned). Add[email protected]and give that user an eligible licence. - Create the admin group
AVD-Lab-Adminsand add your admin account. - Create a dynamic device group
AVD-SessionHostswith this rule, so every new session host gets your policies automatically:(device.displayName -startsWith "avdlab")
- Turn on Entra authentication for RDP (needed for single sign-on): Entra admin center > Devices > Remote connection configuration > Windows Cloud Login > Enable Microsoft Entra ID authentication protocol > Save (steps).
Intune policies for multi-session hosts must come from the Settings catalog; templates (except certificates) and Windows Update rings don't apply to Windows Enterprise multi-session (Microsoft Learn).
Phase 2 · 20 min
Azure foundation
- Create the subscription. Go to the Azure free account page, sign in with your work (tenant) admin account, and finish sign-up. A card is needed for identity checks; the free credit is used first.
- Set a budget alert. Cost Management > Budgets > Add: €10 per month, email alerts at 50%, 80% and 100%.
- Register resource providers. Subscription > Resource providers: confirm
Microsoft.DesktopVirtualization,Microsoft.ComputeandMicrosoft.Networkare Registered. - Create the resource group
rg-avd-labin the region closest to your users (for example West Europe or East US). - Create the virtual network
vnet-avd-lab: address space10.20.0.0/16, subnetsnet-avd=10.20.1.0/24, Azure-provided DNS. - Create a network security group
nsg-avd-labwith the default rules only and attach it tosnet-avd. AVD needs no inbound ports; the session host connects out to the service.
| Resource | Name |
|---|---|
| Resource group | rg-avd-lab |
| Virtual network / subnet | vnet-avd-lab / snet-avd |
| Host pool | hp-avd-lab |
| Workspace | ws-avd-lab |
| Desktop application group | hp-avd-lab-DAG |
| Session host prefix | avdlab (VMs become avdlab-0, avdlab-1) |
Phase 3 · 30 min
Create the host pool with Entra join and Intune enrolment
Azure portal > Azure Virtual Desktop > Host pools > Create. Fill each tab as below; everything not listed stays at its default.
| Tab | Setting | Lab value |
|---|---|---|
| Basics | Resource group / Host pool name | rg-avd-lab / hp-avd-lab |
| Basics | Location | Same region as the resource group |
| Basics | Validation environment | Yes (gets new AVD features first; fine for a lab) |
| Basics | Preferred app group type | Desktop |
| Basics | Host pool type / Load balancing | Pooled / Breadth-first |
| Basics | Max session limit | 4 |
| Session hosts | Add virtual machines | Yes |
| Session hosts | Name prefix / Number of VMs | avdlab / 1 |
| Session hosts | Image | Windows 11 Enterprise multi-session (latest, without Microsoft 365 apps) |
| Session hosts | Size | Standard_D2s_v5 (2 vCPU, 8 GB) |
| Session hosts | OS disk | Standard SSD |
| Session hosts | Network / Public IP | vnet-avd-lab / snet-avd, No public IP |
| Session hosts | Domain to join | Microsoft Entra ID |
| Session hosts | Enroll VM with Intune | Yes |
| Session hosts | Local admin | avdadmin + a strong password kept in a password manager |
| Workspace | Register desktop app group | Yes, new workspace ws-avd-lab |
| Tags | env | lab |
Select Review + create > Create. Deployment takes 15–20 minutes. When it finishes, Host pools > hp-avd-lab > Session hosts shows avdlab-0 as Available.
Standard_D2s_v5 is Microsoft's minimum for a light workload; for more than 2–3 users at once, use Standard_D4s_v5 (4 vCPU, 16 GB) (sizing guidelines).
Phase 4 · 15 min
Users, app group and access roles
Entra-joined session hosts need one extra role on top of the app group assignment, or users connect and then see "The sign-in method you're trying to use isn't allowed".
| Who | Assign | Where | Why |
|---|---|---|---|
AVD-Lab-Users | Desktop Virtualization User (app group Assignments) | hp-avd-lab-DAG | Shows the desktop in Windows App |
AVD-Lab-Users | Virtual Machine User Login | rg-avd-lab | Lets users sign in to Entra-joined VMs |
AVD-Lab-Admins | Virtual Machine Administrator Login | rg-avd-lab | Local admin on the session hosts |
| Host pool managed identity or AVD service principal | Desktop Virtualization Power On Contributor | rg-avd-lab | Needed for Start VM on Connect |
- Single sign-on: Host pools >
hp-avd-lab> RDP Properties > Connection information > Microsoft Entra single sign-on = Connections will use Microsoft Entra authentication to provide single sign-on > Save. The RDP property behind it:enablerdsaadauth:i:1
- Start VM on Connect: host pool > Properties > Start VM on connect = Yes > Save.
Phase 5 · 15 min
Verify in Intune and connect as a user
All six ticked? The lab is ready. Your ticks are saved in this browser only.
Cost control and clean-up
| When | Action | Where |
|---|---|---|
| Every evening | Auto-shutdown (deallocates the VM) | VM avdlab-0 > Operations > Auto-shutdown |
| During use | Start VM on Connect powers it on for the first user | Host pool properties |
| Weekly | Check spend against the €10 budget | Cost Management > Cost analysis |
| Between uses | Delete the VM, its OS disk and NIC; keep host pool, workspace and VNet (they cost nothing) | rg-avd-lab |
| Next time | Host pool > Session hosts > Add one VM with the same settings; it joins Entra and enrols in Intune again | Host pool |
| End of the lab | Delete the device in Intune and Entra, then delete rg-avd-lab | Intune, Entra, Azure portal |
On the free account, Azure stops services when the USD 200 credit or 30 days run out unless you upgrade to pay-as-you-go; your budget alert still protects you after upgrading.
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| VM is Entra joined but not in Intune | MDM user scope not All, or subscription in a different tenant | Set MDM scope to All; check the subscription's directory is your Microsoft 365 tenant, then re-add the session host |
| The sign-in method you're trying to use isn't allowed | Missing Virtual Machine User Login role | Assign it to AVD-Lab-Users on rg-avd-lab |
| Web, Mac or phone client fails to sign in | Single sign-on not enabled | Turn on Microsoft Entra single sign-on, or add targetisaadjoined:i:1 (password-only fallback) (RDP properties) |
| Desktop not visible in Windows App | User not in the app group assignment | Add AVD-Lab-Users to hp-avd-lab-DAG > Assignments |
| Session host shows Unavailable | VM stopped, or agent still updating | Start the VM; wait 5 minutes; restart if it stays Unavailable |
| Intune policy shows Not applicable or fails | Template policy or update ring used on multi-session | Recreate it in the Settings catalog |
| VM doesn't start on connect | Power On Contributor role missing | Assign Desktop Virtualization Power On Contributor at resource group or subscription |
Adapting this lab to your tenant
The guide uses example names; swap in your own before you build.
| Example in this guide | Replace with |
|---|---|
contoso.com, [email protected] | Your domain and a licensed test user |
rg-avd-lab, hp-avd-lab, ws-avd-lab | Your own naming convention |
Session host prefix avdlab | Your prefix; update the AVD-SessionHosts rule to match |
10.20.0.0/16 | Any range that doesn't overlap your other networks |
| €10 budget | Your own monthly limit |
Sources: Microsoft Learn pages linked throughout this guide, checked 11 Nov 2026.
Want to build this live, with help?
This lab is part of my hands-on Azure Virtual Desktop and Intune training. Small batches, live online, real tenant.