The GA release adds Azure Arc onboarding, built-in backup and restore, and certificate management through Active Directory Certificate Services (AD CS). Administration Mode (aMode), the familiar Windows Admin Center, also gets resilience and security fixes and a redesigned Azure registration process. Microsoft says vMode comes at no additional cost.
This article covers what is generally available, what is still in preview, and the details to know before deploying it.
How vMode got here
vMode took about a year to reach GA. Microsoft's Windows Admin Center team wrote that at Microsoft Ignite 2025 we announced our first public preview of Windows Admin Center: Virtualization Mode. Public Preview 2 followed in April 2026, and Microsoft refreshed it in June.
GA arrived later than some early observers expected. A Medium analysis published around the first preview listed GA as targeted for Q2 2026, with the complete vMode feature set. The same writer expected that the VM Conversion tool reaches General Availability at the Public Preview 2 milestone. That did not happen. VM Conversion is still headed to private preview, which is covered below.
One earlier promise was kept. During the preview, Microsoft said that Administration Mode (Windows Admin Center 2511) and Virtualization Mode are currently separate installers. Once Virtualization Mode is generally available, the installers will be unified and will include an option for mode selection. In version 2611, both modes share one installer and you choose a mode during setup.
Section summary: vMode moved from an Ignite 2025 preview to GA in November 2026. It shipped later than some outside forecasts, and Microsoft delivered the unified installer it promised.
aMode vs. vMode: two tools for different jobs
vMode does not replace classic Windows Admin Center. Microsoft says Administration Mode is still the right tool for hands-on work on individual servers. vMode is meant for running a whole virtualization environment.
The Microsoft Learn overview explains the architectural difference:
| Area | Administration Mode | Virtualization Mode |
|---|---|---|
| Purpose | General server administration (Device Manager, Registry, Roles & Features) | Virtualization fabric management (hosts, clusters, VM lifecycle, Network ATC) |
| Connection model | Stateless, per-session WinRM/PowerShell connections | Stateful, with a database and agents on managed hosts |
| Typical scale | Roughly 1–50 hosts | Up to 1,000 hosts and 25,000 VMs per instance |
| Operations | Remote PowerShell at runtime | Parallel operations through a local agent |
The two modes must be installed on separate systems. In vMode, a web gateway handles authentication, request routing and a stateful database, and agents on Hyper-V hosts carry out the work. TLS secures the traffic between the gateway and the agents. In earlier preview coverage, 4sysops described vMode as deployable as a stateful appliance with an integrated PostgreSQL database. The GA upgrade instructions mention PostgreSQL credentials, which fits that description.
The Microsoft Learn overview was updated on the GA date but still shows a banner saying vMode is "currently in PREVIEW." Given the official announcement, that banner looks like a documentation label that has not been updated yet. It does not mean the product is still in preview.
What is generally available in version 2611
Navigation built around resource groups
vMode has one navigation hierarchy with Compute, Storage and Networking views. Resource groups are the top-level containers and work like folders. Keep these rules in mind when planning the structure:
- Every resource belongs to a resource group.
- Resource groups do not nest.
- Each host belongs to exactly one resource group.
- Users see only the resources that role-based access control allows them to see.
If you are used to nested folder trees in other hypervisor consoles, plan a flat set of groups by site, environment or workload before you onboard anything.
Add Resource: a guided onboarding wizard
Microsoft's guided Add Resource workflow can onboard three kinds of compute:
- Standalone Hyper-V hosts that are not part of a failover cluster.
- Existing clusters. Enter the cluster FQDN and vMode finds and onboards every member node.
- New clusters. vMode builds a failover cluster from two or more standalone hosts during onboarding.
To start, select the ellipsis (...) next to a resource group and choose Add Resource. The wizard moves through these steps:
- Getting started: choose the Compute profile, validate host or cluster FQDNs, and turn on Clustered if you are creating a new cluster.
- Clustering: confirm the existing cluster settings, or name the new cluster and choose DHCP or static IPs.
- Networking: bind Network ATC intent templates to physical adapters. This step is skipped for hosts that will stay standalone.
- Storage: choose a storage option or use storage already connected to the hosts.
- Compute: set enhanced session mode, concurrent live migrations and the default VM path.
- Review: check the selections, then select Submit.
Microsoft has published a companion post on the networking changes since preview. It says admins can review existing intent status, refresh the Networking page in Add Resource to retrieve host-side changes without restarting the wizard, and specify Storage VLANs when creating network intent templates.
Note: editing a Network ATC intent template affects only future deployments. Intents already set on hosts or clusters stay as they are. To change deployed intents, use the Network ATC PowerShell cmdlets.
Storage: three supported types, with different limits
- Windows Scale-Out File Servers: vMode validates the share and installs its agent on the file server. It can also set share permissions and SMB delegation so live migration works. If Active Directory permissions are missing, it tells you so you can set delegation up manually.
- Non-Windows SMB file servers: vMode checks that the UNC path exists and is reachable. Permission and delegation options are not available for these servers.
- Fibre Channel and iSCSI SANs: register the SAN by hostname. When you onboard connected hosts, vMode scans shared LUNs and shows which are ready, which it can configure, and which need manual work.
The Learn documentation adds that hyperconverged storage configuration is not available yet. If you run Storage Spaces Direct, check the documentation before assuming vMode covers your setup.
Workflow tracking, resume and retry
Onboarding can involve host reboots, so vMode includes a workflow status pane, opened from the header bar. It shows each step's progress, required reboots and error details. If a service disruption pauses a workflow, you can resume it where it stopped. If a step fails, fix the cause and retry the step, as long as rerunning it will not disrupt the rest of the workflow.
RBAC and Windows permissions
Users sign in to the gateway with their Active Directory accounts through Windows authentication. vMode RBAC then decides what each person can do. Roles can be assigned at the gateway root, a resource group, a cluster or a host, and they apply to everything below that level. There are three built-in roles:
- Global Administrator: full control of the gateway, including access, resource group structure, certificates, and backup and restore.
- Fabric Manager: day-to-day fabric work within an assigned scope, such as adding hosts, managing templates and onboarding machines to Azure Arc.
- Reader: view-only access within an assigned scope.
Two points can cause problems on day one. Right after installation, only the installing account has access, so assign roles before you tell the team the tool is ready. Also, vMode roles do not replace Windows permissions. Users still need administrative rights on the hosts they manage.
Backup and restore of the management database
Backups are encrypted and password-protected. They contain the management database: inventory, cluster metadata, gateway configuration, RBAC settings, templates and operational state. You can save them to a local folder or a UNC share. Start from Overview > Backup & Restore.
Restore recovers only the management database. It does not roll back servers, clusters, VMs, storage or networks. vMode reads the current state of those resources as agents reconnect, so this is not a VM backup product. If you lose the backup password, the backup cannot be restored, so store the password somewhere other than next to the file.
During the preview, StarWind's overview noted no linked-mode/high-availability for the gateway yet — planned for GA. Microsoft's GA announcement focuses on backup and restore for gateway recovery and does not describe gateway high availability. Anyone sizing a 1,000-host deployment should confirm with Microsoft how a gateway failure is handled.
Global search
Search covers resource groups, hosts, clusters and VMs, and it supports three syntaxes:
- Basic: partial names, with
*as a wildcard. - Hierarchical: for example
/ResourceGroup1/Cluster1: web. Wildcards are not allowed in the path. - Object type: for example
[Virtual machine]: WS2025.
Search follows RBAC. Deleted resources and attached objects such as virtual hard disks do not appear in results.
Azure Arc onboarding and a new registration flow
You can select many hosts, apply one set of Azure settings (subscription, resource group, region, cloud environment and optional tags), and vMode installs the Azure Connected Machine agent on each one. Each machine gets its own workflow, so one failure does not stop the others. In this release, machines connect through a public endpoint, either directly or through a proxy.
The redesigned Azure registration asks only for the permissions the current user and task need. It does not require tenant-level administrator consent. Azure RBAC can still limit who performs Azure operations. aMode users can find the redesigned registration in gateway settings under Register.
Certificates through AD CS
Self-signed certificates are still fine for testing. For production, you can now issue and automatically renew vMode certificates through AD CS using your existing templates. Go to the gateway settings and open the Certificates tab. Automatic renewal reduces the risk of an outage from an expired certificate.
Hyper-V Replica management
Version 2611 adds Hyper-V Replica management to vMode:
- Replica Brokers and replication over HTTP or HTTPS.
- Per-disk selection, replication frequency and recovery-point retention.
- Test failover on an isolated copy, without interrupting the original VM.
- Planned and unplanned failover.
- Reverse replication for failback.
- Extended replication to a third site.
Section summary: most day-to-day fabric management, including onboarding, storage, RBAC, search, Arc, certificates and Replica, is generally available. Read the limits on restore, permissions and template edits before relying on them.
What is still in preview
- Replication Monitor is entering private preview. It adds a combined view of replication health and test-failover status, and you sign up by email.
- VM Conversion, the VMware ESXi-to-Hyper-V migration tool, is moving to an appliance-based design in private preview through the Windows Server TAP. It replaces the earlier preview extension and adds prechecks, data sync before cutover, and batch moves.
Microsoft's announcement presents vMode against organizations reconsidering their virtualization platform after licensing changes. Teams leaving VMware should note that the migration tool built for that move is not generally available yet.
Upgrading: update the gateway and the agents follow
- Back up the vMode environment, or take a checkpoint if the gateway runs in a VM.
- Run the latest Windows Admin Center installer on the gateway machine.
- Reuse your existing PostgreSQL credentials when prompted.
- After the upgrade, sign back in and confirm the version under Settings > About.
- Watch the agent health indicators. Agents on managed hosts update automatically. If any show as disconnected, use the troubleshooting documentation.
The in-place upgrade keeps resource groups, managed hosts, templates and access assignments.
Developer and partner updates
The SDK has moved to 6.0.0. Microsoft says it features two major updates: commands for upgrading existing Windows Admin Center extensions to Angular 20 as well as commands for creating and testing React-based Windows Admin Center extensions.
Partner extensions have also been updated:
| Extension | Version | Main changes |
|---|---|---|
| Dell OpenManage Integration | 3.8.0 | Supports 2611 in both aMode and vMode; adds PowerEdge R9815 and R9825 support |
| Dell APEX Cloud Platform | 3.0.7 | Security hardening; certificate-expiry fix |
| Dell PowerPath | 3.0.0 | Moved to Angular 15 |
| Lenovo XClarity Integrator | 5.2.1 | Adds FX650 V4 and FX630 V4 systems and ThinkAgile MX Best Recipe 2605; fixes cluster-consistency and compliance bugs |
| Everpure FlashArray | 1.1.180 | Arrays must be registered by a gateway administrator; existing connections migrate automatically |
Should you deploy it?
Teams running Hyper-V without System Center Virtual Machine Manager are the main audience. A free, central console with RBAC, encrypted state backup, PKI-managed certificates and bulk Arc onboarding fills a real gap for them. Large shops should still check three things before moving production management to it:
- Gateway resilience: the GA announcement does not describe gateway high availability.
- Hyperconverged storage: the documentation says it is not supported yet.
- VMware migration: VM Conversion is still in private preview.
A reasonable plan is to deploy vMode in a lab or a single resource group first. Assign RBAC roles right away, take a backup and store its password separately, and check the known-issues documentation before expanding. Microsoft's own documentation still had a preview banner on launch day, so check the release-specific known issues before rolling it out widely.
References
- Virtualization Mode in Windows Admin Center is now generally available! Windows Admin Center Blog · 2026-11-16T22:30:00+00:00
- How to install Windows Admin Center vMode on Windows Server 2025 4sysops.com
- Windows Admin Center Virtualization Mode: Microsoft’s Bold Answer to VMware Migration medium.com