Tuesday, 6 January 2026

A new FAQ covers driver policy conflicts, reboot coordination, driver availability and removal, synchronization, pause behavior, extension drivers, co-management, deadlines, deferrals, user experience settings, and inventory timing.

The driver updates overview removed its Frequently Asked Questions section, including assignment filters, Autopilot, rollback, policy conflict, pauses, deadlines, deferrals, and co-management guidance, following publication of a separate FAQ article.

The expedited quality update reporting steps were renumbered using Markdown auto-numbering without changing the report navigation or actions.

The article states feature update policies are public-cloud only and not supported in GCC High or DoD, distinguishes Intune Plan 1 from Autopatch-entitled licensing for gradual rollout and optional updates, and clarifies LTSC is unsupported.

The overview renames the Workplace Joined limitation section for Microsoft Entra registered devices and states that feature, quality, driver, and Hotpatch policies relying on WUfB DS cannot be used on those devices.

The Windows updates overview moves Microsoft Entra registered-device restrictions into its general prerequisites: WUfB DS-backed feature, quality, driver, and Hotpatch policies are unsupported, while update rings remain available.

The update rings article clarifies that Intune Plan 1 is required for core policy creation and assignment and updates platform and edition wording.

The registered-device limitation sentence received a formatting-only correction.

The update rings article made a minor wording change to the statement that Windows Holographic for Business supports a subset of Windows update settings.

The article replaced a hard-coded list of qualifying Windows licenses with a link to the Autopatch entitlement licensing documentation for gradual rollout and optional feature updates.

The article heading changed from Manage your Windows Update rings to Manage update rings.

The feature update policy prerequisites removed the instruction to enable data collection for reporting.

The feature update reports article reorganized diagnostic-data requirements into tenant and device sections, explains that Windows update reports require sharing diagnostic data with Intune, and removes older duplicate collection text.

The driver reports article reorganized prerequisites into shared device and tenant requirement sections and states Windows diagnostic data must be collected at Required or higher for complete status and event reporting.

The report requirements now separate tenant configuration from device configuration and direct admins to enable Windows diagnostic data at Required or higher for driver-update reporting.

The quality update reports article removed blank lines only.

The manual Company Portal article now uses `winget download "Company Portal" --source msstore` rather than the install command, and identifies the default Downloads folder.

The Company Portal download command was indented as a PowerShell block and the Downloads-folder guidance was converted from a note to regular text.

The EPM plan replaced a support note with a dedicated statement that Endpoint Privilege Management supports specified virtual platforms.

The privacy data-storage article changed the documented Intune audit-log retention period from up to one year to up to two years; personal data deletion remains described as within 30 days after deletion.

The in-development page says Apple’s Rapid Security Responses rebrand to Background Security Improvements will be reflected in iOS/iPadOS Settings Catalog restrictions, and changes Android management-mode filtering to future tense.

Intune's February release adds two new Managed Home Screen RBAC permissions—TemporarilySuspendManagedHomeScreen and RestoreManagedHomeScreen—to the School Administrator and Help Desk Operator roles, enhancing Android device management. No admin action is needed, but reviewing role assignments and updating documentation is recommended.

The release notes now state that Microsoft Deployment Toolkit and its Configuration Manager integration are retired and unsupported, warn that retained MDT task-sequence steps can cause corruption or modification failures, and point to Autopilot or supported OSD.

The MDT retirement warning changed the instruction to say customers should remove MDT task-sequence steps and MDT integration to avoid corruption and modification failures.

The EPM FAQ replaces the statement that Azure Virtual Desktop is unsupported with a supported-virtual-devices section and clarifies that administrator launches matching elevation rules are reported as unmanaged elevations.

The EPM planning article now states that EPM policies support Azure Virtual Desktop single-session VMs instead of listing Azure Virtual Desktop as unsupported.