Microsoft cloud
Custom image
Custom Windows image
A custom Windows image, in the context of Azure Virtual Desktop and Windows 365, is a pre-configured virtual machine image, built by an organisation rather than taken directly from the Microsoft-provided gallery, that bakes in applications, settings, and configuration.
Why Custom image matters in a Microsoft estate
Custom image matters because Microsoft 365, Azure, Windows 365, Teams, and related services are usually managed as one estate. The term connects to planning, cost, configuration, security, and day-two operational decisions across that estate.
How Custom image shows up in practice
Every new session host or Cloud PC provisioned from it then arrives in a consistent, ready-to-use state instead of a generic out-of-box Windows installation requiring post-deployment configuration. The alternative to a custom image is using one of Microsoft's Azure Marketplace gallery images directly, which is faster to get started with and requires no image maintenance. It leaves every application installation, Office activation, group policy configuration, and line-of-business tool deployment to run at first sign-in or through a separate post-provisioning configuration profile. This is workable at small scale but becomes slow and inconsistent as session host or Cloud PC count grows into the hundreds. Building a custom image typically starts from a Microsoft-provided base image, commonly the multi-session enabled Windows 11 Enterprise editions purpose-built for Azure Virtual Desktop, or standard Windows 11 Enterprise for Windows 365.
It then layers on required applications, removes unwanted default apps and services to reduce boot time and resource consumption, applies organisational branding and default settings, and is captured, generalised with sysprep, and published as a versioned image in an Azure Compute Gallery for reuse across provisioning policies and host pools. Image versioning and lifecycle management is where custom images demand ongoing operational discipline rather than being a one-off build task. Windows security updates, application version updates, and configuration changes all need to be rolled into new image versions on a defined cadence.
An organisation that builds one image and never revisits it accumulates a growing patch and update burden that then has to be caught up in a single disruptive pass, or worse, gets pushed onto post-deployment configuration profiles running redundant work at every sign-in that a properly refreshed image would have avoided entirely. The performance and cost implications of image quality are genuinely significant at scale: a bloated image carrying unnecessary background services, unneeded default Windows apps, or inefficient application installations directly increases boot time, per-session resource consumption on Azure Virtual Desktop's shared multi-session hosts, and effective Cloud PC sizing requirements on Windows 365. Image hygiene is therefore not a cosmetic concern but a direct lever on both compute cost and end-user experience across every host or Cloud PC provisioned from that image.