Citrix to Windows 365 Enterprise mapping

Citrix's BrokerMachine.json export (the primary machine inventory used throughout Compass) does not include CPU or memory sizing for a machine. That detail lives in a separate, optional export file: ProvisionedVirtualMachines.json, which is produced only when the environment uses Machine Creation Services (MCS) provisioning and the export script captures it. 

During snapshot processing, each entry in ProvisionedVirtualMachines.json is matched to its corresponding machine record by machine name (case-insensitive). From the matched provisioning record, three values are carried onto the machine's processed record: 

Because this data originates from an optional file, it is only available for machines that were provisioned through MCS and captured in that export. Machines provisioned manually or through PVS, or machines from an export that didn't include ProvisionedVirtualMachines.json, will have no sizing data. 

Not every machine in the environment is a meaningful candidate for a one-to-one Cloud PC size mapping. The table is filtered down to machines that are: 

Machines that fail any of these conditions (multi-session hosts, or single-session machines with no sizing data available) are simply excluded from this view rather than shown with placeholder values. This keeps the table focused on machines where a size recommendation is actually meaningful. 

Windows 365 Enterprise is sold in a fixed set of Cloud PC sizes, each defined by a vCPU count and a memory (RAM) amount (storage size does not factor into the sizing decision made here). Compass maintains an ordered list of these size tiers, from smallest to largest:

For a given machine, the recommendation logic walks this list from smallest to largest and picks the first tier whose vCPU count and RAM are both greater than or equal to the machine's source vCPU count and source RAM. In other words, it finds the smallest Windows 365 Enterprise size that can comfortably fit the existing Citrix machine's resource footprint, rather than the closest size by any other measure. 

If the source machine's vCPU count or RAM exceeds every available tier (larger than the largest published Windows 365 Enterprise size), the recommendation falls back to the largest available tier and the row is flagged with an Exceeds max indicator, so the analyst reviewing the table knows that a straight one-to-one mapping isn't fully possible and the machine may need to be split, resized, or reconsidered for a different migration target. 

If either the source vCPU count or source RAM is unavailable for a machine, no recommendation is produced (this should not occur for rows shown in the table, since the table is pre-filtered to machines with both values present). 

The list of Windows 365 SKU identifiers and their human-readable display names (for example, mapping a SKU part number like CPC_E_4C_16GB_128GB to Windows 365 Enterprise 4 vCPU, 16 GB, 128 GB) is a static lookup table maintained in the codebase. It was originally sourced from Microsoft's published licensing service plan reference documentation (Microsoft Learn's Entra ID licensing service plan reference), which lists Microsoft's official SKU part numbers and product names across all Microsoft 365 and Windows 365 offerings, not just Windows 365. 

Because this table is static, it reflects the Windows 365 Enterprise SKU catalog as it existed at the time the table was last updated. If Microsoft introduces new Windows 365 Enterprise sizes, both the sizing-tier list used for recommendations and the display-name lookup table will need a manual update to recognize them. 

If a SKU part number isn't found in the lookup table, the raw part number is shown instead of a friendly name, so the table degrades gracefully rather than showing a blank value. 

The Windows 365 Enterprise mapping table lists one row per qualifying machine, with the following columns: 

The table supports the same sorting, filtering, and pagination behavior as other data tables in the app, and includes a CSV export option so the mapping can be taken into a separate licensing or cost-planning exercise. The identical table (same columns, same filtering rules) is embedded in the generated HTML snapshot report, so the mapping is available for offline review without needing to open the live app. 

The Modeler tab's cost calculator estimates Windows 365 Enterprise costs using a single flat per-seat monthly rate, independent of individual machine size. It does not draw on the size-tier recommendation logic described in How a recommended Windows 365 Enterprise SKU is selected, so the per-machine SKU recommendations in this mapping table are a sizing exercise only and are not reflected in the Modeler tab's cost projections.