First: Insider only, not public yet
- Status: Insider Preview. The capability shipped in Intune service release 2611 (week of 16 Nov 2026) and was shown at Ignite. It is opt-in, and works only on Windows Server Insider Preview builds.
- When it goes public: Microsoft has not published a date for a public preview or for general availability (GA). Future licensing has not been announced either.
- Support: testing and evaluation only. Microsoft does not support production use, and the builds may change substantially before commercial release.
- An important distinction: Windows Server 2028 Preview (build 29706, 17 Nov 2026) is available to anyone who registers for the Windows Server Insider program. The Intune capability is a separate preview that works only on those builds.
What it is
Until now Intune was built for user PCs and mobile devices, and servers were managed with other tools. The preview lets you manage Windows servers in the same console, with the same workflows and policy model as Windows PCs. The focus is servers that behave like endpoints, meaning servers with an associated user identity.
Which servers are supported
- Active Directory servers: AD-joined servers in environments that use Entra Connect (hybrid join).
- Entra ID servers: servers joined directly to Entra ID, with no AD DS dependency.
- Servers used as workstations: privileged access workstations (PAWs), jump boxes, Remote Desktop Session Hosts, development and test systems, and factory-floor terminals.
- Edge and branch servers: distributed servers at retail sites and branch offices.
- Azure Virtual Desktop Hybrid: one RDSH session per device. Multiple concurrent sessions are outside this preview.
What you need
- Licensing: an existing Intune and Entra ID subscription. Microsoft states that no additional subscription is required for the preview, and that this does not describe future licensing terms.
- Build: Windows Server vNext Insider Preview, build 29621.1000 or later according to Microsoft's guide. The current announced build is 29706, so check the Insider release notes before you start.
- Installation type: Desktop Experience only, physical or virtual, persistent single-session.
- Access: local administrator on the server, and a test user.
- Network: connectivity to the Microsoft services needed for enrollment and management. Disconnected (air-gapped) servers are not included.
- Hybrid setups: a synchronized domain user with an Intune license, and Entra ID P1 or P2 for automatic enrollment.
What is supported
| Area | Supported in the preview | Not included |
|---|---|---|
| Enrollment | Entra join from Settings, or hybrid join with automatic enrollment through Group Policy | Autopilot, MDM-only enrollment, bulk enrollment, userless enrollment and automatic enrollment of co-managed devices |
| Configuration | Supported settings catalog groups, Endpoint security templates (Antivirus, Disk encryption, Firewall, Local admin password solution, Attack surface reduction), Device restrictions or Kiosk, custom profiles, and ADMX templates for Edge, Firefox, Chrome, Microsoft 365 Apps, OneDrive and Adobe Acrobat | Settings the CSP in the build does not support. Validate each setting on the server |
| Compliance | Supported compliance policies, with the result used as a Conditional Access signal | Firewall, Antivirus, Antispyware and Configuration Manager compliance checks |
| Updates | Update ring settings of Windows Update for Business (and Windows Autopatch): automatic updates, notifications, preview build controls, quality update deferrals, deadlines, maintenance windows and restart behavior | Quality updates, Feature updates and Driver updates policies |
| Apps | Win32 apps with status monitoring, and Company Portal | Only Win32 is listed. Other app types are not covered |
| Inventory and status | Device inventory, and policy, app and compliance status | Not detailed beyond that |
| Remote actions | Sync, Restart, rotate BitLocker keys, rotate local administrator password, Retire, Delete, Wipe, collect diagnostics, and Defender scan and update | Other actions may appear in the console but do not work |
What is not included at all
- Server Core: not supported.
- Non-persistent hosts: multisession, ephemeral and non-persistent hosts are not included.
- Released versions: the feature requires Insider builds, not released Windows Server versions.
- MMPC: features that depend on this protocol, such as Endpoint Privilege Management and Resource Explorer.
- Configuration Manager: co-management with Configuration Manager is not included.
- Defender: moving servers from Defender security settings management to MDM enrollment is not supported yet.
- OMA-DM is not blocked. Features that depend on this protocol are not blocked on enrolled servers, so policies not designed for servers can apply to them. This is the biggest risk in the preview.
- Sign-in methods. Web Sign-In is excluded. Windows Hello for Business is excluded for local sign-in but works for remote sign-in over RDP. Smart card, FIDO2 and YubiKey in PIV mode are included.
- DEM accounts are not supported for Group Policy automatic enrollment on servers.
- Excluded compliance checks (Firewall, Antivirus, Antispyware and Configuration Manager) can report Error or Not applicable if you configure them. Leave them Not configured.
Enrollment and separation from PCs: where it goes wrong
- Blocked by default. In Device platform restrictions, set Server devices to Allow. To enroll through Settings > Accounts > Access work or school, you must also allow Personally owned devices, but that opens personal-device enrollment for everyone the profile applies to. Microsoft offers two ways to keep personal devices blocked: add an assignment filter on the deviceOwnership property that blocks personally owned Windows devices, or configure corporate identifiers for the servers before enrollment.
- Existing assignments can reach servers. Windows policies assigned to All devices, to users or to dynamic groups can land on servers after enrollment. Creating a server group does not remove those assignments.
- How to identify a server. In an assignment filter, use the operatingSystemSKU property, which now includes Windows Server values: Standard (7), Datacenter (8), Standard evaluation (79), Datacenter evaluation (80) and Datacenter Azure Edition (407).
- Policy sets and PowerShell scripts do not support assignment filters. Use explicitly scoped groups and exclusions.
- Permissions. There are no new RBAC roles. Existing Intune roles and scope tags apply to servers too, including permissions for remote actions, BitLocker keys and local administrator passwords.
- A user who signs in to a server can trigger app installs through user assignments, unless an assignment filter excludes servers.
- Multifactor authentication. If a Conditional Access policy requires MFA and applies to servers, an enrolled server may stop syncing without prompting for sign-in. Select Sync and sign in again.
- BitLocker is not installed on a server by default. Install the feature and restart before you configure encryption or evaluate compliance.
Azure Arc, Azure and Configuration Manager
- Arc is the complement. Microsoft recommends Azure Arc for production servers and infrastructure management, and describes it as complementary to Intune. Azure and Arc are not required to manage servers in Intune.
- Division of roles. The endpoint team uses Intune for apps, settings, updates and compliance. The infrastructure team uses Arc for monitoring and governance. Intune fits servers that behave like endpoints with a user identity, and Arc fits the rest.
- The key rule: Intune and Arc, Group Policy or Configuration Manager must not enforce conflicting settings on the same server.
- Servers on released versions stay in Configuration Manager under its own support requirements.
- Azure VMs: Intune users with applicable permissions get control of enrolled VMs through Intune roles, without Azure RBAC group membership and without just-in-time requirements. Azure and Intune compliance policies can conflict, and Azure Update Manager can change update behavior.
What to do now
- Join Insider. Join the Windows Server Insider program and install a test server.
- Review assignments. Go over existing assignments to All devices, users and dynamic groups, and add exclusions for servers.
- Enroll one server. Enroll a single test server, and validate on the server that each setting really applies, not only that the report shows success.
- Send feedback. Send feedback to the Intune product team about management issues, and use Feedback Hub for build issues.
- Wait for production. Do not enroll production servers until Microsoft publishes a public preview and licensing terms.
Want to test Intune server management in a controlled environment, or prepare your assignments before the capability reaches production? Book a meeting with OnCloud.
Book a meetingSources
- Microsoft Tech Community: What’s new in Microsoft Intune at Ignite
- Microsoft Tech Community: Manage Windows Servers alongside PCs with Microsoft Intune
- Microsoft Learn: Get started with Windows Server management (Insider preview)
- Microsoft Learn: What’s new in Microsoft Intune
- Microsoft Learn: What’s new in Windows Server 2028 Preview
- Microsoft Learn: Enrollment restrictions, blocking server devices