Daily Intune News
2617
2729
28161629230311873211345678910111213141516117118192021222324225262728232958
305122534September’s most consequential Intune change is the planned migration of Windows Health Attestation compliance evaluation for Windows 11 from Device Health Attestation to Microsoft Azure Attestation. The service-side migration is automatic, but affected environments need network access to Azure Attestation endpoints. Intune also gained more granular Windows Autopatch approval and reporting controls, while Security Copilot became included with Microsoft 365 E5 and E7 plans. Most remaining activity was Configuration Manager documentation maintenance, with meaningful 2609 guidance covering SQL prerequisites and the removal of Asset Intelligence reporting.
Intune · Device securityIntune plans to migrate Windows Health Attestation compliance evaluation for Windows 11 from the Device Health Attestation service to Microsoft Azure Attestation by early 2027. The migration occurs automatically on the service side, but organizations must provide network access to Azure Attestation endpoints or health-based compliance evaluation can fail.
Intune · ComplianceRolling out from September 1 through October 15, 2026, the enhancements add customizable automatic or manual approvals, deferral settings, update pausing, and per-device reporting for Windows quality, .NET Framework, and quick machine recovery updates.
Configuration Manager · GeneralThe updated support guidance marks SQL Server 2016 and SQL Server 2016 Express as deprecated in version 2609. SQL Server editions earlier than SQL Server 2017 CU2 must be upgraded before installing or updating to 2609, and the Visual C++ Redistributable on secondary sites must also be updated.
Configuration Manager · GeneralThe updated operations guidance says that, starting in version 2609, the Catalog Synchronization and Inventoried Software Status sections and Asset Intelligence reports are removed. Procedures on the page apply to version 2603 and earlier, so administrators should review reporting dependencies before upgrading.
Security Copilot · ComplianceSecurity Copilot is now included in Microsoft 365 E5 and E7 plans, with monthly Security Compute Units, developer tools, and agents integrated across Defender, Entra, Intune, Purview, and the Security Copilot portal. No purchase or administrator action is required for the included capability; additional paid features remain optional.
Prioritize Azure Attestation endpoint access for Windows 11 devices using health-based compliance policies. Review Windows Autopatch approval, deferral, pause, and reporting options during its September 1–October 15 rollout. For Configuration Manager 2609 plans, validate SQL Server and secondary-site Visual C++ prerequisites and assess dependencies on Asset Intelligence reports. Microsoft 365 E5/E7 organizations receive Security Copilot, monthly Security Compute Units, and developer tools without a new purchase or required action.
This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.
The article now defines device categories as labels, explains their relationship to dynamic Microsoft Entra security groups, and covers creating categories, building groups, and assigning categories to devices.
The index now links to the device management overview, uses updated titles for device categories and primary-user tasks, and removes links for endpoint security device management, admin tasks, and encryption status details.
The instructions now direct administrators to select **Remove data** > **Retire** from the device overview action icons, instead of selecting **Retire** directly.
The new guidance explains how to rename managed devices from the Intune admin center, supported platforms, platform-specific naming rules, bulk-renaming variables, and limitations such as hybrid-joined Windows devices not being supported.
The article now explains how to open a device’s Device details tab, distinguishes read-only inventory from editable Properties, and documents hardware and software inventory refreshing every seven days from enrollment.
The instructions specify selecting **Locate device** on Windows and **Locate** > **Locate device** on iOS and Android. Location details remain available from the map pin.
The article was retitled and updated to explain how to change or remove a device’s primary user from the Properties tab, along with how Intune assigns and uses the primary user.
The documentation consistently renames the action to “Remove apps and configurations” and updates the steps to select Remove data > Remove apps and configurations.
The instructions now direct administrators to select Locate before choosing either Play Lost Mode sound or Play lost device sound.
The archive page now links to the Admin tasks content under Governance instead of Device management.
The device overview instructions now direct administrators to select Remove data, then Autopilot reset.
The instructions now say to select **Secure** before choosing **Disable Activation Lock** in the device overview action menu.
The instructions now direct administrators to select **Remove data** before selecting **Fresh Start** in the device overview pane.
The documented steps changed from selecting **Full scan** directly to selecting **Microsoft Defender** > **Run full malware scan**.
The Intune What’s new page was updated, including a new metadata date, and the entry describing bulk eSIM actions for corporate-owned Android Enterprise devices was removed.
The instructions now direct administrators to select **Remote actions** before choosing **Logout current user** from the device overview pane.
The instructions now direct administrators to select **Locate** and then **Lost mode (supervised only)** from the device overview action icons.
The documented steps now direct administrators to select Remote actions > Pause Config Refresh from the device overview pane.
The instructions now direct administrators to select Microsoft Defender > Run quick malware scan from the device overview action icons.
The instructions now direct administrators to select **Secure** > **Remote lock** from the device overview action icons.
The instructions now direct administrators to select **Secure** and then **Remove passcode** from the device overview action icons.
The instructions now direct administrators to select **Secure** > **Reset passcode** from the device overview action icons.
The restart procedure now instructs administrators to select **Remote actions** > **Restart** > **Yes** from the device overview pane.
The instructions now direct administrators to select Remote actions > Restore Managed Home Screen from the device overview pane.
The instructions now direct administrators to select **Secure** > **BitLocker key rotation** from the device overview action icons.
The action is now accessed through **Secure** > **Rotate FileVault recovery key** in the device overview pane.
The device overview instructions now direct admins to select **Secure** before choosing **Rotate Local admin password**.
The instructions now direct administrators to select Secure > Rotate Recovery Lock Passcode from the device overview action icons.
The documented path changed from selecting Shut down directly to selecting Remote actions > Shut down > Yes.
The instructions now direct administrators to select **Remote actions** before choosing **Suspend Managed Home Screen**.
The Company Portal help page now links to “Rename a device in Microsoft Intune” at a new documentation location.
The article now links to `/device-management/inventory-and-status/rename-device` instead of `/device-management/actions/rename`.
The documented steps now direct administrators to select Remove data > Wipe from the device overview action icons.
The page documenting the Rename device action, including supported platforms, role requirements, and admin-center steps, was deleted.
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 app-exclusion setting description now spells out “Managed Home Screen” instead of using the abbreviation “MHS” when referring to authentication.
During onboarding, the Intune, Microsoft Authenticator, and Company Portal apps are installed as required apps on dedicated devices, in addition to fully managed and corporate-owned work profile devices.
The documentation now states that failed macOS app installations are retried at the next agent check-in, with up to three retries while the app remains assigned.
The guide now states that app configuration policies support only MDM-managed apps and cannot configure DDM apps. The setup steps were also renumbered.
The documentation now warns that re-uploading an existing VPP token for DDM causes available app assignments to be lost. It recommends creating a new Apple Business token for DDM and using MDM for available assignments and apps requiring app configuration policies.
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 page now uses simpler wording for device actions and updates the Intune security policies link path.
Two references to “Monitor device encryption with Intune” now point to /intune/device-configuration/endpoint-security/monitor-encryption instead of /intune/device-management/monitor-encryption.
The endpoint security policies page now uses an updated link to the guidance for managing devices with endpoint security in Intune.
The documentation now links to the Admin tasks pane under the governance path instead of the device-management path.
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 iOS/iPadOS platform guide now links to the endpoint security devices page at a new URL; the link description is unchanged.
The macOS platform guide now links to the endpoint security devices page at its updated documentation path.
The article now points to the encryption report and instructs admins to select Secure > Rotate FileVault recovery key from the device overview, then confirm with Yes.
The instructions now direct administrators to select Secure > Rotate Recovery Lock Passcode, choose Yes, and note that Intune generates a new passcode.
The “Managed by” documentation now links to the endpoint security devices location for details by management type.
The procedure now instructs administrators to select **Collect data** instead of **Yes** to confirm the action.
The multi-admin approval documentation now links to the centralized Admin tasks pane under the governance path instead of the device management path.
The China endpoints documentation now lists `https://graph.chinacloudapi.cn` instead of `https://graph.chinacloudapi.us`.
The documented navigation now directs administrators to select a device and choose **Remote actions** > **Begin a remote assistance session**.
Windows Autopatch enhancements, rolling out Sept 1–Oct 15, 2026, offer improved control over Windows quality, .NET Framework, and quick machine recovery updates. Features include customizable automatic/manual approvals, deferral settings, update pausing, and detailed per-device reporting for better update management.
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 documented action and pane names changed from “Run remediation (preview)” to “Run remediation.”
The device management actions index updates its Rename entries to link to the bulk-rename-devices section of the device inventory and status documentation.
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 documentation now states that active devices collect inventory multiple times per day, while initial collection can take up to 24 hours because full synchronization runs once daily.
The Disk encryption documentation now uses the relative link `monitor-encryption` instead of `../../device-management/monitor-encryption`.
The option must be set to No and will soon be removed. The Sync with computers setting was deprecated by Apple in iOS 13 and is no longer included in enrollment policies.
A new overview describes the Devices area in the Intune admin center, including device details, actions, inventory, reports, tools, and related guidance.
The Windows platform guide now links to the endpoint security devices page at a new documentation path; the link description is unchanged.
The BitLocker documentation now uses updated links for the encryption report and Monitor disk encryption, and clarifies that recovery keys can be viewed and managed from the encryption report.
The Android platform guide now links to the endpoint security devices article at its updated documentation path.
The documentation now explains how to edit a managed device’s name, ownership, primary user, notes, and scope tags from the Properties tab.
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.
Starting in version 2609, the Catalog Synchronization and Inventoried Software Status sections, along with Asset Intelligence reports, are removed. The page instead provides deprecation information and links to the product lifecycle dashboard and Asset Intelligence client settings. Earlier procedures apply only to version 2603 and earlier.
The documentation now states that built-in Asset Intelligence reports are removed from Monitoring > Reporting > Reports in version 2609. References apply to version 2603 and earlier.
The documentation marks SQL Server 2016 and SQL Server 2016 Express as deprecated in version 2609. SQL Server editions earlier than SQL Server 2017 CU2 must be upgraded before installing or updating to 2609; the Visual C++ Redistributable on secondary sites must also be updated.
The documentation now specifies Microsoft ODBC Driver for SQL Server and links to minimum, validated, and blocking versions. Starting in version 2609, Configuration Manager automatically installs the Microsoft OLE DB Driver for SQL Server and no longer requires SQL Server Native Client; versions 2603 and earlier retain the previous Native Client behavior.
The documentation now requires ODBC Driver 18.6.2.1 or later for Configuration Manager 2609 and later, and SQL Server 2017 CU2 or later starting with 2609. Unsupported versions can block installation or upgrades; it also identifies version-specific incompatible ODBC releases and adds a non-blocking warning about automatic client approval.
The documentation states that version 2609 removes the Catalog Synchronization and Inventoried Software Status sections from the Asset Intelligence home page and removes Asset Intelligence reports from Monitoring > Reporting > Reports.
Starting with Configuration Manager version 2609, the TRUSTWORTHY database property is not required to load Microsoft-signed SQLCLR assemblies, including for databases using SQL Server Always On availability groups. Version 2603 and earlier still require TRUSTWORTHY to be enabled.
The index now includes Configuration Manager 2609 and links to KB 2377842. Entries for versions 2107 through 2211 were removed, and the page date was updated.
Starting with Configuration Manager version 2609, Windows Server 2012, Windows Server 2012 R2, and their Windows Storage Server editions will no longer be supported as client operating systems.
The page now lists version 2609 (5.00.9152.1000), released September 28, 2026, with support through March 28, 2028. Version 2503 is now shown as plain text.
The Configuration Manager version 2309 documentation now links to the prerequisite-checks page for minimum required versions, validated versions, and known blocking issues for the ODBC driver for SQL Server.
The documentation now states that all SQL Server versions currently supported by Configuration Manager support TLS 1.1 and TLS 1.2. Secondary site servers now require SQL Server 2017 Express with CU2 or later, replacing the previous SQL Server 2016 Express SP2 minimum.
The page date changed to September 22, 2026, and the “What’s new” link changed from version 2503 to version 2609.
The guidance now requires TRUSTWORTHY for Configuration Manager 2603 and earlier, but says it isn't needed and should be skipped for version 2609 and later when loading SQLCLR assemblies.
The documentation no longer lists Windows Server 2012 R2, Microsoft Hyper-V Server 2012, or Windows Server 2012. The page date was updated to September 21, 2026.
The documentation now lists SQL Server 2025 and removes SQL Server 2016, SQL Server 2014, and the SQL Server 2016 upgrade link.
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 documentation states that the deprecated `scepinstall.exe` installer will no longer be included with Configuration Manager starting in version 2609.
The documentation now states that Microsoft Defender Antivirus contextual file and folder exclusions can be specified in the policy setting or with the Set-CMAntimalwarePolicy cmdlet starting in version 2609.
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 documentation now lists Windows 11 version 26H2 (build 10.0.26300) with support indicators shown as ❌, ✅, and ✅.
The documentation now lists Windows 11 25H2 as supported with ConfigMgr 2503, 2509, and 2603, and adds ConfigMgr 2609 to the matrix.
The documentation date was updated, and the support table now lists ConfigMgr 2509, 2603, and 2609 instead of 2503, 2509, and 2603.
The documentation table now lists ConfigMgr 2509, 2603, and 2609 instead of 2503, 2509, and 2603. The page date was also updated.
The documentation now states that Configuration Manager supports data deduplication with distribution points on supported Windows Server versions, replacing the explicit “Windows Server 2012 or later” wording.
The Configuration Manager documentation now links to `integrate-windows-update-client-policies.md` instead of `integrate-windows-update-for-business-windows-10.md`.
The article’s guidance on integrating Windows Update client policies was revised. It continues to state that computers using Windows Update client policies or Windows Insiders aren’t evaluated in Windows servicing plans and must use Configuration Manager software updates with WSUS.
The 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`.
Starting with version 2609, the Asset Intelligence report category and its 67 reports will be removed. They apply to version 2603 and earlier.
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.
The documentation now links to the centralized Admin tasks pane under the governance path instead of the device-management path.
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.
Security Copilot is now included with Microsoft 365 E5/E7 plans, integrating agents across Defender, Entra, Intune, Purview, and its portal. No purchase or action is needed. Organizations get monthly Security Compute Units, developer tools, and can explore additional paid features or opt out by contacting support.
