Source estates are mixed
Some desktops are in Azure Virtual Desktop. Some are standalone Azure VMs. Others come from legacy VDI or custom image paths that need to be prepared before they can follow a supported Windows 365 import route.
Solution
Migrate legacy VDI and Azure VMs into Windows 365 with less manual risk.
VDI exits stall when every desktop, user, snapshot, schedule, and cleanup action is handled manually. EtherInsights gives teams a guided migration route built around Microsoft's Windows 365 migration API, with readiness checks, scheduling, status tracking, and post-migration evidence in one place.
AVD + VDI
migration planning for Azure Virtual Desktop, legacy VDI, and eligible Azure VM paths
API-led
built around Microsoft's Windows 365 migration API and Graph-based status visibility
Tracked
schedule, import, migration history, statistics, and cleanup in the same motion
The problem
Moving from VDI to Windows 365 is rarely blocked by one setting. It is blocked by coordination.
VDI exits stall when source desktops, users, snapshots, scheduling, and post-migration cleanup are managed as separate manual tasks. Azure Virtual Desktop, legacy VDI, standalone Azure VMs, and custom image paths each need validation before they can land safely in Windows 365.
Manual steps create risk
User mapping, snapshot preparation, licence assignment, maintenance windows, and cleanup decisions are easy to mis-sequence when every wave is coordinated outside the migration tool.
Progress is hard to defend
Teams need to know what was imported, what succeeded, what failed, how long each stage took, and which actions remain before the next migration wave.
Cleanup is often delayed
Original VMs, network interfaces, disks, and third-party VDI agents can remain behind because nobody wants to remove production dependencies without evidence.
How it works
A guided route from source VM to managed Cloud PC.
Select and validate the source
Start from existing Azure Virtual Desktop personal desktops, eligible Azure VMs, or a prepared custom VM path. Legacy VDI candidates can be assessed and prepared into a supported Azure VM/VHD snapshot route before import.
Map the user and prepare the import
Match source desktops to target users, check readiness, apply naming rules where needed, and prepare the snapshot-based Windows 365 import without rebuilding every step by hand.
Schedule the migration window
Plan migrations around maintenance windows, licence assignment, and user impact so the team can move in controlled waves rather than one-off manual jobs.
Track, review, and clean up
Follow import status, migrated Cloud PC history, duration statistics, and post-migration cleanup so the next wave has evidence rather than guesswork.
Migration operating view
Bring the source estate, target user, schedule, and result into one record.
EtherInsights turns the migration into a managed workflow: select eligible AVD or Azure VM sources, map users, prepare snapshot-based imports, track progress, review migrated Cloud PCs, and keep migration statistics ready for the next wave.
Product walkthrough
See Windows 365 migration and Cloud PC control together.
The current walkthrough shows the wider Cloud PC operating view. The migration page is designed to take screenshots from the dedicated migration workflow when those assets are ready.
- Use the migration workflow to select source VMs and target users.
- Track import and provisioning status rather than managing migrations from spreadsheets.
- Use history and statistics to plan the next maintenance window.
How we deliver it
EtherInsights leads the migration workflow.
Use EtherInsights when the question is how to move users from Azure Virtual Desktop, legacy VDI, standalone Azure VMs, or prepared custom VM paths into Windows 365 with less manual risk. EtherApps Forge supports application readiness where apps block the wave. EtherAssist supports day-two runbooks and troubleshooting once Cloud PCs are live.
EtherInsights started as the cost management platform for Microsoft 365 and Azure. It shows where spend is going, which owners need to act, and how to turn waste into savings. It now extends that operating view into full Windows 365 lifecycle support, plus tenant, user, security, device, and Intune reporting.
EtherApps Forge captures installed Windows applications from running systems, analyses the real application footprint, supports AI-guided packaging decisions, and produces deployment-ready outputs for modern environments.
EtherAssist gives IT and compliance teams the speed of AI without giving up data control, auditability, or practical governance. It supports troubleshooting, scripting, documentation, policy work, and repeatable internal support workflows.
Where this fits
- Azure Virtual Desktop personal desktop estates moving to Windows 365 Cloud PCs.
- Legacy VDI exits where Citrix, Omnissa, VMware Horizon, or standalone Windows VM paths need discovery and preparation.
- Azure VM-based desktops that need target-user mapping, scheduling, import tracking, and cleanup.
- Custom image or custom VM paths that need to become a supported Azure VM/VHD snapshot route before Windows 365 import.
- Migration waves where leaders need evidence on duration, success, failures, cleanup, and the next maintenance window.
Start here
Make the migration wave manageable before users move.
Start with a Windows 365 migration assessment, use the quick TCO calculator for the first commercial signal, then validate the source estate, schedule, and cleanup path inside EtherInsights.
- Microsoft documents the Windows 365 migration API as a REST-based route for Azure-based VM snapshot migration into Cloud PCs.
- The documented model supports VHD snapshot-based provisioning for Azure-based virtual machines; image-based imports are not currently available.
- EtherInsights wraps the operational work around that API route: discovery, readiness, user mapping, scheduling, tracking, history, statistics, and cleanup evidence.