Adopt AVD on measured headroom - not on Azure invoice surprise.
LoadGen ships a dedicated 7-step AVD wizard with Azure tenant / client / resource configuration and a Classic/ARM toggle. The same scenario engine that runs Citrix and Horizon 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 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 production-scale finance close. Without parity testing across host pools, regression surfaces on cutover weekend.
AVD hides real capacity behind a single tenant URL.
Generic load tools see "AVD" - they don’t drive the wizard, they don’t land per-session on the session host, and they don’t compare Citrix and AVD on the same scenario shape.
How LoadGen handles AVD
Discover · Author · Migrate · Validate.
Four motions on the same scenario engine (author, run, measure, compare), with the same agent fleet that runs Citrix and Horizon.
Discover
The 7-step AVD wizard captures the workload at scenario level. Azure tenant, client, and resource identifiers plus a Classic/ARM toggle.
Author
The same `.lgs` scenario that runs on Citrix and Horizon runs on AVD. Author once, replay on any supported stack.
Migrate
Run the same scenario shape that ran on Citrix. Compare Citrix and AVD side by side on one cockpit.
Validate
Generic p95 latency captured per transaction on every run. Azure Function and Azure App Service availability tracked separately as Uptime check types.
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
Guess
After
Measured
Before
Guess
After
Measured
Before
Guess
After
Measured
Before
Assumed
After
Evidenced
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.
Load Profile Wizard
7-step AVD wizard. Azure tenant / client / resource fields plus a Classic/ARM toggle. Same scenario engine as Citrix and Horizon.
/features/load-profile-wizard
Agents
VDI agents for AVD pools - Activate, Reset, Kill operations on every session host.
/features/agents
SUT Monitoring
Bind any Windows performance counter through the SUT Monitoring step, capacity correlates with infrastructure health on one timeline.
/features/sut-monitoring
Uptime
Azure Function and Azure App Service availability tracked as Uptime check types, on the same audit trail as your session-host availability.
/products/uptime
Analytics & AI
AI-flagged 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.
