A futuristic cloud server displays a Windows desktop, command prompt, and an “Evaluation Software” label.
Microsoft has released a new Azure-hosted preview of its next server operating system. Windows Server vNext Datacenter: Azure Edition preview build 29706 is now available through the Microsoft Server Operating Systems Preview offer in Azure, in both Desktop Experience and Server Core versions. Microsoft announced it on November 17, 2026, alongside the broader build 29706 release. That broader release also brings new branding: the preview now carries the name Windows Server 2028.

This is a test build. Don't let a confident version number talk you into using it in production.

A futuristic cloud server displays a Windows desktop, command prompt, and an “Evaluation Software” label. What Microsoft actually shipped​

The Azure Edition announcement is short. It says the 29706 image can be deployed from the Microsoft Server Operating Systems Preview offer, in either the graphical Desktop Experience or the minimal Server Core version, and that Azure Edition is optimized to run in Azure. It doesn't mention pricing, Azure regions, VM sizes, deployment steps, or any new feature specific to the Azure image.

Most of the detail is in Microsoft's companion post, "Announcing Windows Server vNext Preview Build 29706." It describes 29706 as a new build of the next Windows Server Long-Term Servicing Channel (LTSC) preview, including:

  • Datacenter and Standard editions in both Desktop Experience and Server Core
  • Azure Edition, which Microsoft labels as being for VM evaluation only

The same post confirms the new name. The preview is now branded Windows Server 2028, but Microsoft asks testers to keep calling it "Windows Server vNext preview" when they report issues. Microsoft's broader launch messaging says "Today, we're introducing Windows Server 2028, in public preview now." Coverage on ElevenForum points customers who want earlier access to Windows Server 2028 features and direct contact with Microsoft's engineers to the Windows Server Technology Adoption Program (TAP).

In short: you get a new Azure Edition image in two installation options, a new product name, and an announcement with no Azure-specific feature list.

Why Azure Edition is its own track​

If you haven't followed Azure Edition, it differs from Standard and Datacenter in a few ways. Microsoft Learn describes it as an edition focused on innovation and virtualization and optimized for Azure. According to that documentation, it:

  • Gets yearly product updates through Windows Update rather than full OS upgrades
  • Runs only as a virtual machine
  • Is available only to Software Assurance, Windows Server subscription and cloud customers
  • Doesn't support Windows Server containers
  • Can't be switched back to a non-Azure Edition OS after installation without reinstalling

The same documentation lists the edition's main capabilities as Hotpatch, SMB over QUIC, Storage Replica compression and Azure Extended Network. Note that this Learn page currently applies to Windows Server 2022 and 2025. It explains the edition in general, but it doesn't prove that every listed capability or support term applies unchanged to the vNext preview.

What earlier vNext builds added​

The 29706 post itself lists only two new items: the Windows Server 2028 branding and the Feedback Hub app for Server Desktop users. The Feedback Hub app should update itself; if it doesn't, use "Check for updates" in the app's settings. Earlier builds in this series added more. 4sysops reported that Windows Server vNext preview builds from 29531 through 29621 introduce four notable additions, including ReFS boot and an NVMe-over-Fabrics initiator. Two caveats from that coverage:

  • ReFS boot requires UEFI firmware. Legacy BIOS boot is not supported, and Hyper-V Generation 1 virtual machines—which use legacy BIOS—cannot use ReFS boot volumes. You must use Generation 2 VMs.
  • For Windows Server vNext, Quick Machine Recovery is currently available for test mode, and Microsoft says a Group Policy option is planned for upcoming builds.

These features come from the general vNext build stream. Microsoft hasn't said which of them are present, enabled or supported in the Azure Edition 29706 image, so check them yourself rather than assuming they're there.

Known issues to read before you deploy​

TLS hybrid key exchange can crash LSASS​

This is the most serious known issue in the 29706 post. Microsoft reports a race condition in the TLS hybrid key-exchange implementation. It can crash the Local Security Authority Subsystem Service (LSASS) when a TLS server negotiates hybrid groups. The affected groups are:

  • X25519_MLKEM768
  • SecP256r1_MLKEM768
  • SecP384r1_MLKEM1024

These are the post-quantum hybrid groups that pair classical elliptic curves with ML-KEM. When LSASS crashes, the authentication service goes down with it. On a test VM running TLS endpoints, that means unexpected restarts and test results you can't trust.

Microsoft's temporary fix is to disable those three hybrid groups with the TLS cmdlets or Group Policy until a patch ships. No date for the fix has been given. The issue is listed for build 29706 as a whole, not just Azure Edition. If you're testing post-quantum TLS on purpose, keep in mind that the workaround turns off exactly the feature you're testing.

Upgrade paths: clean install from 29531 or later​

Microsoft says:

  1. Build 29531 is the new preview baseline. Upgrades from vNext previews older than 29531 aren't supported.
  2. Setup.exe doesn't technically block upgrades from build 26525 and older, but Microsoft warns of known problems. VMs may fail to upgrade or fail to start afterward, which can affect live migration and failover clusters.
  3. Build 29531 itself wasn't offered as a flight because of upgrade issues. Flighting resumed with build 29550.

If you have old preview VMs, deploy fresh ones instead of upgrading them. Microsoft doesn't describe a separate upgrade path for the Azure offer.

Server Core and the AppCompat FOD​

Server Core users may not be able to install the latest App Compatibility Feature on Demand (AppCompat FOD) after upgrading to build 29574. Microsoft says this seems limited to Server Core installations with third-party application licenses that fail compatibility checks after the upgrade, and that a future build will fix it.

Flight label shows Windows 11​

Microsoft also notes that the label on the flight may say Windows 11. If you select it anyway, it installs the Windows Server vNext update. Microsoft says to ignore the label.

How to get it and what you're agreeing to​

  • In Azure: deploy from the Microsoft Server Operating Systems Preview offer and choose Desktop Experience or Core.
  • Downloadable media: registered Insiders can use the Windows Server Insider Preview download page. Microsoft lists Azure Edition preview media in ISO and VHDX formats, English only. The LTSC preview comes as ISO in 18 languages and as VHDX in English. Separately, hartiga.de found that regional versions of the download URL can fail, noting the regional URL might not work (broken as of 16.08.2026). Make sure you use:.
  • Keys: preview keys work only on preview builds, and Azure Edition doesn't accept a key.
  • Expiration: Microsoft says the preview expires October 15, 2027. The post doesn't say whether that date applies separately to deployments from the Azure offer.
  • Support: this is pre-release software provided "as-is" and isn't supported in production. You're responsible for installing updates from Windows Update, and the Insider Terms of Use apply.

Sending feedback​

On Desktop Experience, use the Feedback Hub app for Windows Server. On Server Core, or if the app won't run on the server, use Feedback Hub on a registered Windows 10 or Windows 11 Insider device. Choose the Windows Server category and a subcategory, and put the build number in the title, for example [Server 29706] Title of my feedback.

Microsoft also asks testers to set diagnostic data to Optional during the preview. Server diagnostic data can be set to off, Required or Optional, and administrators can change it in Settings. If you're testing in a regulated tenant, check this setting against your data policies first.

Who should try it​

The new name suggests Windows Server 2028 is getting close, but build 29706 is still an evaluation build with:

  • An LSASS crash bug tied to the post-quantum TLS groups
  • A clean-install requirement for older previews
  • A Server Core AppCompat FOD issue still waiting on a fix

It's worth spinning up if you plan Azure IaaS standards, test line-of-business apps on the next LTSC release, or follow Azure Edition's capabilities. Keep it on throwaway VMs, disable the hybrid TLS groups unless you're testing them on purpose, and file bugs with the build number in the title.

 

References

  1. Windows Server Datacenter: Azure Edition preview build 29706 now available in Azure Windows Server Insiders 2026-11-17T18:41:20Z
  2. Windows Server Datacenter: Azure Edition preview build 29706 now available in Azure | Microsoft Community Hub techcommunity.microsoft.com
  3. Windows Server 2028 is now in Public Preview elevenforum.com