Support For Windows 11
The documentation now lists Windows 11 version 26H2 (build 10.0.26300) with support indicators shown as ❌, ✅, and ✅.
A cross-product view of Microsoft Intune changes related to Windows.
The documentation now lists Windows 11 version 26H2 (build 10.0.26300) with support indicators shown as ❌, ✅, and ✅.
The BitLocker documentation now uses updated links for the encryption report and Monitor disk encryption, and clarifies that recovery keys can be viewed and managed from the encryption report.
The Windows platform guide now links to the endpoint security devices page at a new documentation path; the link description is unchanged.
The documentation date was updated, and the support table now lists ConfigMgr 2509, 2603, and 2609 instead of 2503, 2509, and 2603.
The documentation now lists Windows 11 25H2 as supported with ConfigMgr 2503, 2509, and 2603, and adds ConfigMgr 2609 to the matrix.
The documentation table now lists ConfigMgr 2509, 2603, and 2609 instead of 2503, 2509, and 2603. The page date was also updated.
The documentation now states that Configuration Manager supports data deduplication with distribution points on supported Windows Server versions, replacing the explicit “Windows Server 2012 or later” wording.
The Configuration Manager documentation now links to `integrate-windows-update-client-policies.md` instead of `integrate-windows-update-for-business-windows-10.md`.
The article’s guidance on integrating Windows Update client policies was revised. It continues to state that computers using Windows Update client policies or Windows Insiders aren’t evaluated in Windows servicing plans and must use Configuration Manager software updates with WSUS.
The article’s service metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, and its subservice metadata changed from `core-infrastructure` to `core-infra`.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The task sequence upgrade documentation now uses the `osd` and `configuration-manager` metadata values.
The page metadata now uses `osd` with `configuration-manager` instead of `operating-system-deployment` with `microsoft-endpoint-configuration-manager`.
The article now uses `ms.subservice: osd` with `ms.service: configuration-manager` instead of the previous metadata values.
The page metadata changed from `microsoft-endpoint-configuration-manager`/`core-infrastructure` to `configuration-manager`/`core-infra`.
The page metadata now uses `osd` with `configuration-manager` instead of `operating-system-deployment` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `core-infra` for `ms.subservice` and `configuration-manager` for `ms.service`.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The article metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `osd` for `ms.subservice` and `configuration-manager` for `ms.service`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The article metadata now uses `osd` with `configuration-manager` instead of `operating-system-deployment` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `core-infra` instead of `core-infrastructure` and `configuration-manager` instead of `microsoft-endpoint-configuration-manager`.
The article metadata now uses `ms.subservice: osd` with `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `ms.subservice: osd` and `ms.service: configuration-manager`.
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 `osd` with `configuration-manager` instead of `operating-system-deployment` with `microsoft-endpoint-configuration-manager`.
The page now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `osd` and `configuration-manager` instead of `operating-system-deployment` and `microsoft-endpoint-configuration-manager`.
The article’s service metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, and its subservice metadata changed from `operating-system-deployment` to `osd`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The documentation now uses `core-infra` and `configuration-manager` as the service metadata values.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page now uses `core-infra` and `configuration-manager` metadata values instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `core-infra` instead of `core-infrastructure` and `configuration-manager` instead of `microsoft-endpoint-configuration-manager`.
The article metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The document’s service metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
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` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: osd` with `ms.service: configuration-manager` instead of the previous values.
The document metadata now uses `ms.subservice: mdt` and `ms.service: configuration-manager` instead of the previous identifiers.
The page metadata now uses `mdt` as the subservice and `configuration-manager` as the service.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `co-management`.
The page metadata now uses `osd` as the subservice and `configuration-manager` as the service instead of `operating-system-deployment` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `core-infra` and `configuration-manager` for its service classification.
The page’s service metadata changed from Microsoft Endpoint Configuration Manager and operating-system-deployment to Configuration Manager and osd.
The page metadata now uses `osd` with `configuration-manager` instead of `operating-system-deployment` with `microsoft-endpoint-configuration-manager`.
The page’s metadata now uses `osd` as the subservice and `configuration-manager` as the service.
The page metadata now uses `osd` and `configuration-manager` instead of `operating-system-deployment` and `microsoft-endpoint-configuration-manager`.
The page now uses the `configuration-manager` service metadata value with the `co-management` subservice.
The documentation metadata now uses `core-infra` for `ms.subservice` and `configuration-manager` for `ms.service`.
The article’s service metadata was updated from `operating-system-deployment` and `microsoft-endpoint-configuration-manager` to `osd` and `configuration-manager`.
The documentation metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.
The service metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining the `sdk` subservice.
The page’s ms.service value 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 SDK subservice association remains.
The page's `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while `ms.subservice` remains `sdk`.
The documentation service tag changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while `ms.subservice` remains `sdk`.
The documentation metadata changes `ms.service` from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining the SDK subservice classification.
The page 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 now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`; its `ms.subservice: sdk` remains unchanged.
The documentation 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’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while the SDK subservice association remains.
The page metadata changes `ms.service` from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while the `sdk` subservice remains paired with it.
The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.
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 SDK subservice association remains.
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 `sdk`.
The page now pairs ms.subservice=sdk 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 metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`, while the SDK subservice remains unchanged.
The documentation service label 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 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’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining the SDK subservice.
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 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`.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while the `sdk` subservice remains associated.
The documentation now pairs `ms.subservice: sdk` with `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.
The documentation’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` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while remaining paired with `ms.subservice: sdk`.
The documentation 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.
The page metadata changed ms.service from microsoft-endpoint-configuration-manager to configuration-manager while retaining ms.subservice as sdk.
The documentation metadata changes `ms.service` from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining the SDK subservice.
The documentation metadata changed the service classification from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The documentation now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`; `ms.subservice: sdk` remains unchanged.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining the SDK subservice classification.
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`, while retaining the SDK subservice.
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; ms.subservice remains sdk.
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 documentation now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`, paired with the SDK subservice.
The page changes the ms.service metadata from microsoft-endpoint-configuration-manager to configuration-manager while retaining ms.subservice=sdk.
The page 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 documentation's `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.
The `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; the `ms.subservice` value remains `sdk`.
The page metadata changed from `ms.service: microsoft-endpoint-configuration-manager` to `ms.service: configuration-manager`.
The documentation changes the `ms.service` metadata value from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining `ms.subservice: sdk`.
The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager` while retaining the `sdk` subservice.
The page metadata changes `ms.service` from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining `ms.subservice: sdk`.
The page’s ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager; ms.subservice remains sdk.
The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.