Monday, 5 January 2026

A new article documents using the Windows quality update policy to deploy Hotpatch security updates through Autopatch, including benefits and prerequisites.

A new consolidated article documents driver update policies: automatic or manual approval, pausing and approving drivers, prerequisites, supported editions, GCC limitations, RBAC, deployment planning, and reporting.

The driver update overview replaced its telemetry guidance with the shared device-configuration requirements, including enrollment, Entra join state, required telemetry, the Sign-In Assistant service, and Windows Update and Autopatch endpoints.

The overview renamed the Windows Update client policy section and clarified that each update policy type has its own prerequisites, while feature, quality, driver, and Hotpatch use the same backend service as Autopatch.

The guidance for devices ineligible for Windows 11 now points administrators to the central feature update policy workflow for policy behavior, creation, and licensing requirements.

The driver policy article now links its prerequisite, deployment-planning, and FAQ reference to the renamed driver-updates article.

The Windows 10-to-Windows 11 upgrade link now directs to the separate feature-updates-windows-10 article rather than an anchor in the main article.

The Windows updates index changed its quality updates Learn more link from quality-updates-policy.md to the renamed quality-updates.md article.

The driver overview removed the Windows diagnostic-data reporting section and its steps to enable the Windows data setting in Intune.

The former driver-updates-overview.md article was removed as part of the documentation rename to the consolidated driver-updates.md article.

The article removed the Microsoft Entra registered-device limitations section and its next-steps links, leaving the core policy guidance in the main article.

The former quality-updates-policy.md article was removed as part of the documentation rename to quality-updates.md.

The driver reports article now states that Windows diagnostic data must be enabled and gives the Intune path: Tenant administration > Connectors and tokens > Windows data, then enable the processor-configuration setting.

The article removed duplicate device prerequisite text and corrected the organizational-report anchor from Windows 10 feature updates to Windows feature updates.

The archived What's New entry now links Windows driver update policy guidance to driver-updates.md instead of driver-updates-overview.md.

The app monitoring article refreshed its wording and clarified several Android AOSP line-of-business app error descriptions and administrator actions, including conflicts, network failures, size limits, and download validation.

The Company Portal article now tells administrators to use `winget install "Company Portal" --source msstore` to download the Windows Company Portal app and its dependencies.

The in-development entry changed the Android Intune settings catalog settings-list link to a relative documentation path.

The Windows diagnostic data page now links the Windows driver updates report to driver-updates.md rather than the retired overview article.

The in-development page added planned items: an Intune admin center link to Lenovo Device Orchestration for Windows 11, Android settings catalog filtering by management mode, DDM assignment filters for Apple software updates, expanded managed-app device-management filter values, and Zimperium certificate inventory sync.

The co-management Windows Update workload guidance now links to the Windows software updates index rather than the former configure page.