Blog Post

Intune Customer Success
6 MIN READ

Manage Windows Servers alongside PCs with Microsoft Intune

Arnab Biswas's avatar
Arnab Biswas
Icon for Microsoft rankMicrosoft
Nov 17, 2026

Another way into the cloud: Test Intune management for eligible Windows Servers alongside your PCs.

Microsoft enables organizations to bring more of their workloads into the cloud, but the path looks different for every organization. Some Windows Servers, including servers used as workstations, remote desktop session hosts, and branch-office servers, still run mission-critical workloads and may continue to be managed with traditional tools such as Configuration Manager, Group Policy, and scripts.

Microsoft is extending familiar endpoint-management workflows to these eligible Windows Servers through Microsoft Intune. Available through the Windows Server Insider program, this preview allows endpoint administrators to manage supported servers in Intune alongside the Windows clients and other devices they already manage.

With this preview, endpoint administrators will be able to apply configuration and compliance policies, deploy apps, manage updates, and use device compliance as a signal for Conditional Access on eligible Windows Servers. Intune roles and scope tags help control who can view and manage these servers. These familiar workflows give endpoint teams a more consistent way to manage supported Windows Servers alongside their Windows clients. To explore the preview, enroll eligible non-production servers running a supported Windows Server Insider build in a test environment and share feedback with Microsoft.

Figure 1: A list of enrolled Windows and Windows Server devices in the Intune admin center.

Bring servers into familiar endpoint workflows

For endpoint teams already managing Windows 11 PCs, bringing Windows Server management into Intune is a natural extension. Intune becomes a single pane of glass for both servers and Windows endpoints as many of these servers are managed by the same teams that run Intune for their endpoints. If your Azure team manages both the cloud and on-premise servers, we recommend using Azure Arc.

Intune-eligible scenarios include Active Directory–joined servers in environments that use Microsoft Entra Connect, and servers that join Microsoft Entra ID. Here are some examples:

  • Windows Server used as workstations: privileged access workstations and jump boxes for reaching production environments, remote desktop session hosts, development and test systems, and factory-floor terminals.
  • Edge, branch, and distributed Windows Server: servers in retail sites, branch offices, and other remote locations where generalist IT teams manage local services alongside PCs.
  • Persistent virtual desktop sessions: Windows Server RDSH sessions in hybrid virtual desktop environments, such as Azure Virtual Desktop Hybrid. Intune manages each session as a device and applies user policies; the virtualization platform continues to manage host pools and images. Multiple concurrent sessions are outside the scope of this preview.

 

Figure 2: Device details of an enrolled Windows Server.

Keep control of who manages your servers

Servers such as privileged access workstations and jump boxes often hold the keys to production environments, so who can manage them matters as much as how they are managed. Intune gives you control at each step:

  • Windows Server enrollment is opt-in. Server enrollment is off by default.

To enroll servers, change the Windows Server devices setting from Block to Allow; existing custom Windows restrictions continue to block servers until changed. Entra groups and assignment filters give you granular control over who can enroll.

 

Figure 3: Server devices restricted from enrolling by default.

  • Identity and compliance gate access. Enrolled Windows Servers join Microsoft Entra ID. You can evaluate them against compliance policies and use Conditional Access to require a compliant device before users reach protected apps and resources.
  • Roles and scope tags determine who can act. Existing Intune roles and scope tags apply to servers. Admins who manage PCs today may be able to see and act on servers after they enroll. Plan role assignments and scope tags before enrollment so server management stays with the right admins.
  • Filters keep policies where they belong. Use assignment filters with the operatingSystemSKU property to target server policies precisely and keep PC policies off servers.

 

Figure 4: New assignment filters for Windows Server SKUs.

Choose the right management approach for your servers

To determine eligibility for servers, weigh team ownership alongside your organization’s existing management approach. Use these questions to guide the decision:

  • Ownership: Which team is responsible for the server?
  • Team scope: Does the team operating the server also manage endpoints?
  • Azure readiness: Is your organization already using Azure, or ready to adopt it?
  • Standardization: Is standardization of management tools across endpoints and servers a priority?
  • Infrastructure needs: Does the server need Azure-based governance and services?

Combine the strengths of Intune and Azure Arc

Intune and Azure provide complementary management capabilities. Intune brings endpoints and eligible Windows Servers into the same device-management workflows, while Azure provides infrastructure management across environments—whether resources are hosted in Azure, on-premises, or in other clouds.

For example, an endpoint team can use Intune to deploy applications, apply supported security configurations, deploy patches, and evaluate device compliance on a Windows Server. The infrastructure team can connect that same Windows Server to Azure through Azure Arc, making it available as an Azure resource. They can then use Azure Monitor to monitor server health and performance, and Azure Policy to audit supported configurations against infrastructure governance requirements.

Together, these capabilities let each team manage the same server through the lens relevant to its role. Clear ownership of administrative responsibilities is essential to keep Windows Server behavior predictable. Intune and Azure can manage different areas of the same server, but they should not enforce competing policies for the same settings or workload.

Intune and Azure are both cloud-native and serve different management needs. Intune brings eligible Windows Servers into the endpoint-management workflows that endpoint teams already use, while Azure provides infrastructure management, monitoring, and governance for production and business-critical servers, wherever they run. For customers already operating in Azure and looking to manage on-premise servers, Azure Arc remains Microsoft’s recommended management plane for on-premises and hybrid servers.

Review the Windows Server Insider preview scope

The preview supports selected Windows management workflows on eligible servers, as outlined below. Before planning a rollout, review the documentation for supported settings, app types, and device actions.

 

TaskWhat you can test
Opt inServer enrollment is off by default. In the Intune admin center, device platform restrictions include a Server devices setting initially set to Block. To opt in, change it to Allow in the default restriction or in a custom Windows restriction assigned to users who will enroll servers. Existing custom Windows restrictions continue to block servers until you change them.
EnrollOn the server, add a work or school account to join Microsoft Entra ID and enroll in Intune. Automatic enrollment is also supported for hybrid-joined servers.
Find and organizeEnrolled servers appear under the Windows platform and in All devices alongside PCs. Use groups and assignment filters - including the operatingSystemSKU property - to include or exclude servers. Supported remote actions are also available.
UpdateManage server updates with supported update ring settings and maintenance window policies using Windows Autopatch.
ConfigureApply supported server settings from the settings catalog. Where settings apply to both, manage them with a single policy, or author separate server and PC policies if you need to. Each setting’s server applicability determines where settings apply.
Protect accessExtend existing Conditional Access policies to servers where applicable, or create separate policies for servers. Require a compliant device for supported access to protected apps and resources.
Deploy appsDeploy supported Win32 apps and monitor their deployment status.

 

This preview covers core scenarios only. Windows Autopilot doesn't apply to servers, and MDM-only enrollment, bulk enrollment, and automatic enrollment for co-managed devices aren't available yet.

Prepare before enrollment

Complete these checks before enrolling your first servers:

  1. Review All devices assignments. Enrolled servers appear in All devices.
    During the preview, existing configuration policies do not apply to servers until you edit them. Review other All devices assignments before enrollment.
  2. Create server assignment filters. Use operatingSystemSKU to target server SKUs with a server policy or exclude them from a PC policy.
  3. Check roles and scope tags. Existing Intune roles and scope tags apply to servers, so admins who manage your PCs today may be able to see and act on servers after they enroll. Plan scope tags before enrollment to keep server management with the right admins.
  4. Start with a pilot in a test environment. Enroll a few non-production servers in a test tenant first. If Configuration Manager, Group Policy, or Azure Arc also manages them, decide which tool is the authority for each workload.

Start with a pilot and shape what comes next

This preview brings core server-management scenarios to Intune so organizations can test them on non-production servers. Microsoft will continue building on the preview based on customer feedback.

As with any Insider Preview build, test the capabilities in a separate environment rather than the tenant used to manage production devices.

Updated Nov 16, 2026
Version 1.0

10 Comments

  • AaronMHall's avatar
    AaronMHall
    Brass Contributor

    I obviously agree with the "All Devices" comments here, simply because I know a lot of people do this. But my question to all of them is... why on earth would you do that option in the first place? Groups and filters. All anything is rarely a good idea.

  • Agree here - feel the "All deviecs" can be a bit dangerous then, to mess up stuff we shouldn't 😅

  • Ben_Nicholls's avatar
    Ben_Nicholls
    Copper Contributor

    The "All devices" group needs separating out into something like "All endpoints" & "All servers". It's a recipe for disaster without this change.

  • ibdmnm5000's avatar
    ibdmnm5000
    Tin Contributor

    I'm celebrating this step – I've been waiting a long time for this to become possible. Thank you!

  • BryanDam's avatar
    BryanDam
    Iron Contributor

    What's the licensing going to look like here?

    EMS (Intune) is most commonly licensed via user licenses (M365) and less commonly via devices licenses.
    Autopatch also: it's strictly tied to having a Windows subscription; you can own EMS/Intune without owning Autopatch.

    • Dennis_Peabody's avatar
      Dennis_Peabody
      Tin Contributor

      It will be confusing. Mention of that should have been included in this article, but likely the author has no idea either.

  • Enrolled servers appear under the Windows platform and in All devices alongside PCs.
    Why though? Got a ton of "All Devices" deployments out there. I feel like if you silently renamed existing "All Devices" to something like "All Devices (except servers)" and then "All Servers" is a new pseudogroup that would be a much better and more predictable experience for everyone.

     

    Use groups and assignment filters - including the operatingSystemSKU property - to include or exclude servers.

    Sure, I'll just add filters to exclude server SKUs from my All Devices deployments then, no problem... but I still can't apply multiple filters to an assignment. So now I've gotta go edit allllll of my Windows filters and add SKU criteria to them?

    Feel like this could have been handled a lot better - why not separate Windows "Workstation" from Windows "Server" in the same way that iOS / Android are completely separate from each other? If that had happened, there wouldn't be any issue with "All Devices" deployments at all, because the config profiles / apps etc wouldn't cross over that boundary.

    • anotherSysAdmin22's avatar
      anotherSysAdmin22
      Occasional Reader

      This - Intune either needs to add multiple filter support or some other way to safely and easily exclude servers from All Devices scope. Massive blocker for existing intune deployments to go through and update all of our scripts, config polices, apps, etc.

    • port42's avatar
      port42
      Tin Contributor

      Keeping servers and clients separate would be really great. Otherwise, this is going to be a big mess.

  • Hi thnx for the blogppost- interesting
    Is it possible for you to tell how the intention is to manage servers joined to an AD different from the the Intune instance "domain/Entra ID"?
    Do we need an Intune instance per AD forest?