A blue-lit data center showcases server racks, with holographic cybersecurity and network graphics.
Microsoft used Ignite 2026 to officially announce Windows Server 2028. If you've been running the Insider builds, the bigger news may be what's missing from the headline: several of the features Microsoft is now promoting have been sitting in preview builds for months. Microsoft's Windows Experience Blog says Windows Server 2028, now in public preview, extends the trusted foundation to the datacenter with new security hardening, including Trusted Launch virtual machines, post-quantum cryptography and a hardened OS baseline.

Neowin, which broke the story, says Microsoft is pushing several major improvements from security to storage performance, virtualization, and more, alongside its plans to bring AI inference capabilities directly to enterprise infrastructure. That's accurate. But this is a public preview, not a finished release. What Microsoft has formally committed to and what showed up in one outlet's feature list are not the same thing, and the gap matters. Here's what's confirmed, what has been around for a while, and what you should still treat as unconfirmed.

A blue-lit data center showcases server racks, with holographic cybersecurity and network graphics. The headline: a preview you can test now​

Microsoft gives two ways in. It tells organizations to test Windows Server 2028 in the Windows Insider Program for Windows Server, or apply to the Windows Server TAP for earlier access. The Technology Adoption Program (TAP) is for organizations that want to work directly with the Windows Server engineering team.

Neowin reports that the preview is available as Server build 29706. Microsoft's main Ignite announcement doesn't mention that build number, so check the version on whatever you download before you treat 29706 as official.

Neowin also reports a limit on the AI features: the hybrid AI capabilities are currently restricted to a limited early-access program, with specific hardware requirements. In practice, the security, storage and management features look like the parts most admins can try straight away. The local AI work looks gated for now.

Section summary: Server 2028 is officially in public preview through the Windows Server Insider Program, with TAP for earlier access. The build number and the AI early-access limits come from Neowin's reporting, not from Microsoft's main announcement.

Security: what Microsoft has confirmed​

Microsoft's own post names three security pillars:

  • Trusted Launch for virtual machines
  • Post-quantum cryptography
  • A hardened OS baseline

Trusted Launch isn't brand new to Insiders. Before Ignite, the Windows Server team's Tech Community post said several features you'll hear about at Ignite are already in Insider builds, and we've covered them here on Tech Community, including Trusted Launch for virtual machines, ReFS boot, and Windows NVMe-over-Fabrics initiator preview.

Neowin lists more items: a hardened Server Core configuration by default, a new security baseline, Trusted Launch for virtual machines, and Confidential VM support, plus work on automatic certificate management. Microsoft's Ignite blog doesn't spell out Confidential VM support, a Server Core-first default, or automatic certificate management. They may well be in the product, but wait for the release notes before you write any of them into a compliance plan.

Section summary: Microsoft has publicly confirmed Trusted Launch VMs, post-quantum cryptography and a hardened baseline. The rest of the security list is reported but not yet in Microsoft's own announcement.

Storage: NVMe and ReFS boot have been around for a while​

Microsoft has been preparing the storage changes for close to a year.

Native NVMe​

Neowin says native NVMe support is enabled by default in Server 2028. That matches what Microsoft has said before. In December 2025, Microsoft's storage team announced native NVMe for Windows Server 2025. The redesigned stack stops treating NVMe drives as SCSI devices, so the system no longer translates NVMe commands into SCSI commands. In Microsoft's own DiskSpd tests, Server 2025 with native NVMe delivered up to about 80% more IOPS and about 45% fewer CPU cycles per I/O on 4K random reads, compared with Server 2022. Microsoft's usual caveat applies: results vary by hardware.

The difference between versions is the default. Because Server 2025 is a shipped LTSC product, native NVMe there is opt-in. You need the October 2025 cumulative update or later, plus a registry override or Group Policy setting. A Microsoft engineer confirmed in the comments that the feature is enabled by default in the vNext Insider builds, which is what Server 2028 now ships with.

Two practical notes from Microsoft's original guidance:

  • Driver matters. The gains only apply to drives using the in-box Windows NVMe driver (StorNVMe.sys). If your vendor supplies its own driver, you won't see a difference.
  • How to check it worked. With native NVMe active, NVMe devices appear under "Storage disks" in Device Manager. Microsoft suggests comparing before and after with DiskSpd and the Performance Monitor counter Physical Disk > Disk Transfers/sec.

NVMe over TCP and RDMA​

The NVMe/TCP and NVMe/RDMA transports Neowin mentions first appeared in March 2026. That's when Microsoft added a basic, in-box NVMe-over-Fabrics initiator to Insider builds and described it as early and meant for evaluation. One known problem was that connections didn't survive a reboot. In October, a Microsoft engineer said the fix would be in the Insider build released for Ignite. If you gave up on NVMe-oF because you had to rerun connection commands after every restart, it may be worth trying again. In the same discussion, NVMe over Fibre Channel was described as below the current priority line, so FC shops shouldn't plan around it yet.

ReFS boot​

Microsoft announced ReFS boot for Windows Server Insiders in February 2026. You can format the C: partition as ReFS directly in Setup, starting with build 29531 (the Insider builds from February 11, 2026). Microsoft's selling points include online integrity checking without chkdsk, metadata checksums, and volume sizes up to 35 PB, compared with NTFS's typical 256 TB limit. It also says block cloning creates fixed-size VHDX files dramatically faster.

The requirements, according to Microsoft:

  • UEFI firmware is required. Legacy BIOS isn't supported, so Generation 1 Hyper-V VMs are out.
  • Secure Boot is not required, according to a Microsoft reply in the comments.
  • It works with native NVMe, according to the same reply.
  • To check it worked, run fsutil fsinfo volumeInfo C: after installation, or open the drive's properties.

Section summary: The storage features are real and documented, but they've been in Insider builds since earlier in 2026. What's new with Server 2028 is that they're becoming part of the official next release, and native NVMe is on by default.

Management: Intune for servers and vMode reaches GA​

Microsoft's management pitch is ambitious. Its Ignite post says that for the first time, endpoint teams can manage servers and PCs as one Windows fleet with Intune and Windows Autopatch, while infrastructure teams use Azure Arc. Neowin describes Intune management for Windows Server as being in preview, covering configuration, compliance, apps and updates for "eligible persistent servers." Read "eligible" as a real limit: not every server will qualify.

Windows Admin Center Virtualization Mode (vMode) is a separate milestone that arrived the same week. Microsoft declared vMode generally available on November 16, 2026, in Windows Admin Center version 2611. According to Microsoft, one vMode instance can manage up to 1,000 Hyper-V hosts and 25,000 VMs. The release adds bulk Azure Arc onboarding, encrypted backup and restore of the vMode management database, and certificate management through Active Directory Certificate Services. Administration Mode (aMode) is still the tool for hands-on work with individual servers. vMode is for running a whole Hyper-V environment.

Microsoft says plainly why it built vMode: licensing changes and renewal uncertainty have pushed many organizations to look for alternatives to their current virtualization platform. Microsoft also says VMware ESXi-to-Hyper-V conversion is coming to vMode in private preview. vMode is a Windows Admin Center release, not a Server 2028 feature, but it clearly fits the same strategy.

Section summary: Intune and Autopatch for supported servers is in preview. vMode is generally available now and works with your current Hyper-V estate.

AI: "token factories" in your datacenter​

This is the part Microsoft wants you to remember. It says it is extending Microsoft Foundry to Windows Server 2028 and expanding hardware choice. On hardware, AMD's MI350P accelerator will be available in preview in the first half of 2027 for Windows Server 2025 and later, and NVIDIA DGX Station for Windows, with the GB300 Grace Blackwell Ultra Desktop Superchip and up to 748 GB of coherent memory, will support Windows Server 2028 at general availability.

One detail that's easy to miss: MI350P support isn't limited to Server 2028. Microsoft explicitly includes Windows Server 2025, so if you've just deployed 2025, you won't need to upgrade to test it.

Microsoft's Azure team describes the goal this way: Windows Server 2028 enables AI inference alongside business-critical applications and data, while Windows PCs bring intelligence directly to the devices where people work through local processing.

Neowin also lists support for open-weight and custom models through Foundry Local, Windows ML, vLLM and llama.cpp. Microsoft's main announcement names Microsoft Foundry and gives NVIDIA Nemotron as an example model, but it doesn't confirm that full framework list. Treat it as reported, not confirmed.

Is this a real shift or Ignite buzzword bingo? Some of each. Running inference next to sensitive on-premises data addresses real data-residency and cost problems. But the hardware is still months away, access is gated, and no general availability date has been announced.

Section summary: The AI story is the most ambitious part of the release and the least finished.

What admins should do now​

  • Set up an Insider lab. Install the preview on spare UEFI hardware or Gen 2 VMs. Don't put it into production.
  • Benchmark native NVMe. Compare against your current Server 2025 baseline, and confirm your drives use StorNVMe.sys.
  • Try ReFS boot on non-critical systems. Test your backup, imaging and monitoring tools, because some third-party agents may assume the system drive is NTFS.
  • Look at vMode if Hyper-V consolidation or a move away from VMware is on your roadmap. It's generally available today.
  • Consider TAP if your organization wants to work directly with Microsoft's engineers on AI workloads.

The Windows Server team will go deeper at Ignite in session BRK418, which covers Hyper-V, Active Directory, storage, and networking, and how the next release raises the bar for security, performance, and AI.

Bottom line​

Windows Server 2028 is official and testable. The storage work is the most mature part, which makes sense because it has been in Insider builds for most of the year. The security baseline sounds promising, Intune for servers could genuinely help organizations where endpoint and server teams manage separately, and the AI plans depend on hardware and access that aren't broadly available yet. Test the preview now, but wait for Microsoft's release notes before you treat the reported-but-unconfirmed items as commitments.


Update: Hardened Server Core defaults detailed for build 29706 (November 18, 2026)​

Neowin now reports that Windows Server Insider Preview build 29706 ships with a hardened Server Core configuration enabled by default, turning on hundreds of security settings at deployment rather than requiring organizations to apply their own baseline scripts.

According to Neowin, the default policy favors Kerberos over NTLM, protects LSASS, requires SMB signing and encryption, keeps the firewall enabled across profiles, disables legacy name resolution and unauthenticated RPC, and blocks weaker WinRM options. It also reportedly tightens TLS cipher choices, introduces hybrid post-quantum key exchange using ML-KEM, encrypts the paging file, and expands auditing and PowerShell logging.

The practical trade-off is compatibility. Legacy protocols, unsigned workflows, older remote-management tooling, and scripts that assume relaxed defaults may fail until admins selectively relax policies. Microsoft is reportedly delivering the controls through OSConfig and Group Policy, with the MSHardenedPolicyEval tool intended to show which hardening settings apply. A score below 100% does not necessarily indicate a misconfiguration while that evaluation tool remains incomplete.

This makes the hardened baseline more concrete than the earlier high-level announcement, but it remains preview software: test application dependencies and management workflows before treating these defaults as production-ready.


Update: Additional details (November 18, 2026)​

BleepingComputer reports that Microsoft has explicitly described Confidential VM support as an early step toward integrity-protected runtimes on supported confidential-VM hardware. That is a firmer statement than the initial Ignite overview, which did not detail Confidential VM support. The hardened Server Core profile also includes strong passwords and account lockout policies, removes consumer accounts, limits installer self-elevation, prevents Guest sign-in, and requires RDP connections to use Network Level Authentication and TLS.

Microsoft has also clarified that the default hardening work is not complete. According to BleepingComputer, NTLM blocking, hardware-backed platform protection, additional print and RPC hardening, and other settings remain in development. That distinction matters for administrators: build 29706 establishes a substantially stricter baseline from first boot, but it should not yet be treated as the final security configuration planned for Windows Server 2028.


Update: Microsoft details how admins can assess and roll back Hardened Server Core policies (November 18, 2026)​

Microsoft’s Windows Server team has now documented the in-box controls behind Hardened Server Core in build 29706. The MSHardenedPolicyEval PowerShell module can score the server’s enforced configuration by category, while Set-MSHardenedPolicy reapplies hardened values and Restore-MSHardenedPolicy removes them for a selected category or the entire server.

The rollback option is important for compatibility testing: restoring a category returns it to standard Windows Server behavior, rather than restoring an organization’s prior custom configuration. Microsoft advises using these commands only on unmanaged systems; where OSConfig, Group Policy, or another management platform owns the configuration, admins should use the evaluation tools for scoring only to avoid conflicting policy enforcement.

Microsoft also warns that gpresult and RSOP can show the built-in defaults as “Not Configured” because the policies are embedded in the image rather than delivered through a .pol file. MSHardenedPolicyEval is the intended way to see the effective state.

Early scores may remain below 100 percent even on correctly configured systems, because some controls are not yet measured and domain controllers can report certain KDC-related settings as unmet. Microsoft says the module and command names may change in later Insider flights.

 

References

  1. Microsoft launches Windows Server 2028 with native NVMe, ReFS boot, and more features Neowin 2026-11-17T19:22:01+00:00
  2. Microsoft announces Windows Server 2028 with hardened security BleepingComputer 2026-11-18T04:24:31-05:00
  3. Windows Server 2028 will be secure by default, which could break some workflows Neowin 2026-11-18T07:08:01+00:00