Solution brief · Windows 365 and Cloud PC

Windows 365 Migration API Solution Brief

An API call does not make a migration programme ready. Source eligibility, user mapping, maintenance windows and cleanup still need decisions, so wrap a controlled wave around the supported Microsoft route.

Send me the solution brief

Enter your details and we will email your copy.

We will send the solution brief to this address.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

We use your details to fulfil this request and understand interest in our resources. Requesting the solution brief does not subscribe you to marketing. Read our privacy notice.

© 2026 EfficientEther Limited. Supplied for internal business use. Republishing, resale, or adaptation requires written permission.

Cover of the Windows 365 Migration API Solution Brief from EtherInsights

What this solution brief helps you decide

An API call does not make a migration programme ready.

Microsoft provides a supported route from eligible Azure virtual machines to Windows 365 Enterprise. What the route does not provide is the programme around it. Source eligibility, VHD preparation, user mapping, licensing, maintenance windows, status tracking and post migration cleanup are still decisions somebody has to make, agree and record.

This brief wraps a repeatable wave around the generally available Windows 365 Migration API. Sources are assessed against Azure virtual machine, operating system, disk, agent and tenant requirements before anything is scheduled. User mappings, approvals, maintenance windows and exception handling are agreed as a group. Status, history, duration and cleanup actions are retained for review before the next group starts.

The boundaries are stated plainly. Microsoft supports eligible Azure based virtual machines moving to Windows 365 Enterprise in the Commercial cloud, the Gen2 VHD snapshot covers only the operating system disk, and cross tenant access, third party agents and an Intune migration interface are not supported.

  • Which Azure virtual machine, operating system, disk and agent requirements decide source eligibility.
  • How to prepare user mappings, approvals and maintenance windows before the API is called.
  • How to track succeeded, failed and remaining source actions by owner.
  • Who reviews the results and authorises source cleanup once a migration group completes.
  • What the supported route does not cover, so exceptions surface before the wave rather than during it.

What you get

  • Two pages: where the decision gets difficult, what changes and how you measure it, and the four questions to settle first.
  • Three measures to track: sources passing validation, group readiness, and results and cleanup.
  • A scope statement covering the supported Microsoft boundary as announced in February 2026.
  • One live decision to test the approach on, using a small set of eligible Azure virtual machines.

Who it is for

IT leaders, migration leads, architects and MSPs moving Azure virtual machines to Windows 365 Enterprise. Written for the person who has to get a change approved as much as for the engineer who will run the wave.

Get the solution brief