On November 17, 2026, at Microsoft Ignite, Microsoft put Windows Server 2028 into public preview as Insider Preview build 29706, according to its Windows Server Tech Community announcement. It also opened a separate preview that lets Microsoft Intune manage eligible Windows Servers alongside PCs. Both are prerelease and for nonproduction use only.
So should you test it? Yes, in a lab, with a reminder to check the current Insider build’s expiration before you rely on it.
What Happened With the Windows Server 2028 Public Preview
Microsoft announced the release on its Windows Server Tech Community blog. It documented the details on the What’s new in Windows Server 2028 Preview page. The changes that matter to admins fall into three buckets.
Secure-by-default Server Core. New Server Core installs ship with broader security hardening turned on by default, covering areas like network exposure, identity, privilege, remote access, cryptography, code integrity, and observability, according to Microsoft’s preview documentation. In practice, that means tighter out-of-the-box settings for SMB, firewall rules, credential protection, remote access, and logging. That means less manual hardening after install. It also means a legacy app that leans on NTLM or unsigned SMB can break on day one.
Storage and virtualization. Native NVMe storage support is enabled by default, and Generation 2 Hyper-V VMs get Trusted Launch boot-integrity protection. NVMe over TCP, NVMe over RDMA, and ReFS boot are separate, preview-stage capabilities in this release, not defaults, according to Microsoft’s documentation.
Management. PowerShell 7 ships next to Windows PowerShell 5.1, so your old scripts keep running. A new SMB Policy Controller lets admins apply a security or performance profile to a share. Servers can join Microsoft Entra ID through Settings > Accounts > Access work or school, the same flow used on Windows 11.
Microsoft also previews early AI inference support for the platform, along with plans to extend hardware compatibility to additional accelerators over time.
The Intune half
The Intune announcement covers compliance policies, settings catalog and administrative templates, and Win32 apps. It also covers Windows Update for Business/Autopatch, inventory, and some remote actions. You need an existing Intune and Entra ID subscription.
The scope is narrow. Only persistent, Desktop Experience physical servers and VMs qualify, per Microsoft’s requirement for persistent, single-session environments. Server Core is explicitly unsupported, and that same persistence requirement effectively rules out multisession, ephemeral, and nonpersistent hosts as well.
Enrollment is off by default, too. Device platform restrictions > Server devices ships set to Block.
There’s also a version mismatch. The get-started guide lists a minimum of build 29621.1000, but 29706 is the current announced build. Check the latest Insider build notes before you enroll anything.
How It Stacks Up
No Windows Server 2028 benchmarks have been published, vendor or independent. The more useful question is which management tool owns which server.
| Tool | Scope per Microsoft | Fit for 2028 Preview |
|---|---|---|
| Intune server management (preview) | Persistent Desktop Experience servers only | Lab pilots by teams already running Intune |
| Azure Arc | Recommended for production and business-critical servers | The production answer |
| Configuration Manager | Supported for released Windows Server versions | Intune co-management of servers isn’t in this preview |
Do you need Arc, Intune, or both? Microsoft says the two can run side by side. Arc is still the recommended tool for production servers. Microsoft also warns about mixing tools on one machine. Clashing settings from Group Policy, Configuration Manager, Arc, and Intune cause unpredictable behavior. Give each pilot box to one tool.
Cost is mostly admin time. Microsoft hasn’t published GA licensing for Windows Server 2028, and the Intune preview requires an existing Intune and Entra ID subscription. The hours go into the hardened defaults. You’ll spend them finding which apps still need NTLM or unsigned SMB.
The Reaction
Reaction is still forming. Early discussion mostly repeats the feature list, with little pushback so far.
Our Take
Verdict: Pilot. Don’t adopt.
Microsoft calls both previews nonproduction and time-limited, which rules out adoption for now. But Server Core shops shouldn’t hold off entirely. Depending on your workload, the new defaults can break assumptions your scripts and line-of-business apps make today — Microsoft’s own documentation frames this as a risk tied to legacy protocol use (NTLM, unsigned SMB), not a guaranteed outcome for every environment. Finding that in a lab costs an afternoon; finding it after GA costs an outage.
A sensible pilot is one Hyper-V host or a spare box with an NVMe SSD. Run a Server Core VM to test the hardened baseline. Run a Desktop Experience VM to test Intune enrollment. If you want to try NVMe over TCP, put a 10GbE network card on both ends. Treat every VM as disposable.
The Intune preview is worth an hour if you already manage PCs in Intune. If your servers are mostly Server Core, it doesn’t apply to you yet.
Wrapping Up
Join the Windows Server Insider Program and pull build 29706. Then run your existing hardening and app checks against a fresh Server Core install. Our read: the security defaults are the biggest change, and Intune for servers is a promising but narrow preview.
The last check for any pilot is a reboot after you apply your policies. Confirm the SMB, RDP, and firewall settings still match what you expect. Then compare again on the next Insider build.