windows
130 TopicsManage Windows Servers alongside PCs with Microsoft Intune
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. Task What you can test Opt in Server 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. Enroll On 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 organize Enrolled 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. Update Manage server updates with supported update ring settings and maintenance window policies using Windows Autopatch. Configure Apply 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 access Extend 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 apps Deploy 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: 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. Create server assignment filters. Use operatingSystemSKU to target server SKUs with a server policy or exclude them from a PC policy. 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. 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. Get the preview build: Get started with Windows Server Insiders preview, on Microsoft Learn Plan your pilot: Windows Server management in Microsoft Intune, on aka.ms/IntuneServerGuide Help shape what’s next: Tell us what works, what’s missing, and which server-management scenarios matter most to you: Preview Feedback | Intune Server Management – Fill out form or visit the Windows Server Insiders community21KViews5likes10CommentsMoving from Windows Autopilot to Windows Autopilot device preparation
By: Maggie Dakeva, Senior Product Manager - Microsoft Intune Organizations have spent years refining Windows Autopilot deployments. Profiles, Enrollment Status Page settings, group tags, dynamic groups, application assignments, and support processes all work together to deliver a familiar provisioning experience. Windows Autopilot device preparation is a re-architecture of Windows Autopilot designed around the customer asks we hear most often: simpler configuration, faster and more reliable setup, clearer progress for users, and near real-time deployment reporting for administrators. A single device preparation policy brings deployment and the out-of-box experience (OOBE) settings together, enrollment time grouping (ETG) places devices into the right security group during enrollment, and granular application and PowerShell script status makes troubleshooting easier. Autopilot device preparation is now the recommended solution for user-driven scenarios. Future engineering investments will focus on Windows Autopilot device preparation, enabling organizations to benefit from ongoing improvements to provisioning, reliability, reporting, and support. Moving eligible deployments positions your organization to benefit from those ongoing improvements while reducing the complexity of provisioning and support. So how do you move without disrupting devices that are already working - or forcing every deployment scenario to transition at once? The answer is a phased approach. Windows Autopilot and Windows Autopilot device preparation can coexist in the same organization. You can move eligible user-driven Microsoft Entra join populations in controlled waves, validate the full experience, and keep scenarios that still require Windows Autopilot on their existing path. The result is a practical way to adopt a simpler provisioning model while protecting the investments and workflows your organization still depends on. Start with the outcome, not a one-for-one migration Windows Autopilot device preparation brings enrollment settings, OOBE, device naming, required applications, PowerShell scripts, and enrollment-time targeting into a more coherent policy flow. The device preparation page, which replaces the Enrollment status page, gives users clearer progress and gives administrators more detailed deployment status for troubleshooting. Windows Autopilot device preparation includes two complementary capabilities: Device preparation policy defines the deployment experience, including OOBE settings, applications, scripts, naming, and ETG. Device association optionally binds a physical device to your organization before enrollment. It can establish corporate ownership and tenant affinity, enable associated-device OOBE settings, and support direct per-device policy assignment. Based on organizational needs, customers can choose to use device preparation policy, device association, or both. Device preparation policy provides the deployment configuration and experience, while device association adds pre-enrollment device affinity and device-based capabilities. Organizations can adopt each capability where it adds value to their provisioning model. But moving to that model shouldn't mean recreating every Windows Autopilot object exactly as it exists today. Instead, begin with the outcome each device population needs. Identify the required OOBE behavior, applications, scripts, naming, assignments, and support experience. Then design the device preparation policy and ETG model that delivers that outcome. This approach reduces inherited complexity and helps ensure that the new deployment is designed for Windows Autopilot device preparation and not constrained by the architecture it replaces. Choose what moves - and what stays Windows Autopilot device preparation is the recommended path for eligible user-driven provisioning scenarios, including: Corporate-owned Windows 11 devices User-driven Microsoft Entra join Windows 365 Continue using Windows Autopilot for scenarios that aren't supported or recommended for transition, including: Pre-provisioning Self-deploying mode Hybrid Microsoft Entra join Autopilot into co-management This isn't an all-or-nothing decision. The right transition plan deliberately separates eligible populations from valid exceptions. Translate the provisioning model Several familiar Windows Autopilot concepts have a corresponding role in Windows Autopilot device preparation: Windows Autopilot Concept Windows Autopilot Device Preparation Model Deployment profile Device preparation policy Enrollment Status Page profile Device preparation policy Enrollment Status Page in OOBE Device preparation page in OOBE Windows Autopilot registration Optional device association Profile and dynamic group-based targeting based on group tags Granular device preparation policy assignment with enrollment time grouping (ETG) using Microsoft Entra static security groups Device name template defined in the Autopilot deployment profile Device name template defined in the device preparation policy Windows Autopilot deployments report Windows Autopilot device preparation deployments report The goal is to preserve the required customer and administrator experience - not every historical configuration object. How the transition flow works A controlled transition can follow eight steps: Define the eligible population: Start with corporate-owned Windows 11 devices using user-driven Microsoft Entra join. Exclude scenarios that should remain on Windows Autopilot. Design enrollment time grouping (ETG): Create assigned, static Microsoft Entra security groups for populations that genuinely differ by location, role, device type, or required configuration. Don't build the new design around a group tag or a device object that must exist before enrollment. Create device preparation policy equivalents: Inventory each deployment profile and Enrollment Status Page pairing. Map the required OOBE settings, naming, applications, PowerShell scripts, blocking requirements, and dependencies into the new device preparation policy. Evaluate whether device association is required for all scenarios. For user-targeted deployments that don't need pre-enrollment tenant affinity or per-device policy selection, the organization can use the device preparation policy without device association and simplify the setup and management of device onboarding. For devices that need automatic corporate ownership, OOBE customization settings, or stronger pre-enrollment trust, continue with step 5. Pre-associate eligible devices. For existing registered or enrolled devices, collect the pre-association information by collecting the diagnostics logs, then exporting the DeviceLink CSV file found in the logs. Upload the CSV in the Associated devices blade in Intune and assign a device preparation policy to the device. Assignment can be done during the CSV upload process or after. Confirm that the device reaches the Pre-associated state before its planned reset or refresh. Note: Device pre-association is only available for devices that meet the minimum OS and hardware requirements , including TPM 2.0. Pilot the complete OOBE experience. Start with new devices or reset a small, representative set of devices. Validate policy selection, ETG placement, applications, scripts, naming, progress reporting. Expand and pre-associate remaining devices. Pre-associate additional populations in controlled waves. You do not need to force resets to all existing enrolled devices but simply pre-associate to prepare them so they enroll via the Windows Autopilot device preparation flow whenever each device next undergoes a natural or required reset. Retire registered flows. Retire deployment profiles, Enrollment Status Page profiles, groups, registrations, and processes only after reporting confirms that no active or planned population still depends on them. Pre-association doesn’t reset the device or disrupt its current use. The device remains enrolled and productive until its next natural or required reset, when Windows Autopilot device preparation takes effect. Don't remove the Windows Autopilot registration early. Doing so can remove Autopilot properties and affect dynamic-group membership that supports the device's current configuration. The next time the device enters OOBE, Windows recognizes the association and follows the Windows Autopilot device preparation path. If a device is both registered and associated, association takes precedence. Plan the pilot around this behavior rather than expecting an automatic fallback to Windows Autopilot. OEM and partner note: Device association uploads are currently only supported through Intune. OEM and partner pre-association scenarios aren't supported yet, but they’re on the roadmap. What this means for your organization You can prepare existing devices for transition while they remain enrolled and in use. You can move one eligible population at a time instead of committing to an organization-wide cutover. You can preserve Windows Autopilot for scenarios that still require it. You can use the transition to simplify assignment and provisioning logic rather than carry every legacy object forward. You can retire the old configuration gradually - after validation and dependency checks confirm that nothing still relies on it. A sample customer pilot setup scenario Consider a multinational organization, Contoso, that uses group tags to distinguish devices in the United Kingdom and Germany and to identify different device use cases. Dynamic groups use those tags to determine which deployment profile, Enrollment Status Page configuration, applications, policies, scope tags, and naming rules apply. The organization wants to move its eligible user-driven Windows 11 populations to Windows Autopilot device preparation without reproducing the same pre-created record and dynamic-group dependencies. The Contoso deployment team transitions to Autopilot device preparation with the following steps: Create static security groups for each required configuration. The team creates assigned Microsoft Entra security groups such as User Devices UK and User Devices Germany. It creates separate groups only when location, role, device type, scope, or required configuration differs. Create a device preparation policy for each population. The team creates a policy such as User Devices UK DPP and User Devices Germany DPP. Each policy contains the required OOBE settings, applications, PowerShell scripts, blocking behavior, and device name template, and identifies the corresponding enrollment time grouping (ETG) security group. Assign the device preparation policies to each population. The team assigns each device preparation policy to the respective sets of devices at time of pre-association or later. During enrollment, the device joins the group selected by the device preparation policy. For example, devices assigned the User Devices UK DPP join the User Devices UK group and receive the apps and policies assigned to that group. Configure scope through the static groups. The team assigns the appropriate regional scope tag to each ETG security group. The device receives the associated scope tag when it joins the group during enrollment. Set a naming template for each device preparation policy. The organization uses a naming convention where devices start with a prefix indicating their location. The team sets UK-%SERIAL% in User Devices UK DPP and DE-%SERIAL% in User Devices Germany DPP. Pre-associate pilot devices without disruption. Selected devices can be pre-associated while they remain enrolled and in use. The team collects diagnostics logs via script, extracts the DeviceLink CSV files, imports them in Intune, confirms the devices reach the Pre-associated state, and keeps the Windows Autopilot registration in place until the approved reset or refresh window. Validate the end-to-end experience with representative devices. The admin team uses test devices representing each target population to verify policy assignment, static group membership, scope tags, naming, applications, scripts, reporting, and successful completion of the device preparation flow. Existing devices can remain in service until their next natural or required reset. Seven-step regional Windows Autopilot device preparation rollout workflow, from creating security groups and device preparation policies through regional configuration, pilot association, and device validation. This scenario is illustrative, not a completed deployment or a measured customer outcome. It shows the transition pattern: define the supported scope, replace group-tag dependencies with ETG, move Enrollment Status Page and deployment profile settings to the device preparation policy, decide where device association adds value, validate end to end, and expand in controlled waves. Get started Begin with one eligible user-driven Microsoft Entra join population. Map its current Windows Autopilot outcomes to enrollment time grouping (ETG) and a device preparation policy. Pre-associate a representative pilot, validate the complete reset-to-desktop experience, and expand only when the results meet your deployment and support criteria. Moving to Windows Autopilot device preparation doesn't require a forced cutover. It requires a clear boundary, a deliberately redesigned assignment model, and evidence from each wave. That gives IT a controlled path toward simpler provisioning while keeping every device population on the experience that supports it best. Learn more Windows Autopilot device preparation overview Compare Windows Autopilot device preparation and Windows Autopilot Windows Autopilot device preparation user-driven Microsoft Entra join workflow Windows Autopilot device preparation requirements We’d love to hear your feedback! Share your thoughts in the comments below, follow us on LinkedIn or reach out to us on X @IntuneSuppTeam or @MSIntune.17KViews1like22CommentsWindows 11, version 26H2 security baseline
Update: The Windows 11, version 26H2 security baseline has been updated to reflect the general availability of Administrator protection. An updated v2 package is now available, and organizations should review and test the existing Administrator protection configuration as appropriate for their environment. You can download the baseline package from the Microsoft Security Compliance Toolkit, test the recommended configurations in your environment, and customize / implement them as appropriate. Summary of Changes This release includes several changes since the Security baseline for Windows 11, version 25H2 to further strengthen enterprise security and align the baseline with current platform capabilities and industry standards. Security Policy Change Summary Printer\Configure Windows Ready Print driver ranking Configured as “Enabled” to reduce reliance on third-party print drivers in the stack, narrowing the overall print driver attack surface. Internet Explorer\Internet Control Panel\Advanced Page\Turn off encryption support Updated from TLS 1.1 and TLS 1.2 to TLS 1.2 and TLS 1.3 to align with current security standards. User Account Control: Configure type of Admin Approval Mode (updated) Configured as “Admin Approval Mode with Administrator protection” to enable Administrator protection. User Account Control: Behavior of the elevation prompt for administrators running with Administrator protection (updated) Configured as “Prompt for credentials on the secure desktop” to require credential verification for administrative elevation. Windows Ready Print driver ranking Configure Windows Ready Print driver ranking" is the newly added setting under Administrative Templates\Printers to control whether Windows prefers the modern inbox IPP class driver over third-party OEM drivers when installing new printers. We recommend enabling this policy to reduce reliance on third-party print drivers in the stack, narrowing the overall print driver attack surface. Note that driver ranking applies when printers are installed via a connection method that supports IPP, such as USB or network multicast discovery. In those cases, if the printer supports IPP, Windows will install using the class driver even if a vendor V3/V4 driver is available. If the printer doesn't support IPP, or is installed directly as a TCP/IP printer, there's no change in behavior. Encryption Support We have updated the policy "Turn off encryption support" to allow only TLS 1.2 and TLS 1.3. Previous baseline releases permitted TLS 1.1 and TLS 1.2; however, TLS 1.1 is now considered obsolete and is no longer recommended for enterprise environments. This change aligns the security baseline with modern cryptographic standards while maintaining compatibility with widely deployed services that support current TLS versions. Administrator Protection (update) Administrator protection is now generally available. Organizations can enable it through Microsoft Intune or Group Policy. Important: Organizations should review and test their existing configuration and adjust these settings as appropriate for their environment. The security baselines for Windows 11, versions 24H2, 25H2, and 26H2 include settings that enable Administrator protection. The following policies are part of the security baseline: User Account Control: Configure type of Admin Approval Mode User Account Control: Behavior of the elevation prompt for administrators running with Administrator protection An updated v2 package has been published for Windows 11, version 26H2, to reflect this change. Please let us know your thoughts by commenting on this post or through the Security Baseline Community.Support tip: Why Windows driver recommendations may vary between deployment rings
By: Dorin Mardari – Sr Technical Support Engineer | Microsoft Intune Managing Windows driver updates across deployment rings might give results that seem inconsistent. You might expect the same update to behave the same way everywhere, but Windows Update evaluates updates separately for the devices in each ring. As a result, the update might appear under Recommended drivers in one ring and Other drivers in another, change classification over time, arrive at different times, or not appear at all even though the manufacturer's website lists it for your devices. In most cases, this behavior is expected. This article explains why it happens, what it means when you approve and deploy drivers, and how to tell expected behavior from a problem that needs Microsoft Support. For general information about driver update policies, approval modes, and the Recommended drivers and Other drivers lists, see: Configure Windows driver update policies Manage driver and firmware updates (Windows Autopatch) Where driver classifications come from Intune and Windows Autopatch don't decide whether a driver is recommended. First, the publisher submits the driver. Many drivers are built by a component maker, such as a chipset, audio, or graphics vendor, but published to Windows Update by the original equipment manufacturer (OEM). The publisher decides which hardware the driver targets and whether it's marked as required. Only drivers marked as required can appear under Recommended drivers. Windows Update then evaluates each device. Windows Update decides whether a driver applies, and how it ranks against other drivers that also apply. It bases this on the device's hardware IDs, currently installed drivers, the Windows version, and the publisher's targeting rules. Finally, Intune shows the result for each policy. Each policy's driver list is built from the results for the devices assigned to it. Why the same driver can be listed differently in different rings A driver isn't classified once for your whole tenant. Instead, it's classified for each policy (ring), based on the devices in that policy. Two devices can get different results for the same driver depending on their model, already installed drivers, and Windows version, even within the same ring. When the devices are in different rings, each ring can show the driver differently. This is especially common for drivers that apply to several device models. One device can change how the whole ring shows a driver If a driver is recommended for at least one device in a policy, the policy shows it under Recommended drivers, even if it's only optional for the other devices. Example: Ring A contains Device 1 and Device 2. The driver is recommended for Device 1 and optional for Device 2, so Ring A shows the driver under Recommended drivers. Ring B contains only devices like Device 2, so Ring B shows the same driver under Other drivers. Both rings can be managed the same way and contain similar hardware, but they show different results because of one device. Changes can apply to only some devices Each driver published to Windows Update has a unique UpdateID. You can find it in the driver's Update Details in the Microsoft Update Catalog. The same driver name and version can be published several times, for example for different devices or components, or with different requirements. Each of these publications is a separate update with its own UpdateID. Windows Update can also deliver one update to several groups of devices, called flights. Flights are based on details such as the manufacturer, hardware, installed drivers, and Windows version. During a driver's rollout, Windows Update can change how the driver is ranked, for example from optional to recommended. Changes can be triggered by events such as a new driver dependency or an operating system update, and they can apply to the whole update or to one flight only: If the change applies to the whole update, the driver moves to Recommended drivers in every ring that has devices it applies to. If the change applies to one flight only, the driver changes only in the rings that contain devices from that flight. This is why a driver can move from Other drivers to Recommended drivers in one ring, stay unchanged in another, or even move back again later. To check which flight a device is in, run Get-WindowsUpdateLog on the device and search the generated WindowsUpdate.log for the driver's name or UpdateID. The entry shows the UpdateId and the FlightId, for example: Title=Mediatek Inc. Bluetooth Driver Update (1.1146.0.608), ProductName=(null), UpdateId=09FA9654-A73F-4DF4-8691-81543A9E577E.1, FlightId=RD:000000, DeploymentID=000000000, DeploymentAction=Install, ClientMetadata: audience=(null), admin=(null), update=(null) Two devices with the same UpdateId but different FlightIds are in different flights and can show the same driver differently. A device's FlightId can also change after the driver's ranking changes. You can't choose or change a device's flight. Use this information to compare devices across rings, or include it when you contact Microsoft Support. For more information about how drivers roll out, see Gradual rollout – Windows drivers. The device's current driver matters Whether a driver is recommended for a device can depend on what's already installed. For example, a device running a generic driver might get the manufacturer's driver as recommended, while a device that already has a manufacturer driver might get the same update as optional. The same driver can appear as more than one update Different versions of a driver often have identical names. The same driver version can also be published more than once, for example with a different driver date or targeting different hardware. Each publication is a separate update, with its own classification and “Applicable devices” count. Use the “Version” and “Release” date columns to make sure you're comparing the same update. Driver names might not match what you're used to Driver names in Intune are generated from information in the driver package. Since February 2026, they use the format Provider Class Driver Update (Version), for example Lenovo Ltd. Firmware Driver Update (1.0.0.31). Drivers published before then may show an older naming format. Names also might not match the ones used on the manufacturer's website or in other tools – (for example, a BIOS update shows as Firmware). To match a driver, compare the version and, if needed, search the Microsoft Update Catalog for the driver's UpdateID. The UpdateID identifies one specific update, even when several updates share the same name and version. The Catalog's Driver Model field can also help, but its accuracy depends on how clearly the publisher describes the device in the "Models" section of the driver's INF file. Why the Applicable devices count might be lower than you expect The Applicable devices count shows how many devices in the policy can install that specific update. It can be lower than the number of devices of the same model for a few reasons: The update applies only to devices that match its targeting and don't already have a newer or better-matching driver. The same driver might be split across several updates, each with its own count. Inventory depends on each device’s Windows Update scan. Healthy devices can take up to 24 hours to complete their daily scan, after which Intune processes the results. This is not a guaranteed 24-hour limit for the complete inventory refresh. A previous version's count isn't a reliable indicator of how many devices a new version applies to. Why drivers are missing or arrive later Windows Driver Update Policies FAQs. A driver can also be missing, or arrive later in some rings, for the following reasons: Scan and processing timing: the driver only appears once an applicable device in that ring has scanned and the backend has processed it. It doesn't target your devices. Windows Update checks the device's hardware IDs. For firmware and some other drivers, it also checks computer hardware IDs (CHIDs), which identify the specific system model. If the publisher didn't include your model's identifiers, the driver isn't offered to it, even if the manufacturer's website lists it for that model.Only the publisher can fix this by republishing the driver. Recommended does not guarantee that the selected update is the OEM’s preferred CHID-targeted release. Windows driver update policies have a documented CHID-targeting limitation. See Understand driver update approval behavior. For more information about CHIDs, see Using Computer Hardware IDs (CHIDs). A better-matching driver is available for the device, so this one isn't offered. It isn't on Windows Update. Not every driver on a manufacturer's website is submitted to Windows Update. Some manufacturers also stop publishing newer versions of certain drivers to Windows Update. The device is new to the policy. After a device is assigned, it can take up to 24 hours to register for driver management. Approved drivers are then offered at the device's next update scan. The Windows driver update policies FAQ has additional information why older drivers disappear from a policy. What's expected As described and detailed above, this means the following behaviors may be expected: The same driver is listed under Recommended drivers in one ring and under Other drivers in another. A driver moves between the Recommended drivers and Other drivers lists over time, in some rings but not others. A driver appears in one ring before another. The number of drivers in a policy goes up and down as drivers are replaced or age out. This is more noticeable in small test groups than in large production rings. A driver available on the manufacturer's website doesn't appear in your policies. What this means when you approve and deploy drivers In policies with automatic approval, only drivers in the Recommended drivers list are approved automatically. As a result: The same driver can deploy automatically in one ring and wait for review in another. A driver can start deploying automatically in a ring if it moves into the Recommended drivers list. This can break the release order you planned across your rings. To keep control: To deploy a driver to every ring on your planned deployment schedule: Approve it manually where it's listed under Other drivers, and set the Make available in Windows Update date to match your plan. To make sure your rings follow a strict order: Consider manual approval for later rings, so drivers deploy only when you approve them. Approve each driver after it's validated in earlier rings. In Windows Autopatch, you can choose Automatic or Manual mode per deployment ring. Switching an existing ring between modes creates new policies and removes existing approvals, paused drivers, and declined drivers for it. Plan the change before you make it. For more information, see Manage driver and firmware updates. To hold a driver back everywhere: Pause it in every policy where it's approved. Don't rely on its classification, because it can change. Remember that only the latest approved version installs. If a ring has a newer approved version of the same driver, that version installs instead. More details on the pause behavior: How quickly are paused updates actually paused? To compare rings: Use the Windows Driver updates report, which shows one driver update across all your policies. For more information, see Reports for Windows driver update policies. Keep each device in one policy. For more information, see the Windows driver update policies FAQ. If a driver from the manufacturer's website isn't in Intune Ask the manufacturer. Check whether the driver was published to Windows Update for your model, and whether your model's identifiers were included. Only the publisher can check its submission and republish a driver. For more information, see Get support for the Hardware Program & Hardware Dev Center. Check what Windows Update offers the device directly. Run the following commands in an elevated PowerShell window on an affected device. They ask Windows Update for applicable drivers, independently of Intune. powershell $session = New-Object -ComObject Microsoft.Update.Session $searcher = $session.CreateUpdateSearcher() $searcher.ServiceID = "9482F4B4-E343-43B6-B170-9A65BC822C77" $searcher.SearchScope = 3 $searcher.ServerSelection = 3 $results = $searcher.Search("Type='Driver' and IsInstalled=0") $results.Updates | Select-Object Title, DriverModel, DriverVerDate, DriverHardwareID If the driver isn't listed, it's either already installed or Windows Update doesn't consider it applicable to that device, regardless of the management tool. Check the installed driver version (for example, in Device Manager or the device's Windows Update history) before contacting the manufacturer. If you need the driver urgently, deploy it outside of driver update policies, for example as a Win32 app or with the manufacturer's tools. If a version is causing problems, pause it in your policies. Microsoft Support can't check or speed up a driver submitted by a manufacturer. For publishing status or missing model identifiers, contact the manufacturer directly. When should you investigate further? The following symptoms can indicate a service issue rather than expected behavior, so contact Microsoft Support: Many drivers disappear from all your policies at the same time, and they aren't older than the versions installed on your devices. New drivers don't appear in any of your policies for an extended period, although Windows Update offers them to the same models. Applicable devices counts stay unexpectedly low for several days for drivers that the device check shows as applicable. An approved driver doesn't show a deployment date, or isn't installed on applicable devices that are scanning for updates. Summary When the same driver shows under Recommended drivers in one ring and under Other drivers in another, it's usually because Windows Update evaluates each device separately and can change a driver's ranking for some devices only. Missing drivers are usually caused by rollout timing or by how the manufacturer published the driver. You can't control how a driver is classified, but you can control what's deployed: Approve drivers from the Other drivers list where needed. Use manual approval where release order matters. Pause drivers you don't want. We’d love to hear your feedback! Share your thoughts in the comments below, follow us on LinkedIn or reach out to us on X @IntuneSuppTeam or @MSIntune.1.3KViews0likes0CommentsWindows CLAT is Now Generally Available
As organizations move toward IPv6-only and IPv6-mostly networks, some applications still depend on IPv4-only applications or services. Windows CLAT helps those applications continue to work when a network does not provide native IPv4 connectivity. CLAT is the client-side component of 464XLAT. It statelessly translates IPv4 traffic from the Windows client into IPv6 for transport across the network to a provider-side translator (PLAT), which provides stateful NAT64 translation to IPv4. Why CLAT? Compatibility with IPv4 resources: IPv6-only devices can reach IPv4 resources without requiring the whole network to be dual-stack. Reduced IPv4 address requirements: Devices can share a public IPv4 address through NAT64, reducing demand for scarce IPv4 addresses. This is critical for organizations that cannot obtain a significant block of IPv4 addresses for new networks due to IPv4 address depletion. Simpler network configuration: Organizations can deploy IPv6-only networks while retaining access to IPv4 resources. Seamless user experience: Translation happens as needed, without requiring users to know whether a service uses IPv4 or IPv6. Potential cost savings: IPv6-only deployment can reduce costs associated with IPv4 addresses and operating dual-stack infrastructure. Minimized security risk exposure: Similar to the above, dual‑stack networks expose two attack surfaces, each with its own vulnerabilities and configuration requirements. CLAT helps to reduce this by removing the need to secure an additional network. Incremental deployment: Organizations can introduce IPv6 in stages while maintaining IPv4 compatibility, rather than overhaul the entire network at once. A foundation for future IPv6 growth: CLAT helps organizations build on IPv6 rather than depend on an increasingly limited supply of IPv4 addresses. How Windows CLAT Helps Organizations Accelerate To IPv6-Only Feature What it is Why it’s important IPv4 application access on IPv6 networks CLAT is the client-side component of the 464XLAT architecture (RFC 6877). It translates IPv4 traffic so IPv4-only applications can communicate over an IPv6 network (where a NAT64/PLAT service exists.) Organizations can move network infrastructure toward IPv6 without waiting for every application or destination to support IP Local IPv4 compatibility for applications Allows IPv4 addresses to be assigned to support IPv4-only application flow on IPv6-only devices and networks. Helps existing applications continue to use familiar IPv4 networking while the device uses an IPv6 network underneath. Support across network interfaces The feature is designed for IPv6-capable connections across Wi-Fi, Ethernet, and cellular interfaces. Devices can maintain IPv4 application compatibility as they connect through different network types. Automatic recognition of IPv6-only networks CLAT can begin configuration discovery when IPv4 connectivity is unavailable, or when a network signals IPv6-only-preferred operation using DHCP Option 108 (RFC 8925). Reduces the need for users to configure connectivity themselves and gives networks a standards-based way to indicate that clients should prefer IPv6. Prefix discovery from network advertisements CLAT can discover the translation prefix from PREF64 information in IPv6 Router Advertisements, as defined by RFC 8781. Allows compatible routers to provide the information devices need to use for translation, and to advertise prefix changes as the network evolves. DNS-based prefix discovery CLAT can also discover the translation prefix by querying ipv4only.arpa, following RFC 7050 and RFC 8880. This provides an alternative when the network does not provide PREF64 through Router Advertisements. Gives organizations another standards-based discovery option for networks that rely on DNS to provide IPv4/IPv6 transition information. Where to Get More Details For a practical overview of enabling Windows CLAT, confirming its configuration, and collecting logs, see our Windows CLAT Public Preview blog. For a deeper explanation of what CLAT is and how it works, see Windows CLAT Enters Private Preview: A Milestone for IPv6 Adoption. Accelerating the Global IPv6 Migration We’re excited about the role Windows CLAT can play in the global transition to IPv6. By helping IPv4-dependent applications continue to work as networks evolve, this feature can make it easier for organizations to move toward IPv6-only and IPv6-mostly environments. We’re grateful to the customers and partners whose feedback helped bring Windows CLAT to general availability, and we look forward to seeing its impact across the IPv6 community.3.7KViews0likes9CommentsEdge sync failing on desktop
Hi! Edge sync on my PC (Edge 156.0.4314.56, Windows, personal Microsoft account) gets stuck in "Initializing" every time I restart the browser. Signing out and back in fixes it, but only until I restart again. In edge://sync-internals, the encryption key downloads fine after signing in, but after a restart "Has Keystore Key" goes back to false and Edge never requests the key again, so sync never starts, and it's actually very annoying. I noticed it on October 29 and have already sent feedback through Alt+Shift+I. Is anyone else seeing this, or is there a fix that doesn't require signing out every time?231Views0likes3CommentsBug in RDS Web Client - Copied text in RD session improperly encoded
As the title describes, there appears to be a bug in the HTML5 web client for Remote Desktop Services. This bug is present in both 2.1.85.0 and 2.1.87.0, and possibly earlier. When text is copied to the clipboard within a remote session (tested via a published RemoteApp), the text will occasionally be stored into the clipboard of the local machine encoded in UTF-8 instead of UTF-16 as it is supposed to be. When pasted into an application on the client machine, the UTF-8 encoded text (stored as CF_UNICODETEXT) is interpreted as UTF-16 (as that's how it's supposed to be encoded in memory as that's what Windows uses internally), resulting in meaningless output/mojibake. As an example, the text "Given" is copied from a Remote Desktop session (via the web client). The endpoint has these formats on the clipboard: Copied text CF_UNICODETEXT hex (padded) CF_TEXT hex Decoded text - UTF-8 Decoded text - UTF-16LE Given 47 69 76 65 6E 00 00 00 3F 3F 6E 00 Given 楇敶n The behavior is seemingly random. Most of the time, text is copied without issue. Once out of every 5-10 times, however, the UTF-8 encoded text is incorrectly written to the clipboard. Some additional information about this behavior: It only happens when using the RDS web client. The native RDP client does not exhibit this behavior. This has only been observed on Windows clients. It hasn't been observed on other client platforms, but testing has been minimal. The client browser does not appear to factor into the bug. It has been observed in Edge, Chrome, and Firefox. The issue is unrelated to the text copied. The same text, from the same application, can produce both outcomes when copied. The application being pasted into seems to be irrelevant. Has anyone else seen this behavior?107Views0likes2CommentsIntroducing device association for Windows Autopilot device preparation
By: Maggie Dakeva, Senior Product Manager - Microsoft Intune We’ve heard organizations want Windows deployment to be simple for employees and predictable for IT admins. But before a device enrolls, how does the organization know that the device is really one of its own - and how can IT make sure the right experience and policy reach that device regardless of who signs in? Today, we're announcing device association for Windows Autopilot device preparation, a new way to bind a physical Windows 11 device to your organization before enrollment begins. Device association uses hardware-backed attestation to create a trusted relationship between the device and your tenant at the start of the provisioning journey. That relationship helps Windows Autopilot device preparation recognize the device during the out-of-box experience (OOBE), automatically treat it as corporate-owned, and apply the experience and policy intended for that specific device. The result is a more secure, more consistent, and more device-centric onboarding flow. Start with the device, not just the user Windows Autopilot device preparation already gives IT teams a straightforward way to configure new Windows devices with the apps, scripts, and policies employees need. Device association extends that experience by allowing IT to target a device preparation policy directly to a device before it enrolls. This is especially valuable when the deployment experience needs to follow the hardware rather than the person signing in. For example, one employee can enroll multiple devices that serve different purposes, and each device can receive its own device preparation policy. When both device-based and user-based assignments are available, the device-based assignment takes precedence. That gives administrators greater confidence that the correct configuration reaches the correct device from the beginning of its lifecycle. Create a simpler out-of-box experience Because an associated device is recognized before enrollment, IT can configure more of the Windows setup experience in advance. Device association enables organizations to: Configure Language and region. Automatically configure the keyboard and skip the keyboard selection page. When the device uses a Wi-Fi network connection during OOBE, the language and keyboard selection screens aren't hidden. Hide the Microsoft Software License Terms page. Hide privacy settings during OOBE. Apply a device name template that uses the serial number or a randomized value. Hide account-change options on company sign-in and domain error pages. These controls reduce the number of decisions an employee must make while setting up a device and help create a consistent, organization-ready experience from the first screen. Strengthen trust before enrollment Device association isn't only an experience improvement. It establishes device trust earlier in the deployment process. The association uses hardware-based attestation and TPM-backed cryptographic validation to verify the device's identity. Tenant affinity is stored in the device's UEFI firmware, where it persists across a Windows reset, operating system reinstallation, or removal of enrollment. This durable, hardware-backed relationship helps ensure that the device presenting itself for preparation is the device the organization intended to onboard. Associated devices are also automatically marked as corporate-owned. If your organization blocks personally owned Windows devices with Intune enrollment restrictions, device association can be used instead of uploading a separate corporate identifier. You can continue to use corporate identifiers where they fit your process, but an associated device doesn't need both. How the device association flow works Device association is designed as a clear workflow that starts with IT and finishes automatically during OOBE: Create the device preparation policy. Configure the apps, scripts, deployment settings, OOBE experience, and optional device name template that should apply. Export the device information. During OOBE, a technician opens the Autopilot menu and exports the DeviceLink CSV with the device information required for pre-association to a USB. For an existing device, the same information can be collected from Autopilot diagnostic logs. Figure 1. The Windows Autopilot menu with Assign device association selected. ormation was exported to a removable drive. Pre-associate the device in Intune. In the Microsoft Intune admin center, go to Devices > Enrollment > Device association > Devices, upload the CSV, and optionally assign a device preparation policy directly to the device. Complete association. When the device connects to a network in OOBE, it finds the pre-association record and completes association automatically. A technician can also trigger this step manually from the Autopilot menu. Enroll and prepare the device. The device receives the applicable device-targeted policy, is marked as corporate-owned, and presents the configured OOBE experience. Monitor the deployment. Administrators can review association state and assigned policy in the Device association blade and filter devices by state, policy, manufacturer, or model. The device association lifecycle consists of the following states: Pre-associated: The device was added on the service side and is waiting to complete association in OOBE. Associated: The device completed association by writing the tenant affinity to UEFI and is ready for enrollment. This happens automatically when a pre-associated device syncs with an MDM provider. Pending removal: A request to remove the pre-association is being processed. A device's association can be removed by an administrator or partner with physical access to the device who manually runs a local script that clears the tenant affinity information stored in the device's UEFI. This action should be performed only when the device should no longer be associated with the organization, such as when it is sold, recycled, or transferred. Manage the full device lifecycle The association remains with the device through reset and reinstallation, helping preserve the organization's intended provisioning path when a device is redeployed internally. When a device permanently leaves the organization - for example, when it's sold, recycled, or transferred—the association should be removed as part of decommissioning. Because the tenant affinity is stored on the device, clearing a completed association can be performed via script locally on the physical device, without access to the service. This lifecycle model is intentional: association is durable during normal reuse inside the organization, while permanent removal can be completed by an admin or partner who has control of the physical device. Designed to work alongside your existing Windows Autopilot strategy Device association is part of Windows Autopilot device preparation and can coexist with traditional Windows Autopilot deployments in the same organization. For a device already registered with Windows Autopilot, the association state determines which deployment runs. If the device isn't associated, its Windows Autopilot registration takes precedence. If it is associated, the Windows Autopilot device preparation deployment takes precedence. This gives organizations a practical path to introduce device association while continuing to support existing Windows Autopilot investments. Get started To use device association, you'll need a supported physical Windows 11 device with TPM 2.0 enabled and in a healthy state. Virtual machines aren't supported because device association relies on hardware-backed identity verification. Start by reviewing the Windows Autopilot device association requirements, then create or update your Windows Autopilot device preparation policy. From there, export the device information, pre-associate the device in Intune, and let Windows complete the trusted association during OOBE. With device association, Windows Autopilot device preparation moves device trust, targeting, and customization earlier in the deployment journey - before enrollment and before the employee reaches the desktop. That means fewer setup decisions for users, more predictable deployments for IT, and stronger confidence that the right device is joining the right organization with the right configuration. Learn more Overview of Windows Autopilot device association Requirements for Windows Autopilot device association Set up Windows Autopilot device preparation with device association28KViews5likes28CommentsPreparing for end of support for CNAME auto-discovery in Windows MDM-only enrollment
Today, some organizations use an EnterpriseEnrollment DNS CNAME record to automatically direct devices to the Microsoft enrollment service during Windows MDM-only enrollment. Starting January 15, 2027, as part of our ongoing efforts to simplify and modernize enrollment experiences, Microsoft Intune will end support for CNAME-based auto-discovery in Windows MDM-only enrollment scenarios. This change reduces dependency on DNS-based discovery while providing a more consistent enrollment experience moving forward. After this change, users may need to enter the Microsoft enrollment server URL if it’s not already provided by the enrollment experience: https://enrollment.manage.microsoft.com/enrollmentserver/discovery.svc Who this change affects Your organization may be affected if: You use Windows MDM-only enrollment. You have configured an EnterpriseEnrollment DNS CNAME record. Your enrollment process depends on DNS record to automatically discover the enrollment service. You likely aren't affected if you exclusively use: Microsoft Entra join enrollment Microsoft Entra hybrid join enrollment Other enrollment methods that don't rely on EnterpriseEnrollment CNAME discovery How the user experience will change Today, in affected environments, a user can begin Windows MDM-only enrollment, and the enrollment service is automatically discovered using the organization’s EnterpriseEnrollment DNS CNAME record. The user doesn’t need to provide the enrollment server information. After this change, CNAME-based auto-discovery will no longer be used for these Windows MDM-only enrollment scenarios. If the enrollment service URL isn't already provided by the enrollment experience, the user will need to enter it when prompted. Enrollment can then continue using the Microsoft enrollment service URL. For example: Identifying affected environments Review your organization's DNS configuration and Windows MDM-only enrollment documentation.In particular, look for an EnterpriseEnrollment DNS record similar to: EnterpriseEnrollment.contoso.com If your organization configured the EnterpriseEnrollment record to support Windows MDM-only enrollment discovery, you should prepare for this change. You should also review and update documentation that assumes enrollment service discovery happens automatically through DNS, including: Internal enrollment guides Help desk procedures Device deployment instructions Provisioning documentation User onboarding materials Actions to take if you’re affected To prepare for this change we recommend the following actions: 1. Identify impacted enrollment workflows Review all Windows MDM-only enrollment scenarios used within your organization and determine whether they depend on EnterpriseEnrollment DNS discovery. 2. Update enrollment documentation Update user guides, knowledge base articles, onboarding materials, and other instructions to reflect the new enrollment process. 3. Prepare support teams Ensure help desk and deployment teams understand the change and know when the enrollment service URL may need to be provided. 4. Test enrollment scenarios Validate affected enrollment workflows before the change takes effect. Identify any required updates and determine where users may be prompted to enter the enrollment service URL. 5. Communicate with impacted users If users will need to enter the enrollment service URL, provide updated instructions before the change takes effect. Frequently asked questions Does this affect existing enrolled devices? No. Existing enrolled devices remain enrolled and aren’t affected by this change. Is Windows MDM-only enrollment being retired? No. Windows MDM-only enrollment remains supported. Only CNAME-based auto-discovery will become unsupported. Do I need to remove my EnterpriseEnrollment DNS record? Review your environment and DNS configuration requirements. This change only affects use of the record for Windows MDM-only enrollment auto-discovery. Will every user need to enter the enrollment service URL? Not necessarily. Some enrollment experiences may already provide enrollment server information. Manual entry is only required when the enrollment experience doesn’t provide it automatically. Should we begin testing now? Yes. We strongly recommend validating enrollment scenarios as early as possible and updating relevant documentation before this change takes effect. Next steps Review your Windows MDM-only enrollment processes and identify any dependencies on EnterpriseEnrollment DNS CNAME records. Update enrollment guidance, deployment instructions, onboarding materials, and help desk procedures that assume the enrollment service will be discovered automatically through DNS. Stay tuned to this blog for updates. If you have any questions, leave a comment below.5.4KViews0likes2Comments