Daily Intune News
2617
2729
2816162923031187321134567891011121314151611711819202122September’s most consequential change is Intune’s planned migration of Windows Health Attestation compliance evaluation from Device Health Attestation to Microsoft Azure Attestation for Windows 11, with the change scheduled by early 2027. Azure Attestation endpoint access will be important for devices using health-based compliance policies. Outside Intune, the clearest administrator guidance covered Windows Autopilot hybrid-join pre-provisioning, Remote Help licensing for Android COSU devices, and Advanced Analytics Device Query roles. Most of the 886 recorded changes were Configuration Manager updates, largely broad documentation metadata reclassification rather than operational product changes.
Intune · Device securityIntune will migrate Windows Health Attestation compliance evaluation for Windows 11 from Device Health Attestation (DHA) to Microsoft Azure Attestation (MAA) by early 2027. Organizations should provide network access to Azure Attestation endpoints or risk compliance-evaluation failures for health-based policies.
Windows Autopilot · Device enrollmentWindows Autopilot known-issues guidance says Microsoft Entra hybrid-join pre-provisioning can fail when policy conflict resolution requires domain-controller connectivity, particularly when a bring-your-own VPN is unavailable during technician flow. Avoid assigning policies that require this connectivity during technician flow.
Remote Help · Device enrollmentThe Remote Help planning guidance states that supported Zebra and Samsung devices in Android Dedicated Device (COSU) mode do not require a Sharer license; only the Helper needs a Remote Help license. Review licensing for these deployments and ensure Helpers are licensed.
Advanced Analytics · Endpoint analyticsAdvanced Analytics guidance now describes custom roles as needing permissions to view and access managed devices, with Organization/Read and Managed devices/Read provided as examples. The documentation no longer lists a separate Managed Devices/Query permission, so review custom roles against the updated guidance.
Configuration Manager · GeneralThe affected documentation now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`, replacing `core-infrastructure` and `microsoft-endpoint-configuration-manager`. The change is page metadata classification, with no administrator configuration action indicated.
Prioritize validating network access to Azure Attestation endpoints for Windows 11 devices evaluated with health-based compliance policies. Review Windows Autopilot technician-flow policies for domain-controller connectivity requirements, confirm Remote Help Helpers are licensed for supported Android COSU deployments, and audit Device Query custom roles for managed-device visibility and access. No configuration change is indicated by the broad Configuration Manager metadata updates.
This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.
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 planning guide now links to `integrate-windows-update-client-policies.md` instead of the previous `integrate-windows-update-for-business-windows-10.md` article.
The page adds upcoming features including MHS authentication for protected app activities, declarative VPP downloads, deployment plans, Defender launch during Android setup, bulk eSIM actions, new Apple settings, and Quick Machine Recovery policies. It also documents future macOS and iOS/iPadOS support changes and the September 2609 single-device page default.
The iOS app protection settings reference updated the Screen capture entry, documenting that Block prevents capture of work or school data, while Allow is the default and permits capture and sharing without restrictions.
The servicing information page changed the callout from Caution to Important; its message about impacts to updates, reliability, security mitigations, and feature enablement remains the same.
The China endpoints documentation now lists `https://graph.chinacloudapi.cn` instead of `https://graph.chinacloudapi.us`.
The page now recommends limiting script assignments, avoiding resource-intensive or frequent schedules, and using stable, actionable detection-script results to reduce device performance impact.
The known-issues documentation now explains that Windows Autopilot pre-provisioning for Microsoft Entra hybrid join can fail when policy conflict resolution requires domain controller connectivity, particularly when a BYO VPN is unavailable during technician flow.
The page’s update date changed from August 7, 2026, to September 1, 2026, and the note about new Microsoft Entra ID and Intune records after reset and re-enrollment—and cleaning up stale records—was removed.
The page date was updated, and the note about new device records being created after reset and re-enrollment, including the recommendation to clean up stale records, was removed.
The article’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for co-management content.
The page now uses the `configuration-manager` service metadata value with the `co-management` subservice.
The article now revises its explanation of how Configuration Manager distinguishes Windows Update client policies from WSUS, including the UseWUServer attribute.
The documentation 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 `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page now uses `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous metadata values.
The article’s service metadata changed to `configuration-manager`, and its subservice metadata changed to `core-infra`.
The page now uses `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous metadata values.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`, replacing the previous metadata values.
The article’s metadata now uses `core-infra` for `ms.subservice` and `configuration-manager` for `ms.service`.
The page now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`, replacing the previous metadata values.
The page now uses `core-infra` and `configuration-manager` as its `ms.subservice` and `ms.service` metadata values.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous identifiers.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The article metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-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 `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page 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’s metadata values changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The article’s service metadata changed from core-infrastructure/microsoft-endpoint-configuration-manager to core-infra/configuration-manager.
The document metadata now uses `core-infra` instead of `core-infrastructure` and `configuration-manager` instead of `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `configuration-manager` and `core-infra` instead of `microsoft-endpoint-configuration-manager` and `core-infrastructure`.
The article metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The article’s metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The page’s 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 `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The article metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The article’s service metadata changed from `microsoft-endpoint-configuration-manager`/`core-infrastructure` to `configuration-manager`/`core-infra`.
The page now uses `ms.subservice: osd` and `ms.service: configuration-manager` instead of the previous metadata 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 `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous values.
The article metadata now uses `core-infra` and `configuration-manager` for the service classification.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page now uses `core-infra` and `configuration-manager` metadata values instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The article now uses `core-infra` and `configuration-manager` for its service metadata instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous values.
The page now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`, replacing the previous metadata 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 `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous values.
The page now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`, replacing the previous metadata values.
The page 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 `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`, replacing the previous metadata values.
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` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous values.
The page now uses `ms.subservice: core-infra` and `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 `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 metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous metadata 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 `ms.subservice: core-infra` with `ms.service: configuration-manager`, replacing the previous values.
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 metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous metadata values.
The page metadata now uses `configuration-manager` with `core-infra` instead of `microsoft-endpoint-configuration-manager` with `core-infrastructure`.
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` for `ms.subservice` and `configuration-manager` for `ms.service`.
The page’s service metadata changed from `microsoft-endpoint-configuration-manager`/`core-infrastructure` to `configuration-manager`/`core-infra`.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`.
The article’s service metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `configuration-manager` and `core-infra` instead of `microsoft-endpoint-configuration-manager` and `core-infrastructure`.
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` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous metadata values.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `configuration-manager` with `core-infra` instead of `microsoft-endpoint-configuration-manager` with `core-infrastructure`.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page 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 now uses `configuration-manager` and `core-infra` service metadata labels instead of the previous values.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`.
The document’s metadata values changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page 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 now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous metadata values.
The article 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 `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The page 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` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The technical preview 2002.2 page now uses `ms.subservice: core-infra` and `ms.service: 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 `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page now uses `core-infra` and `configuration-manager` metadata values instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page’s service metadata changed from `microsoft-endpoint-configuration-manager` / `core-infrastructure` to `configuration-manager` / `core-infra`.
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: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page’s service metadata changed to `configuration-manager` and its subservice metadata changed to `core-infra`.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `configuration-manager` and `core-infra` instead of `microsoft-endpoint-configuration-manager` and `core-infrastructure`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
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` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page’s metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page’s service metadata was updated from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `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 `configuration-manager` with `core-infra` instead of `microsoft-endpoint-configuration-manager` with `core-infrastructure`.
The page metadata now uses `configuration-manager` with `core-infra` instead of `microsoft-endpoint-configuration-manager` with `core-infrastructure`.
The page’s metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page’s service metadata changed from `microsoft-endpoint-configuration-manager` and `core-infrastructure` to `configuration-manager` and `core-infra`.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `configuration-manager` and `core-infra` instead of `microsoft-endpoint-configuration-manager` and `core-infrastructure`.
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` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
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` with `configuration-manager` instead of `core-infrastructure` with `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 `ms.subservice: core-infra` and `ms.service: configuration-manager`, replacing the previous values.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The page’s service metadata changed from `microsoft-endpoint-configuration-manager` / `core-infrastructure` to `configuration-manager` / `core-infra`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The page metadata now uses `core-infra` and `configuration-manager` for its service classifications.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `configuration-manager` and `core-infra` instead of `microsoft-endpoint-configuration-manager` and `core-infrastructure`.
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: core-infra` and `ms.service: 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 `ms.subservice: core-infra` with `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 `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 article now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`, replacing the previous metadata values.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The article’s `ms.subservice` value changed from `core-infrastructure` to `core-infra`, and its `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous metadata values.
The application documentation now uses `core-infra` and `configuration-manager` metadata values instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The documentation replaces `ms.subservice: core-infrastructure` and `ms.service: microsoft-endpoint-configuration-manager` with `core-infra` and `configuration-manager`.
The page replaces `core-infrastructure` with `core-infra` and `microsoft-endpoint-configuration-manager` with `configuration-manager`.
The page now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous metadata values.
The page’s metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The article metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The article metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous values.
The page metadata changes `ms.subservice` from `core-infrastructure` to `core-infra` and `ms.service` from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
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` 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 changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page’s service classification changed from `core-infrastructure` / `microsoft-endpoint-configuration-manager` to `core-infra` / `configuration-manager`.
The page metadata now uses `configuration-manager` with `core-infra` instead of `microsoft-endpoint-configuration-manager` with `core-infrastructure`.
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 document metadata now uses `ms.subservice: core-infra` and `ms.service: 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 `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous values.
The page 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’s metadata values changed from `core-infrastructure` to `core-infra` and from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` metadata values.
The documentation metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The article now uses `ms.subservice: osd` and `ms.service: configuration-manager` 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 `ms.subservice: core-infra` and `ms.service: configuration-manager` in place of the previous metadata values.
The page’s service metadata changed to `configuration-manager` and its subservice metadata changed to `core-infra`.
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: core-infra` 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` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`, replacing the previous values.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The article’s metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page 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` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page now uses `core-infra` and `configuration-manager` service metadata values 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 `ms.subservice: core-infra` with `ms.service: configuration-manager`, replacing the previous 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` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `configuration-manager` and `core-infra` instead of `microsoft-endpoint-configuration-manager` and `core-infrastructure`.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous metadata values.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The checklist metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `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` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The page’s service metadata changed from `microsoft-endpoint-configuration-manager` / `core-infrastructure` to `configuration-manager` / `core-infra`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page now pairs `ms.subservice: core-infra` with `ms.service: configuration-manager`, replacing the previous identifiers.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The documentation metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `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 `ms.subservice: core-infra` and `ms.service: 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 metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The article now uses `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous metadata values.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The article metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The article metadata changes 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` for its subservice and service values.
The article metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The document metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `configuration-manager` and `core-infra` instead of `microsoft-endpoint-configuration-manager` and `core-infrastructure`.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The document’s service metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-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 `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` metadata values.
The documentation metadata changed from the previous Microsoft Endpoint Configuration Manager service labels to `core-infra` and `configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page now uses ms.subservice `core-infra` and ms.service `configuration-manager`, replacing the previous metadata values.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The documentation metadata now uses `core-infra` with `configuration-manager` instead of the previous service labels.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`.
The article 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` for its service classification.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The document’s ms.subservice tag changed from core-infrastructure to core-infra, and its ms.service tag changed from microsoft-endpoint-configuration-manager to configuration-manager.
The page now uses `core-infra` and `configuration-manager` for its subservice and service metadata values.
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 metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `ms.subservice: core-infra` with `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 article metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `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 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: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page’s metadata values 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 documentation now uses `core-infra` and `configuration-manager` for its service metadata 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 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 `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 metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The document’s metadata values changed from `core-infrastructure` to `core-infra` and from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The article’s service metadata changed from `microsoft-endpoint-configuration-manager` and `operating-system-deployment` to `configuration-manager` and `osd`.
The article metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `ms.subservice: osd` with `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `osd` with `configuration-manager` instead of `operating-system-deployment` 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 page metadata now uses `ms.service: configuration-manager` and `ms.subservice: osd` instead of the previous identifiers.
The page’s service metadata changed from `microsoft-endpoint-configuration-manager` and `operating-system-deployment` to `configuration-manager` and `os`.
The article’s `ms.subservice` and `ms.service` metadata values were updated to `core-infra` and `configuration-manager`.
The page metadata now uses `osd` and `configuration-manager` instead of `operating-system-deployment` and `microsoft-endpoint-configuration-manager`.
The article metadata changed from `core-infrastructure` to `core-infra` and from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page’s metadata now uses `ms.subservice: osd` and `ms.service: configuration-manager` instead of the previous values.
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` and `configuration-manager` instead of `operating-system-deployment` and `microsoft-endpoint-configuration-manager`.
The article metadata now uses `ms.subservice: osd` and `ms.service: configuration-manager`.
The page metadata now uses ms.subservice `core-infra` instead of `core-infrastructure` and 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 page’s service metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page now uses `ms.subservice: osd` and `ms.service: configuration-manager`, replacing the previous metadata values.
The page metadata now uses `osd` with `configuration-manager` instead of `operating-system-deployment` with `microsoft-endpoint-configuration-manager`.
The page now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous metadata values.
The page now uses `core-infra` for `ms.subservice` and `configuration-manager` for `ms.service`, replacing the previous values.
The page’s service metadata now uses `configuration-manager` and `core-infra` instead of `microsoft-endpoint-configuration-manager` and `core-infrastructure`.
The page now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous metadata values.
The article metadata now uses `configuration-manager` as the service and `core-infra` as the subservice.
The article metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous values.
The article metadata now uses `ms.subservice: osd` and `ms.service: configuration-manager`.
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 `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page tags changed from `core-infrastructure` to `core-infra` and from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The article 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 article’s metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The documentation metadata now uses `ms.subservice: osd` with `ms.service: configuration-manager` instead of the previous values.
The article metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`, replacing the previous values.
The article metadata now uses `ms.subservice: core-infra` with `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 `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The page now uses `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous metadata values.
The page now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous metadata values.
The article’s metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`, replacing the previous metadata values.
The page metadata now uses `ms.subservice: osd` with `ms.service: configuration-manager` instead of the previous values.
The page’s metadata values changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`, replacing the previous values.
The document metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The article’s service metadata changed to `configuration-manager` and its subservice metadata changed to `core-infra`.
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 `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata changes ms.subservice from `core-infrastructure` to `core-infra` and ms.service from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The document metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page 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` for its service classifications.
The page’s service metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses ms.subservice `core-infra` and ms.service `configuration-manager` instead of the previous values.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page’s service metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page’s metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `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 `configuration-manager` with subservice `core-infra` instead of `microsoft-endpoint-configuration-manager` with `core-infrastructure`.
The page now uses `ms.subservice: osd` with `ms.service: configuration-manager` instead of the previous metadata values.
The article’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` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: osd` with `ms.service: configuration-manager` instead of the previous values.
The article 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 article’s metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The document’s metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`.
The article metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The document metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous metadata values.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The article’s metadata now uses `osd` for the subservice and `configuration-manager` for the service instead of the previous values.
The article’s metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page’s metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The documentation metadata now uses `core-infra` with `configuration-manager` instead of the previous service and subservice values.
The document metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The article’s service and subservice metadata changed to `configuration-manager` and `core-infra`.
The article’s metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `configuration-manager` and `core-infra` instead of `microsoft-endpoint-configuration-manager` and `core-infrastructure`.
The article metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The article’s metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The article’s metadata values changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The article metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`, replacing the previous values.
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 article’s service metadata changed from operating-system-deployment/microsoft-endpoint-configuration-manager to osd/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 `osd` with `configuration-manager` instead of `operating-system-deployment` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `osd` with `configuration-manager` instead of `operating-system-deployment` with `microsoft-endpoint-configuration-manager`.
The article metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The documentation metadata now uses `ms.subservice: osd` with `ms.service: configuration-manager` instead of the previous values.
The document metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The document now uses `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous metadata values.
The page 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 pairs `ms.subservice: mdt` with `ms.service: configuration-manager`, replacing the previous values.
The release-notes page now uses `mdt` and `configuration-manager` as its service metadata values, replacing the previous values.
The samples guide now uses `ms.subservice: mdt` and `ms.service: configuration-manager` instead of the previous metadata values.
The page metadata now uses `core-infra` for `ms.subservice` and `configuration-manager` for `ms.service`.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`, replacing the previous metadata values.
The article’s metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The documentation’s metadata values changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `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 `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous metadata values.
The article metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata changed from `core-infrastructure` to `core-infra` and from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The article 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 changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `ms.subservice: osd` with `ms.service: configuration-manager` instead of the previous values.
The page now uses `ms.subservice: osd` and `ms.service: configuration-manager` instead of the previous metadata values.
The page metadata now uses `ms.subservice: osd` and `ms.service: configuration-manager` instead of the previous values.
The page now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous metadata values.
The documentation metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page’s metadata now uses `ms.subservice: osd` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The article now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous metadata values.
The article now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` metadata values.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The article now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous metadata 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` with `configuration-manager` instead of the previous service and subservice values.
The document’s service metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, and its subservice metadata changed from `core-infrastructure` to `core-infra`.
The article’s 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 page’s service metadata changed from `microsoft-endpoint-configuration-manager` with `operating-system-deployment` to `configuration-manager` with `osd`.
The page metadata now uses `ms.subservice: osd` with `ms.service: configuration-manager` instead of the previous values.
The article’s metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The article’s metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `ms.subservice: osd` with `ms.service: configuration-manager` instead of the previous values.
The documentation 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 documentation metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The article metadata now uses `ms.subservice: osd` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page now uses `ms.subservice=core-infra` and `ms.service=configuration-manager` instead of the previous identifiers.
The page now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-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 `mdt` as the subservice and `configuration-manager` as the service.
The page metadata now uses `configuration-manager` and `mdt` instead of `microsoft-endpoint-configuration-manager` and `microsoft-deployment-toolkit`.
The guide’s metadata now uses `mdt` and `configuration-manager` instead of the previous service identifiers.
The page now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` metadata values.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The article now uses `ms.subservice: osd` with `ms.service: configuration-manager` instead of the previous metadata values.
The page’s metadata changes ms.subservice from `core-infrastructure` to `core-infra` and ms.service from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The release notes now use `ms.subservice: core-infra` with `ms.service: configuration-manager`, replacing the previous metadata pair.
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` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The article’s service metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `osd` and `configuration-manager` instead of `operating-system-deployment` and `microsoft-endpoint-configuration-manager`.
The page’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’s metadata values changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `osd` for the subservice and `configuration-manager` for the service.
The page now uses `configuration-manager` with `core-infra` instead of `microsoft-endpoint-configuration-manager` with `core-infrastructure`.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page’s ms.subservice value changed from core-infrastructure to core-infra, and ms.service changed from microsoft-endpoint-configuration-manager to configuration-manager.
The documented metadata values changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The article now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous metadata 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` 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` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The article now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous metadata values.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`, replacing 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 changed from `microsoft-endpoint-configuration-manager` / `core-infrastructure` to `configuration-manager` / `core-infra`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The article metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The article’s 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 `configuration-manager` and `core-infra` instead of `microsoft-endpoint-configuration-manager` and `core-infrastructure`.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `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’s metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `configuration-manager` and `core-infra` instead of `microsoft-endpoint-configuration-manager` and `core-infrastructure`.
The article metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The article’s metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The documented values changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The documentation metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The article metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The page now uses `ms.subservice=core-infra` and `ms.service=configuration-manager` instead of the previous metadata values.
The documentation metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The article metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `configuration-manager` and `core-infra` instead of `microsoft-endpoint-configuration-manager` and `core-infrastructure`.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The article metadata changed from `core-infrastructure` to `core-infra` and from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
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 `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 metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous values.
The documentation metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `core-infra` for ms.subservice and `configuration-manager` for ms.service.
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 `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page’s metadata tags changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata changed from `core-infrastructure` to `core-infra` and from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The document metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-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 `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `osd` with `configuration-manager` instead of `operating-system-deployment` with `microsoft-endpoint-configuration-manager`.
The page now uses `ms.subservice: osd` with `ms.service: configuration-manager` instead of the previous metadata values.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata changed ms.subservice from core-infrastructure to core-infra and ms.service from microsoft-endpoint-configuration-manager to configuration-manager.
The documented `ms.subservice` value changed from `core-infrastructure` to `core-infra`, and `ms.service` changed from `microsoft-endpoint-configuration-manager` to `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 `core-infra` and `configuration-manager` instead of the previous subservice and service values.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous values.
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 metadata now uses `ms.subservice: mdt` with `ms.service: configuration-manager`, replacing the previous values.
The page metadata now uses `ms.subservice: mdt` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `ms.subservice: mdt` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `mdt` and `configuration-manager` instead of `microsoft-deployment-toolkit` and `microsoft-endpoint-configuration-manager`.
The page now uses `mdt` with `configuration-manager` instead of `microsoft-deployment-toolkit` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `mdt` for `ms.subservice` and `configuration-manager` for `ms.service`.
The UDI reference page now uses `ms.subservice: mdt` paired with `ms.service: configuration-manager`, replacing the previous metadata values.
The documentation metadata now uses `mdt` with `configuration-manager` instead of `microsoft-deployment-toolkit` with `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 changed `ms.subservice` from `core-infrastructure` to `core-infra` and `ms.service` from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page’s service metadata changed from `microsoft-endpoint-configuration-manager` and `core-infrastructure` to `configuration-manager` and `core-infra`.
The document now uses `core-infra` and `configuration-manager` for its service metadata.
The documentation metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The article 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` 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 metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`, replacing the previous values.
The article metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`, replacing the previous metadata values.
The page now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous metadata values.
The documentation 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 metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The article metadata now uses `ms.subservice: core-infra` 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 `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The article 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 article metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `configuration-manager` and `core-infra` instead of `microsoft-endpoint-configuration-manager` and `core-infrastructure`.
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` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The article’s service metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The article’s metadata values changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page 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 changes the subservice value from `core-infrastructure` to `core-infra` and the service value from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The article metadata changed from the Microsoft Deployment Toolkit and Microsoft Endpoint Configuration Manager labels to `mdt` and `configuration-manager`.
The page now uses `ms.subservice: osd` and `ms.service: configuration-manager` instead of the previous metadata 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` 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 `core-infra` for the subservice and `configuration-manager` for the service.
The page now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous metadata values.
The article metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The article now uses `core-infra` and `configuration-manager` for its `ms.subservice` and `ms.service` metadata values.
The page metadata changes `ms.subservice` from `core-infrastructure` to `core-infra` and `ms.service` from `microsoft-endpoint-configuration-manager` to `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: core-infra` and `ms.service: configuration-manager`.
The documentation metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The article now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`, replacing the previous metadata 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` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The article now uses `core-infra` and `configuration-manager` for its service metadata instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The article now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` in place of the previous metadata values.
The article metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page’s service metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The article’s service metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` 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 article metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining the co-management subservice.
The page metadata now uses `configuration-manager` instead of `microsoft-endpoint-configuration-manager` for the service label.
The page metadata now uses `configuration-manager` instead of `microsoft-endpoint-configuration-manager` for `ms.service`.
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’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 document’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The article now pairs `ms.subservice: co-management` with `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.
The page’s service metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining the co-management subservice pairing.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; its `ms.subservice` remains `co-management`.
The article’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page’s `ms.service` value changes from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`; `ms.subservice` remains `other`.
The page'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` for the co-management subservice.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; the co-management subservice remains associated.
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 tutorial’s `ms.service` value 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 co-management subservice.
The page’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 document’s metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The document’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, paired with `ms.subservice: protect`.
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 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 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: core-infra` with `ms.service: configuration-manager` instead of the previous values.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `protect`.
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 page now uses `ms.service: configuration-manager` instead of `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 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 `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 page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous values.
The page now uses `core-infra` and `configuration-manager` as its subservice and service metadata values.
The page now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous metadata values.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The document now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous metadata values.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The article’s service metadata changed from `microsoft-endpoint-configuration-manager` and `operating-system-deployment` to `configuration-manager` and `osd`.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`, replacing the previous values.
The article metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`, replacing the previous metadata values.
The document now uses `core-infra` for `ms.subservice` and `configuration-manager` for `ms.service`, replacing the previous values.
The document metadata now uses `core-infra` for `ms.subservice` and `configuration-manager` for `ms.service`, replacing the previous values.
The documentation metadata changed `ms.subservice` from `core-infrastructure` to `core-infra` and `ms.service` from `microsoft-endpoint-configuration-manager` to `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` with `configuration-manager` instead of the previous service identifiers.
The documentation metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`, replacing the previous values.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`, replacing 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` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The documentation metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The documentation metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The document metadata now uses `core-infra` for `ms.subservice` and `configuration-manager` for `ms.service`.
The article metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`, replacing the previous metadata values.
The document metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The documentation 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 metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `configuration-manager` as the service and `core-infra` as the subservice.
The page now uses `core-infra` for `ms.subservice` and `configuration-manager` for `ms.service`.
The documentation now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The documentation metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The documentation now uses `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous values.
The page’s service metadata changed from `microsoft-endpoint-configuration-manager` and `core-infrastructure` to `configuration-manager` and `core-infra`.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` metadata values.
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` for its subservice and service values.
The documentation metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous metadata values.
The document metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`.
The page now uses `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous metadata values.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page’s metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The page’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 documentation now uses `core-infra` and `configuration-manager` as the subservice and service metadata values.
The documentation metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.service: configuration-manager` and `ms.subservice: core-infra` instead of the previous identifiers.
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 page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` 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 `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` 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 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 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 page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `co-management`.
The article metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The page metadata now uses `core-infra` and `configuration-manager` service identifiers.
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 article metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The article now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` metadata values.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
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 changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`, replacing the previous metadata values.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `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 `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The page 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 changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The article’s metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page’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 `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The article’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` 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 article’s metadata changed from `microsoft-endpoint-configuration-manager` and `core-infrastructure` to `configuration-manager` and `core-infra`.
The documentation metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page 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’s service metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The article metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The documentation replaces `ms.subservice: core-infrastructure` with `core-infra` and `ms.service: microsoft-endpoint-configuration-manager` with `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` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The page metadata now uses `core-infra` and `configuration-manager` for its subservice and service 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` 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 `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The article metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page’s service metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The documentation now uses `core-infra` and `configuration-manager` metadata values instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `osd` for the subservice and `configuration-manager` for the service.
The page now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` in place of the previous metadata values.
The document metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page’s metadata tags changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `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 `ms.subservice: core-infra` with `ms.service: configuration-manager`.
The article now uses `ms.subservice: osd` and `ms.service: configuration-manager` instead of the previous metadata 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 `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page now uses `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous metadata values.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `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 `ms.subservice: core-infra` and `ms.service: 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 `configuration-manager` instead of `microsoft-endpoint-configuration-manager` for `ms.service`.
The article now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`, replacing the previous metadata values.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous metadata values.
The page now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous metadata values.
The document metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The page metadata now uses `configuration-manager` and `core-infra` instead of the previous service identifiers.
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 `configuration-manager` for the service and `core-infra` for the subservice.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page’s 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 article metadata now uses `ms.subservice: osd` and `ms.service: configuration-manager`.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The checklist 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 `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The article was rewritten to explain co-management scenarios, scan source policies, common pitfalls, troubleshooting, and the effects of receiving Windows updates directly from Windows Update. It documents impacts to compliance reporting, Microsoft app updates, third-party updates, and software-update-based client deployment.
The article now links to `integrate-windows-update-client-policies.md` instead of `integrate-windows-update-for-business-windows-10.md`.
The version 1706 documentation now links to the Windows Update client policies article at a new path, retaining the same configuration section anchor.
The Configuration Manager article covering Windows Update client policies, co-management considerations, limitations, prerequisites, and client identification procedures was deleted.
The conditional access quickstart now uses `ms.service: configuration-manager` with the co-management subservice instead of `microsoft-endpoint-configuration-manager`.
The documentation metadata now uses `core-infra` and `configuration-manager` for the service and subservice tags.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `mdt` and `configuration-manager` instead of `microsoft-deployment-toolkit` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`, replacing the previous values.
Supported Zebra and Samsung devices in Android Dedicated Device (COSU) mode don't require a Sharer license; only the Helper needs a Remote Help license.
The documentation now describes custom roles as needing permissions to view and access managed devices, with Organization/Read and Managed devices/Read as examples. The separate Managed Devices/Query permission is no longer listed.
The documentation now specifies that Device Query users must be assigned a custom role; the Help Desk Operator role option was removed.
