Intune can manage Windows Server in a public preview announced with Windows Server 2028, but only for nonproduction servers running an eligible Windows Server Insider build with the Desktop Experience. You allow server enrollment in a device platform restriction, enroll a pilot server with Microsoft Entra join or hybrid join, and target it with compliance, update ring, settings catalog and Win32 app policies. Microsoft does not support production use.
Who this is for and what you will have at the end
This guide is for Intune administrators who already manage Windows 11 devices and want to see whether some servers can be handled the same way: jump boxes, privileged access workstations, RDSH hosts, dev and test machines, and branch or retail servers. Microsoft's Tech Community post on the preview lists those scenarios.
By the end you will know whether a server is eligible, which settings to change before the first enrollment, how to enroll one pilot server, which policy types Microsoft says apply, and what is excluded. You will not have a production plan. Microsoft states that Windows Server management in Intune is for nonproduction testing and evaluation only.
If you only need to stand up a test machine first, follow Install the Windows Server 2028 Preview in a Hyper-V Lab. For the wider feature picture, see Windows Server 2028 Preview: What Is New for IT Admins.
What is documented and what is not
The preview was announced at Microsoft Ignite 2026. The facts below come from Microsoft's own pages: the Learn end-to-end guide updated on 2026-11-17, the Intune Customer Success post, and the Intune Ignite roundup. Anything those pages do not state is marked "not documented" instead of guessed.
| Topic | What Microsoft documents |
|---|---|
| Status | Insider preview, nonproduction only, no Microsoft support for production use |
| Eligible build | Windows Server vNext Insider build 29621.1000 or later |
| Editions and install | Windows Server with Desktop Experience, physical or VM; Server Core not supported |
| Host types | Persistent servers and persistent single-session hosts; multisession, ephemeral and nonpersistent hosts out of scope |
| Enrollment | Microsoft Entra join, or hybrid join with Group Policy automatic enrollment |
| Licensing | No additional Windows Server preview subscription; existing Intune, Entra Conditional Access and Defender for Endpoint entitlements apply; future licensing terms not announced |
| Support | None for production; feedback through a form and Feedback Hub |
Microsoft's guide says no general availability date applies here because it is a preview. This article does not guess one.
Decide whether Intune is the right tool
Microsoft's guide separates four approaches, and they can overlap badly if you are not careful:
| Your scenario | Approach | Boundary Microsoft states |
|---|---|---|
| Evaluate endpoint-style management of eligible servers next to Windows clients | Intune server management preview | Nonproduction only |
| Apply supported Defender settings to servers not enrolled in Intune | Defender for Endpoint security settings management | Moving these servers to Intune management is not supported in the preview |
| Keep managing released Windows Server versions | Configuration Manager | Intune server co-management is not included |
| Infrastructure, monitoring and governance across on-premises and multicloud | Azure Arc | Microsoft's recommended plane; avoid competing policies |
The guide's FAQ gives a simple rule: use Intune for endpoint-like servers that have an associated user identity and that you want to manage alongside Windows clients, and Azure Arc for other server-management scenarios. If you already run Arc, read the Arc section near the end before enrolling anything.
Prerequisites
From the Learn guide:
- An existing Microsoft Intune and Microsoft Entra ID subscription.
- A nonproduction Windows Server vNext installation, build 29621.1000 or later, from the Windows Server Insider Preview downloads page.
- Local administrator access to the pilot server.
- A test user or device enrollment manager (DEM) account, plus dedicated groups for pilot users and for pilot server devices.
- An Intune test environment. The guide's FAQ says a separate tenant is the best option if you also want a server that Intune does not touch.
- Connectivity to the Microsoft services that enrollment and your chosen workloads need. Disconnected and air-gapped servers are not included.
Userless enrollment is not supported, so every pilot server needs an enrolling user.
For hybrid join, the guide adds a synchronized domain user with a valid Intune license, and refers to the automatic-enrollment page for the Microsoft Entra ID P1 or P2 requirement.
Step 1: Audit existing assignments before you allow servers
This is the step most likely to cause damage. Microsoft's warning is explicit: broad assignments such as All devices, user assignments and dynamic groups can include newly enrolled servers, and creating a server pilot group does not exclude servers from existing Windows assignments. Windows policies assigned to a Microsoft Entra user generally apply to Windows Server devices enrolled by that user.
Do this review first:
- List broad device assignments (All devices), user assignments and dynamic groups that could include the pilot server or its enrolling user.
- Audit configuration, compliance, endpoint security, app, script, update and policy set assignments.
- Check filter support for each workload. Microsoft notes that policy sets and PowerShell scripts do not support assignment filters.
- Add exclusions to client assignments where needed. For workloads without filter support, use explicitly scoped groups and supported exclusions.
Create a server assignment filter
Microsoft's documented path:
- Sign in to the Microsoft Intune admin center (intune.microsoft.com).
- Go to Tenant administration > Assignment filters.
- Select Create > Managed devices.
- In Basics, enter a Filter name and select Windows 10 and later for Platform.
- Add a rule on the
operatingSystemSKUproperty.
The preview adds these server values to that property:
| SKU | Value |
|---|---|
| Windows Server Standard | 7 |
| Windows Server Datacenter | 8 |
| Windows Server Standard (evaluation installation) | 79 |
| Windows Server Datacenter (evaluation installation) | 80 |
| Windows Server Datacenter: Azure Edition | 407 |
A rule that matches servers can be used in include mode for server policies, or in exclude mode on existing client policies. The Learn guide does not say whether one assignment can carry multiple filters, so check that in your tenant before you design around it.
Check roles and scope tags
Server management adds no new RBAC roles. Review existing role assignments and scope tags, including who can run remote device actions and who can see BitLocker recovery keys or local administrator passwords, because those apply to servers too.
Step 2: Allow server enrollment
Server devices are blocked by default, and Microsoft says existing custom Windows restrictions continue to block servers until you change them. In the platform restriction profile you use (the default Windows device type restriction, or an existing or new Windows profile), set:
- Server devices to Allow
- Personally owned devices to Allow
Both are needed when the server enrolls through Add work or school account in Settings. Microsoft points to its best practice for Windows Server platform restrictions if you want to keep blocking personally owned devices elsewhere. The procedure itself is the standard "Create a device platform restriction" article.
Step 3: Configure automatic enrollment
- In the Intune admin center, go to Devices > Enrollment > Windows > Automatic Enrollment.
- Set MDM user scope to include the pilot users. For the pilot, Microsoft suggests Some and only the intended users.
- Set Disable MDM enrollment when adding work or school account on Windows to No.
Read the scope carefully. Microsoft warns that if you provision Insider builds as Azure VMs, enrolling them gives Entra users with applicable Intune permissions management privileges over those VMs. The MDM user scope applies to both Windows and Windows Server devices.
Step 4: Enroll the pilot server
Option A: Microsoft Entra join
Use this for a new setup. Sign in with the test account that is in the automatic enrollment scope.
- On the server, open Settings > Accounts > Access work or school > Connect.
- Select Join this device to Microsoft Entra ID.
- Sign in and complete MFA if prompted.
- Select Join. The enrolling user becomes the device's primary user.
Verify from an elevated prompt:
dsregcmd /status
Microsoft's guide says to expect AzureAdJoined : YES under Device State (documented output; the surrounding output varies by device). Then in the Microsoft Entra admin center open Entra ID > Devices > All devices, find the device ID, and confirm Join type is Microsoft Entra joined and Managed by is Intune. In Intune, servers appear in Devices > All devices, identifiable by the SKU family column.
Option B: hybrid join with Group Policy
Use this for a domain-dependent pilot server that is already Microsoft Entra hybrid joined. Enrollment uses the same Group Policy automatic-enrollment flow as Windows 11; scope the policy only to the pilot servers. The first user to sign in becomes the primary user, and DEM accounts are not supported for Group Policy automatic enrollment on Windows Server.
Verify with dsregcmd /status as the domain user: expect AzureAdJoined : YES and DomainJoined : YES, and Join type of Microsoft Entra hybrid joined in Entra. If enrollment stalls, Microsoft points to its Group Policy auto-enrollment troubleshooting page.
Not available for enrollment
Per Microsoft's Tech Community post: Windows Autopilot does not apply to servers, and MDM-only enrollment, bulk enrollment and automatic enrollment for co-managed devices are not available. The same post says existing configuration policies in All devices do not apply to servers until edited, but the Learn guide warns that broad assignments can reach newly enrolled servers. Because the two pages differ, assume broad assignments can reach servers and audit them as in Step 1.
Step 5: Apply first policies
Microsoft's guide stresses that a successful policy report does not prove a setting works on Windows Server; verify on the server. Do not copy a Windows 11 baseline unchanged.
Compliance
Create a compliance policy targeted at the server pilot group, with only settings supported in the preview. Install the BitLocker Drive Encryption optional feature and restart first if you want BitLocker compliance, because BitLocker is not installed by default.
Leave these as Not configured; Microsoft says they can report Error or Not applicable:
| Category | Excluded setting |
|---|---|
| Configuration Manager Compliance | Require device compliance from Configuration Manager |
| System security > Device security | Firewall |
| System security > Device security | Antivirus |
| System security > Device security | Antispyware |
The exclusion covers compliance evaluation only; firewall and antivirus configuration is supported through endpoint security templates. Compliance can also feed Conditional Access. Microsoft warns that if a Conditional Access policy requires MFA and applies to server devices, enrolled servers may stop syncing without prompting, and Device sync status shows "Sync wasn't fully successful because we weren't able to verify your credentials." Select Sync and sign in to fix it.
Updates
Use the standard Windows update ring workflow with an assignment to server-only Entra device groups. Update ring settings such as automatic updates, notifications, preview-build controls, quality-update deferrals, deadlines, maintenance windows and reboot behavior can be configured. The Quality updates, Feature updates and Driver updates policies are excluded from the preview. Microsoft's Ignite roundup says the preview incorporates Windows Autopatch for update management. For comparison with the client side, see Intune update rings and hotpatch.
Settings catalog
In the policy's settings picker, select Add settings > Add filter and filter OS edition for Windows Server. That filter only changes which settings are shown; it does not control which devices receive the policy. Actual applicability depends on CSP support in the build, so use each setting's Learn more link and test on the pilot server.
Microsoft lists many included groups, for example LocalPoliciesSecurityOptions, Kerberos, LocalUsersAndGroups, UserRights, RemoteDesktop, RemoteManagement, SecureBoot, DeviceGuard and DeviceLock. Included templates are Endpoint security (Antivirus, Disk encryption, Firewall, Account protection > Local admin password solution, Attack surface reduction), Device restrictions or Kiosk, and custom profiles. Administrative templates cover Microsoft Edge, Mozilla Firefox, Microsoft 365 Apps, Microsoft OneDrive, Adobe Acrobat and Google Chrome. For the LAPS template, see Windows LAPS with Entra ID and Intune.
Win32 apps
Prepare and assign a Win32 app with the normal workflow, targeted at server-specific device groups. Company Portal can be deployed to managed servers for available-app scenarios.
Step 6: Use remote actions carefully
The preview's documented server actions are: sync and restart; rotate BitLocker keys and rotate local administrator password; retire, delete and wipe; collect diagnostics; and Microsoft Defender scan and update. Unsupported actions may still appear in the admin center but do not work on Windows Server. Treat wipe, retire and delete as destructive, and restrict them with RBAC.
Troubleshooting
| Symptom | Likely cause and fix |
|---|---|
| Server cannot enroll | Server devices and Personally owned devices not both Allow, a custom Windows restriction still blocking servers, or user not in MDM user scope |
| Unexpected apps or settings land on the server | Broad client assignments reached it; add exclude-mode operatingSystemSKU filters or scoped groups |
| Compliance shows Error or Not applicable | Excluded checks (firewall, antivirus, antispyware, Configuration Manager) configured; set to Not configured |
| Sync stops after enrolling | MFA Conditional Access policy applies to the server; select Sync and sign in |
| Setting shows success but nothing changes | CSP not supported in that build; validate on the server |
| Hybrid enrollment does not start | Check the Group Policy auto-enrollment scope and Microsoft's troubleshooting page |
Azure Arc and Azure VMs
Arc is optional in this preview, and Intune and Arc should not enforce the same settings. For Insider preview VMs in Azure that use Entra sign-in and are enrolled in Intune, Microsoft lists risks: users with Intune roles can manage those VMs without Azure RBAC or just-in-time access, Intune wipe can bypass Azure privileges, Azure Update Manager behavior can change, Azure and Intune compliance policies can conflict (evaluate the Azure ones in audit mode), and user assignments can trigger installs unless filters exclude the servers.
Known limitations
- Server Core, multisession, ephemeral and nonpersistent hosts are not supported.
- Windows Hello for Business and enhanced VM Connect Windows Hello are excluded for local sign-in; Web Sign-In is excluded for local and remote sign-in.
- MMPC-based features such as Endpoint Privilege Management and Resource Explorer are not included.
- Moving servers from Defender security settings management to MDM enrollment is not supported yet.
- Configuration Manager co-management is not included.
Closing checklist
- Use a separate test tenant and a nonproduction Insider build at 29621.1000 or later with Desktop Experience.
- Audit All devices, user and dynamic-group assignments, and add
operatingSystemSKUfilters. - Set Server devices and Personally owned devices to Allow, and scope the MDM user scope to pilot users only.
- Enroll one server, then confirm with
dsregcmd /statusand Managed by Intune. - Apply compliance, update ring, settings catalog and Win32 policies to server-only groups and verify effects on the server.
- Send feedback through the Intune form or Feedback Hub, and keep production servers on released Windows Server with Arc or Configuration Manager.
What we checked
- Opened Microsoft's Learn guide "End-to-end guide to get started with Windows Server Insider preview" on 2026-11-22 (page dated 2026-11-16, updated 2026-11-17); build 29621.1000 or later, Server Core exclusion, Server devices and Personally owned devices settings, and the admin center paths were copied from it.
- Cross-checked the enrollment restriction default (Server devices starts at Block) between the Learn guide and Microsoft's Intune Customer Success post, "Manage Windows servers alongside PCs with Microsoft Intune"; both agree.
- Opened the Intune Ignite roundup on Tech Community on 2026-11-22; it confirms Insider preview status and Windows Autopatch for update management.
- Compared the list of unavailable items (Autopilot, bulk enrollment, MDM-only enrollment) in the Tech Community post with the Learn guide's exclusions; the two describe slightly different scopes, so only items each page states are listed.
- Noted that the older Learn page on Insider Preview builds is dated 2024 and does not describe this feature, so it was used only as the download path.
- Documented output:
AzureAdJoined : YESfor Entra join andAzureAdJoined : YESplusDomainJoined : YESfor hybrid join, from the Learn guide; the SKU values 7, 8, 79, 80 and 407 also come from it. - Not checked: no tenant, Insider build or server was available, so none of the steps were run; they follow Microsoft's documentation as of 2026-11-22, and screenshots were not taken.
Last tested: 2026-11-22
References
- End-to-end guide to get started with Windows Server Insider preview, Microsoft Learn
- Manage Windows servers alongside PCs with Microsoft Intune, Tech Community
- What's new in Microsoft Intune at Ignite, Tech Community
- Get started with Windows Server Insiders Preview, Microsoft Learn
- Azure Arc-enabled servers overview, Microsoft Learn
This guide was researched and drafted with AI assistance and checked against the vendor documentation listed in its References. Read the maintained version and related guides on EpiFive.
Top comments (0)