Adopt AVD on measured headroom — not on Azure invoice surprise.
LoadGen ships a dedicated 7-step AVD wizard with native ARM discovery for Subscriptions, Resource Groups, and Host Pools. The same scenario shape that ran on Citrix runs on AVD — comparison overlay does the rest.
New Azure Virtual Desktop Profile
Step 1: Set profile name and basic settings
Profile Basics
Configure the basic settings for your Azure Virtual Desktop profile.
A unique name to identify this profile
Enable or disable this profile
The Problem
"AVD will be cheaper" isn’t a measurement.
Cloud desktop economics work — but only if you measured the host pool, sized the SKU, and validated FSLogix on the actual user shape.
AVD adoption built on guesses about Azure cost.
Without measured concurrency on the actual host pool, every spend forecast is a hand-wave — and Azure invoices arrive monthly, not annually.
Pilot pools that pass — production pools that don’t.
A 30-user pilot proves nothing about a 1,500-user finance close. Without parity testing across host pools, regression surfaces on cutover weekend.
FSLogix, brokers, and connection brokers all hide behind one URL.
Generic load tools see "AVD" — they don’t see the resource group, host pool, FSLogix profile share, or connection broker that actually breaks first.
How LoadGen handles AVD
Discover · Author · Migrate · Validate.
Four motions, every one Azure-native — from ARM discovery to FSLogix profile-load timing.
Discover
Native ARM-based discovery — Subscriptions, Resource Groups, and Host Pools surface in the wizard. No CLI scripts.
Author
The 7-step AVD wizard captures Azure-specific config — pool type, session host SKU, FSLogix share, connection broker auth.
Migrate
Run the same scenario shape that ran on Citrix. Wave-by-wave promotion behind a measured validation gate.
Validate
AVD-specific p95, login latency, and FSLogix profile-load time tracked alongside infra counters and Azure App Service uptime.
Live · Migration → AVD
Most teams adopt AVD by migrating. Validate every wave.
The migration cockpit pins your Citrix baseline against the AVD result for every wave — same scenario shape, side-by-side gate. AVD readiness becomes a measurement, not a status meeting.
Outcomes · before / after
Measured AVD adoption. Right-sized Azure spend.
Drawn from teams that ran the AVD wizard against real concurrency before signing the host-pool capacity plan.
Before
7 days
After
4 hrs
Before
±40 %
After
±5 %
Before
Guess
After
Tested
Before
8
After
1
AVD → Platform
Five features. One AVD practice.
AVD isn’t a feature — it’s the way these five compose into a measured cloud-desktop adoption.
- /config/load-profiles/new/wvd— 7-step AVD wizard
- /config/workloads— AVD workload versions
- /testing/active— Live AVD cockpit
- /testing/results— Citrix vs AVD overlay
- /monitoring/profiles— AVD UX validation
Load Profile Wizard
7-step AVD wizard with native ARM discovery — Subscription · Resource Group · Host Pool surfaced inline.
/features/load-profile-wizard
Agents
VDI agents (port 4841) for AVD pools — Activate, Reset, Kill operations on every session host.
/features/agents
SUT Monitoring
Bind FSLogix, AAD, and connection-broker counters to every test — Azure invoices line up with measured load.
/features/sut-monitoring
Uptime
Native Azure Function and App Service status checks alongside session-host availability — same audit trail.
/products/uptime
Analytics & AI
AI-flagged login-latency anomalies and Citrix-vs-AVD parity overlays — surface regressions before users report them.
/products/analytics-ai
Adopt AVD on numbers. Skip the invoice surprise.
Run the AVD wizard this afternoon. Compare Wave 1 against your Citrix baseline. Promote on a measurement — not a meeting.
