For years, SCCM shops have run two worlds: PCs in Intune and servers in Configuration Manager, Group Policy, and PowerShell scripts. That may finally change. Here’s how to manage Windows Server with Intune: what SCCM shops need to know about Microsoft’s new preview, what it supports, what it doesn’t, and how to plan before you enroll a single server.
The short version: the Intune Windows Server management preview is real and useful, but it’s for test environments only. It doesn’t replace Configuration Manager for production servers yet. The smart move now is to pilot, plan ownership, and fix your policy assignments before general availability.
What Microsoft Announced: Windows Server Management in Microsoft Intune
On November 17, 2026, Microsoft announced a preview that brings Windows Server into Microsoft Intune, in a post on the Intune Customer Success blog. It’s available through the Windows Server Insider program. Endpoint administrators can now apply configuration and compliance policies, deploy apps, manage updates, and use device compliance as a Conditional Access signal on eligible servers, all from the same Intune admin center they use for managed PCs.
This is a first. Until now, Windows Server couldn’t enroll in Intune as a managed device. The only Intune touchpoint was Defender for Endpoint security settings management, which delivers a limited set of security policies.
Who it’s for
Microsoft is aiming the Windows Server management preview at servers that behave like endpoints:
Windows Server used as workstations: privileged access workstations, jump boxes for reaching production environments, Remote Desktop Session Host servers, development and test systems, and factory-floor terminals.
Edge servers and branch-office servers: retail sites and remote locations where generalist IT teams manage local services alongside PCs.
Persistent virtual desktop sessions: Windows Server RDSH sessions in hybrid setups such as Azure Virtual Desktop Hybrid. Intune manages each session as a device, while the virtualization platform still manages host pools and images.
The goal is to standardize endpoint management. If the same team runs your PCs and these servers, Intune becomes one endpoint-management platform for both.
What the Intune Windows Server Management Preview Supports, and What It Doesn’t
The preview covers core scenarios only, and Microsoft doesn’t support it in production environments. Here’s the scope, based on Microsoft’s end-to-end preview guide.
| Area | Included in preview | Not included yet |
| OS | Windows Server Insider build (vNext 29621.1000 or later) with Desktop Experience, on persistent physical servers and virtual machines | Server Core; released versions such as Windows Server 2019; multisession hosts and nonpersistent hosts |
| Enrollment | Microsoft Entra join, or Microsoft Entra hybrid join with Group Policy automatic enrollment | Windows Autopilot, MDM-only enrollment, bulk enrollment, automatic enrollment for co-managed devices, userless enrollment |
| Configuration | Settings Catalog (server-applicable groups), endpoint security templates for antivirus, firewall, disk encryption, LAPS, and ASR, custom profiles | Endpoint Privilege Management and Resource Explorer |
| Compliance | Windows compliance policies used as a Conditional Access signal | Configuration Manager compliance checks, plus firewall, antivirus, and antispyware compliance checks |
| Updates | Update ring settings and maintenance window policies with Windows Autopatch | Separate quality, feature, and driver update policies |
| Apps | Win32 apps, with application deployment status reporting | Other app types |
| Remote actions | Sync, restart, BitLocker key rotation, local admin password rotation, retire, delete, wipe, collect diagnostics, Defender scan and update | Other actions may appear in the console but won’t work |
| Other | Optional Azure Arc connection | Configuration Manager co-management; disconnected or air-gapped server management |
On a phone, scroll the table sideways to see every column.
Two extras SCCM teams should note. BitLocker isn’t installed by default on Windows Server, so add the BitLocker Drive Encryption feature and restart before you test encryption policies. And if a Conditional Access policy requires MFA, servers can stop device sync with Intune until someone selects Sync and signs in, so watch the authentication status in Settings.
Intune vs. Configuration Manager vs. Azure Arc: Which Tool Owns Which Server?
Intune won’t be the right home for every server. Microsoft is clear that Azure Arc remains its recommended plane for production and business-critical servers, while Intune suits endpoint-like servers with a user identity.
| Tool | Best for | Key boundary |
| Microsoft Intune (preview) | Endpoint-like servers the PC team already manages: jump boxes, branch servers, RDSH sessions | Nonproduction only for now; user-based enrollment required |
| Configuration Manager | Released Windows Server versions in production today | Intune co-management for servers isn’t in the preview |
| Azure Arc | Infrastructure management, monitoring, and governance across on-premise servers, Azure, and other clouds | Avoid competing policies with Intune on the same settings |
| Defender for Endpoint security settings management | Security policies on servers not enrolled in Intune | Can’t yet transition these servers to Intune |
On a phone, scroll the table sideways to see every column.
Using Intune and Azure Arc together
The two can share a server if each team owns a different job. Your endpoint team uses Intune for apps, security configuration, patches, and device compliance. Your infrastructure team connects the same server to Azure Arc, then uses Azure Monitor for infrastructure-level monitoring and Azure Policy to audit configurations.
As Microsoft puts it, clear ownership of administrative responsibilities is essential to keep Windows Server behavior predictable. Two tools enforcing the same setting is how outages start.
Questions to decide ownership
Which team is responsible for the server?
Does the team running it also manage endpoints?
Is your organization already using Azure, or ready to?
Do you want to standardize endpoint management across PCs and servers?
Does the server need Azure-based governance and services?
Which of your servers are Intune candidates, and which belong in Configuration Manager or Azure Arc?
We’ll sort your server estate into endpoint-like and infrastructure workloads and assign an owner for each.
How to Try the Windows Server Management Preview
Prerequisites
An Intune and Microsoft Entra ID subscription, ideally in a separate test environment, not your production tenant.
A nonproduction Windows Server Insider build with Desktop Experience. Windows Server Standard and Datacenter editions both work.
A licensed pilot account: a test user with a valid Intune license, or a device enrollment manager account.
Microsoft Entra ID P1 or P2 for automatic enrollment.
Internet connectivity to the Microsoft services used for enrollment.
Microsoft says no extra subscription is needed for the preview, but final licensing details for general availability haven’t been announced.
Step 1: Review assignments before you allow enrollment
This is the step SCCM shops most often miss. Enrolled servers show up in All devices next to your PCs, and broad user assignments can follow the user onto a server. Audit configuration, compliance, app, script, and update assignments first. Microsoft notes that policy sets and PowerShell scripts don’t support assignment filters, so scope those with explicit groups.
Step 2: Create server assignment filters
In the Intune admin center, go to Tenant administration > Assignment filters and create a filter on the operatingSystemSKU property. New values include Windows Server Standard (7), Datacenter (8), and Datacenter: Azure Edition (407). Use these filters to target server policies and keep PC policies off servers.
One caution: Windows Enterprise multisession editions report the ServerRdsh SKU even though they’re client systems. Test any filter logic before you rely on it to exclude servers.
Step 3: Plan roles and scope tags
Existing Intune roles and scope tags apply to servers, so admins who manage PCs today may see and act on servers after enrollment. Plan scope tags first so server management stays with the right admins. Review who holds the Intune Administrator role and other Microsoft Entra directory roles, and consider multi-admin approval for high-risk actions such as wipe operations.
Step 4: Allow Windows Server enrollment
Server enrollment is blocked by default. In your device platform restriction, change Server devices from Block to Allow. Any custom Windows restriction you already have keeps blocking servers until you change it too.
Step 5: Enroll a pilot server
For a new server, use Microsoft Entra join: on the server, go to Settings > Accounts > Access work or school and join it to Microsoft Entra ID. For a server that depends on Active Directory, use Microsoft Entra hybrid join through Microsoft Entra Connect and Group Policy automatic enrollment.
Step 6: Apply policies, then verify on the server
Assign your compliance policies, configuration policies from the Settings Catalog, update rings, and a test Win32 app to the pilot group. Then check the device details page for device settings and app status, and confirm the setting actually works on the server. A green policy report alone doesn’t prove it.
Share what you find through Microsoft’s preview feedback form. Microsoft says it will build on the preview based on customer feedback.
What SCCM Shops Should Do Now: A 6-Point Checklist
Don’t move production servers yet. Use the preview window to get ready, so you can move fast when Microsoft announces general availability.
Inventory your server estate. Tag each server as endpoint-like (jump box, branch server, RDSH) or infrastructure (domain controllers, SQL, file servers). Only the first group is an Intune candidate.
Assign an owner per workload. Decide whether Intune, Configuration Manager, Group Policy, or Azure Arc is the authority for each setting, so you never run competing policies.
Clean up “All devices” assignments now. This is the biggest risk Microsoft’s own community commenters raised. Add server-exclusion filters before any server enrolls.
Lock down admin access. Map Intune roles and scope tags to your server team, and turn on multi-admin approval for destructive actions.
Stand up a test tenant. Enroll two or three non-production servers on the Insider build and run through updates, apps, remote actions, and diagnostics collection.
Track the roadmap. Watch for co-management support, Server Core support, and final licensing, since those decide when Intune can realistically replace Configuration Manager for servers.
Frequently Asked Questions
Can Intune replace SCCM for servers today?
No. The preview is nonproduction only, works only on Windows Server Insider builds, and doesn’t include Configuration Manager co-management. Keep production servers in Configuration Manager or Azure Arc for now.
Can I enroll Windows Server 2019 or 2022?
No. The preview needs an eligible Windows Server Insider build. Released versions aren’t supported.
Will my existing PC policies hit my servers?
They can. Enrolled servers appear in All devices, and user-assigned policies can follow users onto servers. During the preview, existing configuration policies don’t apply to servers until you edit them, but apps, scripts, and other assignments still need review.
Is Server Core supported?
No. The preview supports Windows Server with Desktop Experience only.
What remote actions work on servers?
Sync, restart, BitLocker key rotation, local admin password rotation, retire, delete, wipe, collect diagnostics, and Defender scan and update. Other available server-management actions may appear in the console but won’t work yet.
What if a server stops checking in?
Check device communication first. A Conditional Access MFA requirement is a common cause; open Access work or school on the server, select Sync, and sign in.
Does it cost extra?
Not during the preview. Existing Intune, Conditional Access, and Defender for Endpoint entitlements apply. Pricing for general availability, for organizations in the United States and elsewhere, hasn’t been published.
Plan Your Server Move Before General Availability
Bringing Windows Server into the endpoint-management workflows your team already uses is a big step toward one console. But it only pays off if you plan ownership, clean up assignments, and pick the right tool for each server first.
Windows Management Experts helps organizations plan and run Configuration Manager, Intune, and Azure Arc side by side. Talk to a WME consultant to get an SCCM-to-Intune readiness assessment for your server estate.
Plan ownership and clean up assignments before general availability.
We’ll help you run Configuration Manager, Intune and Azure Arc side by side, and pick the right tool for each server.


