Why Devicie
Solutions
- Accelerate SCCM-to-Intune migration
- Meet application patching deadlines
- Package and update specialized applications
- Consolidate application patching tools
- Keep approved configurations in place
- Implement endpoint security requirements
- Resolve device issues faster
Security frameworks
and requirements
By industry
All industries and roles →Customers
Devicie
Articles › Microsoft Intune › Windows Server in Intune: which servers belong there, and where Devicie fits
Windows Server in Intune: which servers belong there, and where Devicie fits
Microsoft put Windows Server management in Intune into preview at Ignite 2026. José Schenardie and Dave Raphael on which servers belong there and what to check first.
Opinions on tap. By José Schenardie and Dave Raphael.
On 17 November at Microsoft Ignite, Microsoft announced that Intune management for Windows Server is now in preview. We recorded this End Pints episode in San Francisco a few minutes later. Below is what the preview covers, which servers it is meant for, how Devicie works with it, and what we would check before enrolling a single server.
What Microsoft announced
The preview is for servers that behave like workstations: privileged access workstations, jump boxes, remote desktop session hosts, dev and test machines, factory-floor terminals, and servers in branches and at the edge. Eligible servers are Active Directory joined through Microsoft Entra Connect, or joined to Microsoft Entra ID. The preview runs on Windows Server Insider builds, and Microsoft recommends non-production servers in a separate test tenant. Server enrollment is off by default until an admin opts in.
The workflows in scope are groups and assignment filters, update rings and maintenance windows through Windows Autopatch, settings catalog configuration, Conditional Access, and Win32 app deployment. Microsoft has not yet published licensing or a general availability date.
Which servers belong in Intune
Microsoft's own guidance is that Azure Arc remains its recommended management plane for on-premises and hybrid servers, and that Intune and Azure should not enforce competing policies on the same settings. We read the announcement the same way. The datacenter estate your infrastructure team runs stays where it is.
What changes is the server that sits in an office or a store, runs a line-of-business app or serves as someone's workstation. It has always been looked after like a desktop without being one. Those servers can now sit in the same Intune tenant as the PCs around them, managed by the same endpoint team.
Where Devicie fits
Devicie works through Intune. The apps we package, the configuration we maintain and the assignments we manage all land in your tenant as Intune objects. A server enrolled in Intune is another Windows device in that tenant. For the workflows Microsoft supports in the preview, we manage it the same way we manage the PCs we already look after: the same packaged Win32 apps, the same settings catalog configuration, the same update rings.
That is also where the care is needed. An app assigned to all devices today reaches a server as soon as the server enrolls, whether or not anyone meant it to. So before a server goes into Intune, every broad assignment needs a decision: keep it off servers, or target servers on purpose. We start the way we start with any estate we take on: a read-only look at what is assigned today, a list of what would reach a server, and the filter and assignment changes agreed with you before anything moves.
What we would check before enrolling a server
1. Assignments that target all devices
Microsoft's guidance is to review every All devices assignment before enrolling. During the preview, existing configuration policies do not apply to servers until they are edited, so a server can pick up a workstation policy the next time someone changes it. A policy written for workstations, such as removing local administrators, is rarely what a server needs.
2. Filters
Microsoft supports the operatingSystemSKU property in assignment filters, which is how you keep PC policies off servers or aim server policies at them. Filters cannot be combined, so keeping servers out of existing assignments may mean adding clauses to the filters you already use, or creating new ones.
3. Roles, scope tags and LAPS
Existing Intune roles and scope tags apply to servers, so an admin who can deploy to Windows PCs may also see and target enrolled servers. If only some people should change servers, plan your scope tags before the first enrollment. Check who can read local administrator passwords too: Windows LAPS already works on servers, and an enrolled server's password may become visible in the Intune console to anyone with the right role.
4. Enrollment at scale
Automatic enrollment works for hybrid-joined servers. Bulk enrollment, MDM-only enrollment and automatic enrollment for co-managed devices are not available yet, and Windows Autopilot does not apply to servers. Plan how your servers will enroll before you plan which ones.
5. What is still unknown
Licensing, which Windows Server versions will be supported, and when the preview reaches general availability.
What to do now
Enroll a test server or two on an Insider build in a test tenant, open the device object in Intune, and list exactly which assignments land. That list is what to fix before production. If you would like a second pair of eyes on your tenant, talk to us.
About the authors
José Schenardie is a Microsoft MVP and a co-founder of Devicie. He has worked in endpoint management since SCCM 2007 and organizes Workplace Ninja community events.
Dave Raphael is Devicie's Chief Product Officer.
More End Pints
End Pints is Devicie's podcast: conversations with the people who manage Microsoft devices for a living, and the community around them. Watch every episode at devicie.com/endpints, or find our short films on Microsoft's monthly updates at devicie.com/watch.
We love hearing from the people who manage Microsoft devices for a living. Come have a pint with us and tell us what you think.
An Intune Health Assessment reviews your current configuration, shows where the gaps are and prioritizes what to address first. Your team runs a read-only collection script.
Request your free assessment