I'm trying to understand what the preview actually supports and what could catch us out when testing it. Can it manage existing Windows Server installations, and how much of the usual Intune setup applies?
Has anyone looked at the Intune preview for Windows Server?
Answers
Not existing Server 2022 or 2025 installations. The preview is for Windows Server vNext Insider builds 29621.1000 or later, with Desktop Experience. Server Core isn't supported. Microsoft recommends using it only for non-production testing in a test tenant.
Enrollment needs a user, so userless, bulk and Autopilot enrollment are out. There's no extra license required during the preview, although automatic enrollment still needs Entra ID P1 or P2.
Reply to this answer
The assignment scope is the bit I'd check first. Policies assigned to All devices, users or dynamic groups can reach an enrolled server. Putting servers in their own group doesn't automatically exclude them from those assignments.
There are operatingSystemSKU filter values for server editions, but scripts and policy sets don't support filters. Export and review assignments before enrolling, even in a test tenant. Also, enrollment through Add work or school account requires the restriction to allow personally owned devices as well as Server devices.
Reply to this answer
There's a decent management surface, but don't read it as full feature parity. Compliance policies can provide a Conditional Access signal, and you can use supported Settings catalog options and custom OMA-URI profiles. Endpoint security includes antivirus, firewall, disk encryption, LAPS and attack surface reduction. Win32 apps and Company Portal are supported too.
One wrinkle is that configuring firewall and antivirus settings is supported, but firewall, antivirus and antispyware compliance checks aren't. Endpoint Privilege Management, Resource Explorer and ConfigMgr co-management aren't supported either. You also can't move a server directly from Defender security settings management to Intune.
Reply to this answer
For an Azure VM, check who has Intune permissions before enrolling. Someone with the appropriate Intune role can perform remote actions, including wipe, without needing Azure RBAC or just-in-time access to the VM.
Also watch for overlapping settings if Azure Update Manager or Azure Policy is managing the same machine. Intune can conflict with those tools.
Reply to this answer
Add your answer
Answers are reviewed before publication.
_k37+zavluno.6:
So update rings work, but does that include the separate quality and feature update policies?