Daily Intune News
A cross-product view of Microsoft Intune changes related to Device security.
What and why: Microsoft Intune will migrate Windows Health Attestation compliance evaluation from the current Device Health Attestation (DHA) service to Microsoft Azure Attestation (MAA). This is an Intune service-side change that will happen automatically.
Intune will migrate Windows Health Attestation from Device Health Attestation to Microsoft Azure Attestation by early 2027. Organizations must ensure network access to Azure Attestation endpoints to maintain compliance evaluation for Windows 11 devices using health-based policies, or risk compliance failures.
The document’s metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `protect`.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The article’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The article’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The BitLocker settings documentation now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.
The documentation now uses `configuration-manager` instead of `microsoft-endpoint-configuration-manager` for the `ms.service` metadata value.
The document’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page’s ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager while retaining ms.subservice: protect.
The article’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; the `ms.subservice` value remains `protect`.
The page’s ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `protect`.
The page metadata changed its `ms.service` value from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The article’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.
The page metadata changes ms.service from microsoft-endpoint-configuration-manager to configuration-manager.
The page now uses `configuration-manager` instead of `microsoft-endpoint-configuration-manager` for its service metadata.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page metadata now pairs `ms.subservice: protect` with `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.
The page’s ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager.
The article’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`, while retaining `ms.subservice: protect`.
The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.
The page metadata now pairs `ms.subservice: protect` with `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while the `protect` subservice pairing is retained.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page metadata now uses `configuration-manager` instead of `microsoft-endpoint-configuration-manager` for `ms.service`.
The document’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page’s service metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page’s service metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The document’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, paired with `ms.subservice: protect`.
The page now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The documentation metadata now uses `configuration-manager` instead of `microsoft-endpoint-configuration-manager` for the service association.
The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.
The documentation page now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.
The documentation metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.
The page’s ms.service metadata changed from microsoft-endpoint-configuration-manager to configuration-manager.
The page metadata now uses `configuration-manager` instead of `microsoft-endpoint-configuration-manager` for `ms.service`.
The document’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page’s ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager while remaining paired with the protect subservice.
The page’s service metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while the `protect` subservice remains paired with it.
The page’s Microsoft Learn service metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.
The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page metadata changes `ms.service` from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `protect`.
The page metadata changes `ms.service` from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `configuration-manager` instead of `microsoft-endpoint-configuration-manager` for `ms.service`.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The documentation metadata changes the `ms.service` value from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining `ms.subservice: sdk`.
The page metadata changes `ms.service` from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page’s ms.service metadata changed from microsoft-endpoint-configuration-manager to configuration-manager.
The document’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page’s service metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining the `sdk` subservice.
The reference now uses `ms.service = configuration-manager` with `ms.subservice = sdk`, replacing `microsoft-endpoint-configuration-manager`.
The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The prerequisites now list RHEL 10.1 with Podman 5.8.2 as the default and explain that the ip_tables kernel module must be manually loaded before Tunnel installation.
The page metadata changed from `ms.service: microsoft-endpoint-configuration-manager` to `ms.service: configuration-manager`.
The documentation’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for the SDK subservice.
The documentation changed the ms.service value from microsoft-endpoint-configuration-manager to configuration-manager.
The page's `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining `ms.subservice: sdk`.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining `ms.subservice: sdk`.
The documentation metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; the `sdk` subservice pairing remains.
The page’s ms.service metadata changed from microsoft-endpoint-configuration-manager to configuration-manager while retaining the SDK subservice association.
The page’s ms.service metadata changed from microsoft-endpoint-configuration-manager to configuration-manager while remaining paired with ms.subservice=sdk.
The documentation metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.
The documentation metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for `ms.service`.
The page metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for `ms.service`.
The page’s ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager while ms.subservice remains sdk.
The documentation now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.
The page’s ms.service metadata changed from microsoft-endpoint-configuration-manager to configuration-manager while retaining the SDK subservice.
The documentation service metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for the `SMS_TopThreatsDetected` WMI class reference.
The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page now documents version 20260818.1, agent and server image digests, minor bug fixes, and package and security updates for the August 18, 2026 release.
The Configure baselines documentation now links to the Windows 365 for Agents security baseline settings reference.
The security baselines overview now links to the Windows 365 for Agents security baseline, including its Version 24H1 settings reference.
Intune now documents the Windows 365 for Agents security baseline version 24H1, including default settings for Cloud PCs running agentic workloads across Windows 11, Microsoft Edge, and Microsoft Defender for Endpoint.
The monitoring guidance now lists log collection status—completed, failed, or in progress—instead of an Incident ID. It also says Microsoft can use logs collected after reproducing an issue during verbose log collection for investigation.
The prerequisites page no longer lists `powerlift-frontdesk.acompli.net` as a Diagnostic Endpoint.
The documentation now explains that Yes disables and No enables catch-up scans because the settings are named “Disable catch-up...”. Full-scan catch-up is disabled when not configured, while quick-scan catch-up is enabled by default; the scan triggers after two missed scheduled scans are also specified.
The documented default for catch-up full scans changed to disabled, while catch-up quick scans remain enabled by default. The settings now specify that catch-up scans occur after two consecutive missed scheduled scans and require a configured scheduled scan.
The documentation now explains how to retrieve existing MBAM groups with PowerShell and map them to equivalent Configuration Manager BitLocker portal groups during migration.
The page metadata date changed from 08/02/2024 to 08/10/2026. No substantive documentation or product changes are shown.
The page’s metadata date changed from August 2, 2024, to August 10, 2026. No substantive content change is shown.
The setup page removes the direct link to BlackBerry UES integration instructions and now tells administrators to sign in with Microsoft Entra and complete setup.
The Microsoft Tunnel MAM for Android page updates links for MAM certificate trust APIs, including the MAMCertTrustWebViewClient reference link.
The prerequisites now list RHEL 9.8 with Podman 5.8.2 or later as the default and explain that the ip_tables kernel module must be loaded manually before Tunnel installation.
Updated Microsoft Intune documentation in intune/device-configuration/endpoint-security/firewall.md.
Updated Microsoft Intune documentation in intune/device-security/microsoft-tunnel/prerequisites.md.
Updated Microsoft Intune documentation in intune/device-security/microsoft-tunnel/upgrade.md.
Updated Microsoft Intune documentation in intune/device-security/endpoint-security-policies.md.
Updated Microsoft Intune documentation in intune/device-configuration/endpoint-security/antivirus.md.
Updated Microsoft Intune documentation in intune/device-security/overview.md.
Updated Microsoft Intune documentation in intune/device-security/mobile-threat-defense/setup-blackberry.md.
Updated Microsoft Intune documentation in intune/configmgr/tenant-attach/endpoint-security-get-started.md.
Updated Microsoft Intune documentation in intune/configmgr/tenant-attach/deploy-antivirus-policy.md.
Updated Microsoft Intune documentation in intune/configmgr/tenant-attach/deploy-asr-policy.md.
Updated Microsoft Intune documentation in intune/configmgr/tenant-attach/deploy-firewall-policy.md.
Updated Microsoft Intune documentation in intune/configmgr/protect/deploy-use/bitlocker/recovery-service.md.
