The Migration Readiness tab gives you an at-a-glance, per-delivery-group assessment of how ready your Citrix environment is to move to Azure Virtual Desktop (AVD) or Windows 365 (W365). Rather than manually cross-referencing provisioning methods, identity status, and access policies for every delivery group, Compass calculates a weighted readiness score for each one automatically from your uploaded Citrix snapshot, so you can quickly see which workloads are ready to migrate today and which need remediation first.
Note
The metrics on this page apply both to Citrix DaaS and Citric CVAD environments; both use the same tab layout and identical scoring rules - the tab simply reads from whichever snapshot is currently selected.
This article guides you through the following:
Everything on this tab is derived from a single processed Citrix snapshot (CitrixSnapshotData), which is itself built once, at upload time, from the raw JSON files inside the Citrix export ZIP. Nothing on the Migration Readiness tab calls out to a live API — it is all pre-computed during snapshot processing and then simply rendered by the tab.
The readiness calculation is done once per delivery group, using data assembled from several raw Citrix export files:
-
Delivery groups (
BrokerDesktopGroup.json) — the unit of analysis. Every row in the readiness tables represents one delivery group. -
Machines (
BrokerMachine.json), joined to their delivery group — used to determine provisioning method, session type, OS type, Azure hosting, image currency, and Entra join state for every machine in the group. -
Machine catalogs (
BrokerCatalog.json) — supplies each machine's provisioning type (MCS, PVS, or Manual). -
Access policies (
BrokerDesktopGroupAccessPolicy.json) — supplies the number of access principals and enabled access rules per delivery group, used for an access-complexity factor. -
Zones (
ConfigZone.json) — supplies zone health state for the zones a delivery group's machines run in. -
Published applications (
BrokerApplication.json) — counted per delivery group and also flows into the RemoteApps / Cloud Apps sub-tab. -
Desktop group usage samples (
BrokerDesktopUsage.json, optional) — powers the Utilization sub-tab; if this file was not present in the uploaded ZIP, the Utilization sub-tab simply has fewer rows (utilization is not required for the AVD/W365 scores themselves).
Because every one of these source files is optional in the ZIP contract, a delivery group with sparse source data still gets a row and a score — missing signals fall back to conservative defaults (for example, a delivery group with no zone data receives a neutral zone-health score rather than being excluded).
The Migration Readiness tab is structured as follows:
-
A Top Delivery Group Readiness section at the top of the tab, containing two side-by-side bar charts: Top Delivery Group Readiness (AVD) and Top Delivery Group Readiness (W365) (see "Top Delivery Group Readiness" summaries).
-
A tier legend describing the three readiness bands and their score thresholds.
-
Five sub-tabs, in this order: Utilization, Azure Virtual Desktop, Windows 365, Windows 365 Enterprise Mapping, and RemoteApps / Cloud Apps.
-
A collapsible Scoring Methodology & Weights panel at the bottom of the tab, closed by default, that documents every scoring factor and its weight for both models.
Both the AVD score and the W365 score use the same three-tier banding, with the following score thresholds:
|
Tier |
Score range |
|---|---|
|
High readiness |
80 and above |
|
Medium readiness |
60 to just under 80 |
|
Low readiness |
Below 60 |
Windows 365 has a fourth, special-case outcome: Not a candidate. This is a hard gate, described in The Windows 365 hard gate, and is distinct from simply scoring poorly — a delivery group in this state shows no numeric W365 score at all.
Tiers are shown as colored badges (green, amber, or red, plus grey for Not a candidate) next to each delivery group's score in both readiness tables, and the same color coding is reused in the bar charts and the tier legend.
A delivery group's AVD score and W365 score are each a weighted blend of several sub-scores, all expressed on a 0–100 scale. Every sub-score is computed independently for AVD and for W365 (they share some inputs but are weighted, and sometimes valued, differently) and then combined using a fixed weighting model.
The following factors and weights make up the AVD score (weights sum to 100%):
|
Factor |
Weight |
What it measures |
|---|---|---|
|
Provisioning Type |
38% |
How easily each machine's provisioning method migrates to AVD. Manually provisioned VMs score highest (they migrate directly); MCS-provisioned machines already running in Azure score high; MCS machines outside Azure score lower (they need an image migration step first); PVS-provisioned machines score zero, since PVS is not a direct AVD migration path. The delivery group's score is the average across all its machines. |
|
Session Model |
27% |
Multi-session machines score highest, since multi-session is AVD's primary use case; single-session machines still count, but at a reduced weight. |
|
Azure Hosted |
16% |
The proportion of the delivery group's machines that are already hosted in Azure (detected from the hypervisor connection), since those machines need no lift-and-shift. |
|
Azure Identity |
11% |
The proportion of machines that are Entra-joined, an AVD prerequisite. |
|
Access Complexity |
4% |
Derived from how many access principals and enabled access rules are configured on the delivery group's access policy — more principals and rules mean more validation work during migration, so complexity reduces the score (with a floor so it never fully zeroes out the group). |
|
Zone Health |
4% |
The proportion of the delivery group's associated zones that are reporting healthy. If no zone data exists at all, a neutral default score is used rather than penalizing the group. |
The following factors and weights make up the W365 score (weights sum to 100%):
|
Factor |
Weight |
What it measures |
|---|---|---|
|
Session & Assignment |
34% |
Statically assigned single-session machines score highest, since they map directly onto a W365 Cloud PC. Pooled (non-static) single-session machines score much lower, since W365 requires a personal assignment model. Multi-session machines score zero — W365 does not support multi-session workloads. |
|
Provisioning Type |
23% |
Same shape as the AVD provisioning factor, but weighted specifically for W365: Manual scores highest, MCS-on-Azure next, MCS-elsewhere lower, and PVS scores zero. |
|
Azure Identity |
23% |
The proportion of machines that are Entra-joined. Entra join is a hard requirement for Windows 365 Enterprise, so this factor carries much more weight in the W365 model than in the AVD model. |
|
Access Complexity |
11% |
Same access-policy-derived factor as AVD, weighted higher for W365. |
|
Zone Health |
9% |
Same zone-health factor as AVD, weighted higher for W365. |
Each factor's contribution to the final score is its sub-score multiplied by its weight, summed across all factors and divided by 100 — so the result lands back on the same 0–100 scale.
Before the weighted W365 score is even considered, every delivery group is checked for machines running an operating system that Windows 365 Enterprise cannot support: any Windows Server OS, or Windows 11 in multi-session mode. If the delivery group contains even one such machine, the entire group is marked Not a candidate — its W365 score is forced to zero and displayed as a dash rather than a number, regardless of how well it would otherwise have scored. This gate exists because Windows 365 Enterprise requires a single-session Windows 10/11 client OS; it is a hard technical requirement, not a matter of degree, so it overrides the weighted model entirely.
Alongside each score, the readiness tables show a short plain-language rationale explaining why a delivery group scored the way it did — for example, calling out how many machines are MCS-provisioned on Azure versus PVS-provisioned, how many are Entra-joined, and how healthy the group's zones are. This text is generated from the same inputs used for scoring, so it always matches the numbers shown in the row. When a delivery group is gated out of Windows 365 entirely, its rationale simply states the disqualifying condition (Windows Server OS or Windows 11 multi-session) instead of walking through the weighted factors.
At the top of the Migration Readiness tab, two bar charts sit side by side under a shared Top Delivery Group Readiness heading:
-
Top Delivery Group Readiness (AVD) — the ten delivery groups with the highest AVD scores, ranked highest to lowest.
-
Top Delivery Group Readiness (W365) — the ten delivery groups with the highest W365 scores, ranked highest to lowest. Delivery groups gated out as Not a candidate score zero and so naturally sort to the bottom, and are unlikely to appear unless fewer than ten groups qualify.
Each chart is a simple horizontal bar per delivery group: the delivery group name on the left, a proportional bar sized relative to the highest score in that chart, and the numeric score on the right. Because both scores are always on a 0–100 scale, each bar is additionally colored by the same tier thresholds used elsewhere in the tab: green at 80 and above, amber from 60 up to 80, and red below 60. If a snapshot has no delivery groups, the chart shows a simple No data placeholder instead of an empty chart.
These two charts are a summary view only — the full, sortable, filterable list of every delivery group (not just the top ten) lives in the Azure Virtual Desktop and Windows 365 sub-tabs described below.
A full data table listing every delivery group with its AVD readiness result: the AVD score (colored by tier), the tier badge, machine count, and each of the six underlying AVD sub-scores (Provisioning, Session, Azure Hosted, Identity, Access, Zone Health) shown as their own columns for transparency, followed by the plain-language rationale. The table supports the standard sorting, filtering, and pagination available on all Compass data tables.
The same delivery-group list, but built around the W365 score, tier, and W365-specific sub-scores (Provisioning, Session & Assignment, Identity, Access, Zone Health). Delivery groups that are gated out show a dash instead of a score, and their tier badge reads Not a candidate in a neutral grey rather than a color tied to score.
Collapsed by default at the bottom of the tab, this panel lists every scoring factor for both the AVD and W365 models as its own row, showing the model it belongs to, the factor name, its weight percentage, and a short rationale for why that factor is weighted the way it is. It also includes a dedicated OS Eligibility row for the Windows 365 hard gate described in The Windows 365 hard gate, noting that it carries no percentage weight because it operates as an override rather than a blended factor. This panel exists so that a reader can audit the scoring model without needing to inspect any code — the weights and rationale shown here are the same values used to produce every score in the tab.
Comments (0 comments)