The page now documents version 20260818.1, agent and server image digests, minor bug fixes, and package and security updates for the August 18, 2026 release.

The prerequisites now list RHEL 10.1 with Podman 5.8.2 as the default and explain that the ip_tables kernel module must be manually loaded before Tunnel installation.

Intune now documents the Windows 365 for Agents security baseline version 24H1, including default settings for Cloud PCs running agentic workloads across Windows 11, Microsoft Edge, and Microsoft Defender for Endpoint.

The security baselines overview now links to the Windows 365 for Agents security baseline, including its Version 24H1 settings reference.

The Configure baselines documentation now links to the Windows 365 for Agents security baseline settings reference.

The monitoring guidance now lists log collection status—completed, failed, or in progress—instead of an Incident ID. It also says Microsoft can use logs collected after reproducing an issue during verbose log collection for investigation.

The prerequisites page no longer lists `powerlift-frontdesk.acompli.net` as a Diagnostic Endpoint.

The documentation now explains that Yes disables and No enables catch-up scans because the settings are named “Disable catch-up...”. Full-scan catch-up is disabled when not configured, while quick-scan catch-up is enabled by default; the scan triggers after two missed scheduled scans are also specified.

The page metadata date changed from 08/02/2024 to 08/10/2026. No substantive documentation or product changes are shown.

The page’s metadata date changed from August 2, 2024, to August 10, 2026. No substantive content change is shown.

The Microsoft Tunnel MAM for Android page updates links for MAM certificate trust APIs, including the MAMCertTrustWebViewClient reference link.

The setup page removes the direct link to BlackBerry UES integration instructions and now tells administrators to sign in with Microsoft Entra and complete setup.

The prerequisites now list RHEL 9.8 with Podman 5.8.2 or later as the default and explain that the ip_tables kernel module must be loaded manually before Tunnel installation.

Updated Microsoft Intune documentation in intune/device-configuration/endpoint-security/firewall.md.

The page now states that the listed eSIM features are rolling out and might not yet be available to all tenants. The page date and authoring metadata were also updated.

The documentation adds capabilities including unattended Remote Help for physical Windows devices, DDM for Apple VPP apps, additional protected apps, and new Android and Apple settings catalog controls.

The archive now documents EPM support for AVD single-session VMs, a Lenovo Device Orchestration link, four protected apps, and additional Windows settings catalog policies for Edge, Chrome, Windows AI, Firewall, and other components.

The documentation now explains that eSIMs are preserved by default on specified Android Enterprise corporate-owned devices and can be removed during a single-device wipe using the new device view.

The page date changed from July 27 to August 21, 2026, and the section describing a planned Audit value for the Microsoft Defender Antivirus template for Linux was removed.

The documentation now states that a tenant can submit up to 1,000 Delete actions per day, cumulatively across individual actions, bulk actions, and Microsoft Graph requests. The limit also applies when Delete triggers Retire or Wipe.

The documentation now states that a tenant can submit up to 1,000 Retire actions per day, cumulative across individual, bulk, and Microsoft Graph API requests.

The documentation now states that individual, bulk, and Microsoft Graph Wipe requests share a cumulative tenant-wide daily limit of 500 actions.

The sync documentation now explains that selecting Sync triggers multiple workloads, including policy processing, app state updates, and scripts/remediations. Admins can monitor progress in the Device sync status tab. This behavior applies to iOS/iPadOS and Windows devices.

The sync documentation now says to turn on the “Preview new device view” toggle in the Intune admin center to see new device sync improvements. The “Compliance policy evaluation” item was also removed from the documented sync behavior.

The documentation adds Windows settings catalog entries for Windows App, custom Microsoft Store package removal, disabling Get Started, several OneDrive behaviors, and the Disable Model Context Protocol Visual Studio policy.

The documentation now lists Chrome, Edge, and Samsung browser as supported for web-based enrollment. The note about phone-call MFA potentially breaking enrollment and its workaround was removed.

The article now documents additional Android settings, including work profile inactivity, eSIM removal during wipes, screen power behavior, and separate device and work profile locks, with supported enrollment types, platform versions, defaults, and value requirements.

The documentation now lists Accessibility appearance for iOS/iPadOS 17 and later and Liquid Glass for iOS/iPadOS 27 and later.

The macOS setup documentation now lists the Liquid Glass pane as skippable for macOS 27.0 and later.

The documentation now directs administrators to the “Personal Devices on Android Management API” report under Devices > Monitor and clarifies that reporting is not shown in the policy’s device assignment status or the device configuration tab.

Intune will support macOS 15 and later after macOS Golden Gate 27 release this year. Existing devices on macOS 14.x or below remain enrolled but new enrollments on these versions won't be allowed. Organizations should identify and upgrade affected macOS devices in Intune before the change.

The licensing documentation now explains that eligible shared-device and no-user-affinity enrollment scenarios support device-targeted management through a device-only subscription. It also states that an unlicensed signed-in user doesn't prevent device-targeted policies, apps, or management actions from processing.

The macOS ADE guidance warns not to target profiles that enable PSSO registration during Setup Assistant to userless ADE devices, because this can cause unexpected enrollment behavior and loss of expected device affinity.

The guidance now links to the general Android and iOS store-app instructions without including direct CylancePROTECT Play Store or App Store URLs.

The documentation now states that enrollment time grouping is available for iOS/iPadOS and macOS, along with the new Apple enrollment policies experience.

The VPP token settings now include a Management type option: MDM (default) or DDM. DDM applies to app deployment and configuration on iOS/iPadOS 18 and later, and supports only Required or Uninstall assignments.

The reference now includes Ben for Intune, Calven, Heijmans, Notability, Notion, SDP - On Premises | Intune, and Superhuman Mail, with descriptions and app links.

Microsoft Intune will require iOS/iPadOS 18 or higher after Apple releases iOS/iPadOS 27 later this year. Organizations should check device compatibility and Intune reports to identify affected devices. Userless devices via Automated Device Enrollment have specific OS version requirements. Use Intune controls to manage OS versions.

The documentation now states that apps targeting Android Enterprise fully managed (COBO) and corporate-owned personally enabled (COPE) devices can use Available assignments for either user or device groups, alongside the existing Win32 exception.

The article now only directs administrators to the iOS app configuration policy guidance; the Sophos Intercept X for Mobile iOS reference link was removed.

The Android managed apps documentation now describes the Azure Information Protection mobile apps without the Google Play link.

The BlackBerry Intune integration page no longer includes the link to BlackBerry UES documentation.

The protected apps reference no longer includes the Klaxoon for Intune listing.

The Intune client and host service endpoint entry now includes 150.171.109.0/24 and 150.171.110.0/24.

The osVersion property is now documented as deprecated. New assignment filters can’t use it, while existing filters continue to work; operatingSystemVersion is the replacement.

The documentation now distinguishes Android unattended control, which requires a dedicated Intune-enrolled device, and adds Windows unattended remote sign-in for targeted physical corporate-owned devices. Both permissions must be explicitly assigned and scoped.

The endpoints documentation now states that Remote Sign-in for Remote Help on Windows requires Azure Virtual Desktop session host endpoints.

The sync behavior and Device sync status tab are documented as applying to Windows and iOS/iPadOS devices, rather than Windows only. The Preview new device view toggle remains required to see the described improvements.

The documentation now covers MAA enforcement for delegated actions and app-authenticated Microsoft Graph API calls, clarifies approver permissions and direct group membership, and documents per-policy enterprise application exclusions. Exclusions apply only to app-auth calls, allow up to 50 applications, require second-admin approval, and are audited.

The documentation now describes missing approval headers as returning HTTP 400, and pending approval as HTTP 412 with a Graph `BadRequest` code and `x-msft-approval-code` header. It also instructs callers to retain the original request details for resubmission.

The documentation now states that Sync from Windows Settings or the Intune admin center initiates both MDM and IME check-ins, including policy, app, script, and remediation processing. Sync progress can be viewed in the Device sync status tab.

The documentation now notes that registry key inventory uses existing Device Inventory permissions and may expose sensitive device configuration information.

The Remediations link now includes the `.md` file extension in its relative path.

The government service page now includes Remediations with a value of “n/a” in its table.

The documentation adds activation and removal of eSIM plans on supported Android Enterprise corporate-owned devices, including supported Android versions, activation-code and ICCID requirements, device-view steps, and required permissions.

The documentation now lists tenant-wide daily limits of 500 Wipe actions and 1,000 each for Retire and Delete. Counts are cumulative across individual, bulk, and Microsoft Graph submissions.

The permissions table now lists Android Enterprise’s “Manage zero touch enrollment” permission for managing or changing the Google Zero-Touch Enrollment portal connection.

A new article explains how to trigger and cancel remote enhanced log collection on supervised macOS 27+, iOS 27+, and iPadOS 27+ devices. Logs are sent directly to Apple for support analysis.

Intune now documents the Apple DDM App Settings configuration for supervised iOS/iPadOS 27+ and macOS 27+ devices, including allowed or denied apps, binaries, and managed-app allowances.

The documentation for collecting device properties now states that registry key inventory uses existing Device Inventory permissions and may expose sensitive device configuration information. It identifies this as an accepted risk and calls for reviewing security and privacy implications.

The PKCS profiles documentation now states that device configuration profiles containing PKCS certificate profiles aren't supported on Microsoft Teams devices running AOSP. The page date was also updated.

The new Intune single device page, offering a consolidated device management view, will become the default in the September (2609) release, replacing the legacy page. All management features remain, but admins should update documentation and familiarize themselves with the new interface beforehand.

Updated Microsoft Intune documentation in intune/device-configuration/monitor-device-profile.md.

The device details documentation now covers ICCID, EID, phone number, carrier, activation state, and SIM origin for supported Android Enterprise corporate-owned devices, including Android version requirements.

The documentation now lists new blob storage URLs for each region and directs administrators to Tenant Status in endpoint.microsoft.com to identify their tenant’s geo and data center.

Windows Autopilot device preparation now supports associating physical Windows 11 devices with an organization before enrollment. Associated devices are marked corporate-owned and can receive device-targeted policies and naming.

The device association entry was removed from the Windows Autopilot What's New page and moved to Device preparation What's New. The page date was also changed to June 18, 2026.

The documentation describes TPM-backed association that writes tenant affinity to UEFI before enrollment, enabling device-targeted policies, device naming, OOBE customization, corporate marking, and stronger onboarding security.

The new article explains how to remove pre-associated devices from Intune and how to clear Device Link UEFI variables before deleting associated devices from Intune.

The page specifies Windows 11, physical-device, TPM 2.0, networking, licensing, and Intune RBAC requirements, including custom-role setup steps.

A new Step 7 guide explains associating devices for user-driven Microsoft Entra join, including exporting device information, importing it into Intune, and reviewing associations. Association is an optional alternative to corporate identifiers.

The new article documents device resets, local association removal, CSV updates, Autopilot registration, stale records, and decommissioning. It notes that associations persist through resets and that stale records are automatically deleted after 360 days.

Step 7 now includes device association as an alternative to corporate identifiers. The documentation explains associated-device OOBE settings, deployment precedence, and device- versus user-based policy assignment.

A new FAQ explains DeviceLink CSV timestamp changes, exporting device information after OOBE, corporate identifier requirements, OEM and partner support, and virtual machine limitations.

The tutorial now documents support for up to 25 essential applications, up from 10, and adds device association as an alternative to corporate identifiers. Associated devices can use settings such as OOBE customization and device naming.

Step 7 now identifies corporate identifiers as one option and links to optional device association as another. Associated devices are automatically treated as corporate-owned, and enrollment links were updated.

Windows Autopilot device preparation now supports associating physical Windows 11 devices with an organization before enrollment. Associated devices are automatically marked corporate-owned and can receive device-targeted policies and naming.

The tutorial now lists device association as an alternative to adding a Windows corporate identifier and clarifies the steps for deploying apps and PowerShell scripts.

The documentation explains that association state determines whether the Windows Autopilot profile or device association takes precedence. Associated physical Windows 11 devices are marked corporate-owned and can receive device-targeted policies and additional OOBE customizations.

The comparison now documents that device preparation devices can be associated with a tenant before enrollment, while Windows Autopilot devices can be registered. It also updates the explanation of deployment selection for Autopilot-registered devices.

Step 7 now offers two options: add a Windows corporate identifier or associate devices. The document date was also updated.

Step 7 now offers two paths: add a Windows corporate identifier or associate devices. The page’s update date was also refreshed.

Step 7 now presents two options: adding a Windows corporate identifier or associating devices. The documentation date was also updated.

Step 7 now documents two options: adding a Windows corporate identifier or using Associate devices. The page date was also updated.

The documentation date and “Date added” value changed from August 20, 2026, to August 27, 2026.

The page title capitalization was updated, and its description now states that administrators can gather hardware hashes and import, edit, and delete device records in the Intune admin center.

The three metadata tag lines on the Add devices page were reverted to their previous formatting.

The documented endpoint list changed from lgmsape*.blob.core.windows.net destinations to ams* lmsas.blob.core.windows.net destinations.

The page’s ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager.

The page’s ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager while the SDK subservice association remains.

The page’s `ms.service` 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 `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

The page’s ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager; ms.subservice remains sdk.

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`, while it remains paired with `ms.subservice: sdk`.

The page metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for `ms.service`.

The page metadata now uses `configuration-manager` instead of `microsoft-endpoint-configuration-manager` for `ms.service`.

The page now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while `ms.subservice` remains `sdk`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

The reference now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager` alongside `ms.subservice: sdk`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation now pairs `ms.subservice: sdk` with `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for `ms.service`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`, while retaining `ms.subservice: sdk`.

The `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while remaining paired with `ms.subservice: sdk`.

The page metadata changed ms.service from microsoft-endpoint-configuration-manager to configuration-manager.

The page's `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining `ms.subservice: sdk`.

The page’s ms.service metadata changed from microsoft-endpoint-configuration-manager to configuration-manager while retaining ms.subservice=sdk.

The documentation’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining `ms.subservice: sdk`.

The page now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`, while retaining the SDK subservice classification.

The documentation metadata changed its ms.service value from microsoft-endpoint-configuration-manager to configuration-manager.

The page now uses `ms.service: configuration-manager` with `ms.subservice: sdk`, replacing `microsoft-endpoint-configuration-manager`.

The documentation metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager` for the SDK content.

The documentation changes the ms.service value from microsoft-endpoint-configuration-manager to configuration-manager.

The page metadata now uses `ms.subservice: mdm` with `ms.service: configuration-manager` instead of the previous values.

The documentation metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page metadata now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.

The service metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining the `sdk` subservice.

The page's `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while `ms.subservice` remains `sdk`.

The documentation service tag changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while `ms.subservice` remains `sdk`.

The documentation metadata changes `ms.service` from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining the SDK subservice classification.

The page metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`; its `ms.subservice: sdk` remains unchanged.

The documentation now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while the SDK subservice association remains.

The page metadata changes `ms.service` from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while the `sdk` subservice remains paired with it.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while the SDK subservice association remains.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

The page now pairs ms.subservice=sdk with ms.service=configuration-manager instead of microsoft-endpoint-configuration-manager.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`, while the SDK subservice remains unchanged.

The documentation service label changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining the SDK subservice.

The page’s ms.service metadata changed from microsoft-endpoint-configuration-manager to configuration-manager.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for `ms.service`.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while the `sdk` subservice remains associated.

The documentation now pairs `ms.subservice: sdk` with `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The documentation’s ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while remaining paired with `ms.subservice: sdk`.

The documentation service metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager.

The page metadata changed ms.service from microsoft-endpoint-configuration-manager to configuration-manager while retaining ms.subservice as sdk.

The documentation metadata changes `ms.service` from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining the SDK subservice.

The documentation metadata changed the service classification from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`; `ms.subservice: sdk` remains unchanged.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining the SDK subservice classification.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining the SDK subservice.

The page’s ms.service metadata changed from microsoft-endpoint-configuration-manager to configuration-manager.

The page’s ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager; ms.subservice remains sdk.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`, paired with the SDK subservice.

The page changes the ms.service metadata from microsoft-endpoint-configuration-manager to configuration-manager while retaining ms.subservice=sdk.

The page now uses `ms.service: configuration-manager` with `ms.subservice: sdk`, replacing `microsoft-endpoint-configuration-manager`.

The page's ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager.

The documentation's `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

The `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; the `ms.subservice` value remains `sdk`.

The page metadata changed from `ms.service: microsoft-endpoint-configuration-manager` to `ms.service: configuration-manager`.

The documentation changes the `ms.service` metadata value from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining `ms.subservice: sdk`.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager` while retaining the `sdk` subservice.

The page metadata changes `ms.service` from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining `ms.subservice: sdk`.

The page’s ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager; ms.subservice remains sdk.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.

The documentation changes the `ms.service` metadata value from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining the `sdk` subservice.

The article metadata changed `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, while remaining paired with ms.subservice=sdk.

The page's ms.service metadata changed from microsoft-endpoint-configuration-manager to configuration-manager.

The page metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for `ms.service`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

The page’s ms.service metadata changed from microsoft-endpoint-configuration-manager to configuration-manager.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining the `sdk` subservice pairing.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while it remains associated with the `sdk` subservice.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while remaining paired with `ms.subservice: sdk`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

The documentation now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`, while retaining the SDK subservice association.

The page’s ms.service metadata changed from microsoft-endpoint-configuration-manager to configuration-manager, while ms.subservice remains sdk.

The CCM_SoftwareBase client WMI class page changes its ms.service metadata from microsoft-endpoint-configuration-manager to configuration-manager while retaining the sdk subservice.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The documentation metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for `SMS_Package.CheckDuplicateShareName`.

The page metadata changed its service value from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation metadata changed the service value from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`, while retaining `ms.subservice: sdk`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for `ms.subservice: sdk`.

The page metadata changed its service value from `microsoft-endpoint-configuration-manager` to `configuration-manager`; the SDK subservice remains unchanged.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`, while retaining `ms.subservice: sdk`.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

The documentation page now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.

The `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while the `ms.subservice` value remains `sdk`.

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 value changed from microsoft-endpoint-configuration-manager to configuration-manager; ms.subservice remains sdk.

The documentation now pairs the SDK subservice 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`.

The page now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`, paired with `ms.subservice: sdk`.

The article’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page 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`; `ms.subservice` remains `sdk`.

The page metadata changes `ms.service` from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining the SDK subservice classification.

The page metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for the `sdk` subservice.

The documentation now pairs `ms.subservice=sdk` 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`; `ms.subservice` remains `sdk`.

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` for the `sdk` subservice.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page metadata 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's ms.service metadata changed from microsoft-endpoint-configuration-manager to configuration-manager.

The page metadata now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.

The page’s ms.service metadata changed from microsoft-endpoint-configuration-manager to configuration-manager.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

The documentation now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page now uses `ms.service: configuration-manager` with `ms.subservice: sdk`, replacing `microsoft-endpoint-configuration-manager`.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining the SDK subservice classification.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while `ms.subservice` remains `sdk`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page metadata changes `ms.service` from `microsoft-endpoint-configuration-manager` to `configuration-manager`; the SDK subservice association remains.

The reference page’s ms.service metadata changed from microsoft-endpoint-configuration-manager to configuration-manager.

The documentation now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The article’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page metadata changed its `ms.service` value from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The `ms.service` value paired with `ms.subservice: sdk` changed 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 now uses `configuration-manager` instead of `microsoft-endpoint-configuration-manager` for the `ms.service` value.

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 documentation now pairs the SDK subservice 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`, while remaining paired with `ms.subservice: sdk`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for `ms.service`.

The documentation now uses `configuration-manager` instead of `microsoft-endpoint-configuration-manager` for the `ms.service` metadata value.

The page metadata now uses ms.service = configuration-manager with ms.subservice = sdk instead of microsoft-endpoint-configuration-manager.

The SDK reference now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

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`.

The page metadata now uses ms.service: configuration-manager instead of microsoft-endpoint-configuration-manager.

The documentation metadata changes `ms.service` from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The reference page’s `ms.service` value 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 SDK subservice remains unchanged.

The page’s service metadata changed from `microsoft-endpoint-configuration-manager` to `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` for the SDK service classification.

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 now pairs the SDK subservice 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`, while `ms.subservice` remains `sdk`.

The page metadata now uses `configuration-manager` instead of `microsoft-endpoint-configuration-manager` for `ms.service`.

The Microsoft service tag changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; the SDK subservice tag remains unchanged.

The documentation service identifier changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation 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`, while the `sdk` subservice remains unchanged.

The page metadata changed its ms.service value from microsoft-endpoint-configuration-manager to configuration-manager.

The documentation now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.

The page metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for `ms.service`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; the `sdk` subservice remains unchanged.

The page metadata changes ms.service 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 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 now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page’s service metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; the SDK subservice remains paired with it.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The documentation now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` while remaining paired with `ms.subservice: sdk`.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation metadata changes `ms.service` from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining the SDK subservice.

The documentation now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while remaining paired with `ms.subservice: sdk`.

The page metadata changes ms.service from microsoft-endpoint-configuration-manager to configuration-manager; ms.subservice remains sdk.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; the `ms.subservice` remains `sdk`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while the `sdk` subservice remains paired with it.

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 documentation now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page’s ms.service metadata changed from microsoft-endpoint-configuration-manager to configuration-manager.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page’s service metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The article now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`, paired with the `sdk` subservice.

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`, while retaining the SDK subservice.

The page’s ms.service metadata changed from microsoft-endpoint-configuration-manager to configuration-manager while retaining ms.subservice: sdk.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

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`; `ms.subservice` remains `sdk`.

The page metadata now pairs `ms.subservice: sdk` with `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The article’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The article’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

The article’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while `ms.subservice` remains `sdk`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while `ms.subservice` remains `sdk`.

The article’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

The page metadata changes its 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`; `ms.subservice` remains `sdk`.

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 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’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`.

The article’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`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while the `sdk` subservice remains unchanged.

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`, while retaining the `sdk` subservice.

The page metadata now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining the SDK subservice.

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` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

The documentation now uses `ms.service: configuration-manager` with `ms.subservice: sdk`, replacing `microsoft-endpoint-configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while `ms.subservice` remains `sdk`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

The page metadata changed ms.service from microsoft-endpoint-configuration-manager to configuration-manager while retaining ms.subservice as sdk.

The page’s service metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; the `sdk` subservice remains.

The documentation metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for the SDK service.

The page now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`; the SDK subservice remains unchanged.

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`; `ms.subservice` remains `sdk`.

The page’s ms.service metadata changed from microsoft-endpoint-configuration-manager to configuration-manager; ms.subservice remains sdk.

The page’s ms.service metadata changed from microsoft-endpoint-configuration-manager to configuration-manager.

The 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`; `ms.subservice` remains `sdk`.

The `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager` for the SDK metadata.

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’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining `ms.subservice: sdk`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

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.

The page’s service metadata changed from “microsoft-endpoint-configuration-manager” to “configuration-manager.”

The documentation metadata changes `ms.service` from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The document’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page metadata changes the service value from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.

The page’s ms.service metadata changed from microsoft-endpoint-configuration-manager to configuration-manager.

The ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager; ms.subservice remains sdk.

The documentation metadata changed its service value from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while the SDK subservice remains associated.

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.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining `ms.subservice: sdk`.

The documentation now uses `configuration-manager` instead of `microsoft-endpoint-configuration-manager` for the `ms.service` metadata value.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while the `sdk` subservice pairing remains.

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.

The page now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The documentation now uses `ms.service: configuration-manager` with `ms.subservice: sdk`, replacing `microsoft-endpoint-configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining `ms.subservice: sdk`.

The page metadata changed its `ms.service` value from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s ms.service metadata changed from microsoft-endpoint-configuration-manager to configuration-manager.

The documentation now pairs the SDK subservice with `configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The documentation metadata changed its ms.service value from microsoft-endpoint-configuration-manager to configuration-manager.

The documentation metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The documentation metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The ReleaseAllLocks method page now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`, while retaining the SDK subservice classification.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`, while retaining the SDK subservice.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`; the SDK subservice pairing remains.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining `ms.subservice: sdk`.

The page metadata changes the service value from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page metadata changes the service value from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation now uses `configuration-manager` instead of `microsoft-endpoint-configuration-manager` for the `ms.service` value.

The documentation now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The documentation now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager` for the SDK reference page.

The page’s ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager, paired with the sdk subservice.

The documentation metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page metadata changed its ms.service value from microsoft-endpoint-configuration-manager to configuration-manager.

The page’s ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager; ms.subservice remains sdk.

The page metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for `ms.service`; `ms.subservice` remains `sdk`.

The page's ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`, paired with the existing SDK subservice classification.

The `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while the `sdk` subservice pairing remains.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

The `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for the `ResolveConflict` method reference.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining `ms.subservice: sdk`.

The page metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for `ms.service`.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page now uses `ms.service: configuration-manager` with `ms.subservice: sdk`, replacing `microsoft-endpoint-configuration-manager`.

The page’s service metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation service metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The documentation now pairs the SDK subservice with `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The documentation’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s service label changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation metadata changes ms.service from microsoft-endpoint-configuration-manager to configuration-manager while retaining the SDK classification.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; the `ms.subservice` value remains `sdk`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; the `sdk` subservice remains paired with it.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

The documented ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager while ms.subservice remains sdk.

The SetSourceSite method page now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`, while retaining the SDK subservice pairing.

The page’s service metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining the SDK subservice.

The reference now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; the `sdk` subservice remains unchanged.

The documentation metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for `ms.service`.

The page now uses `ms.service: configuration-manager` with `ms.subservice: sdk`, replacing `microsoft-endpoint-configuration-manager`.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The documentation now identifies the service as `configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`, while retaining the SDK subservice classification.

The page 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`; `ms.subservice` remains `sdk`.

The article’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation changes the `ms.service` value from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining the SDK subservice.

The documentation now uses ms.service: configuration-manager with ms.subservice: sdk instead of microsoft-endpoint-configuration-manager.

The documentation now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The documentation metadata changed its ms.service value from microsoft-endpoint-configuration-manager to configuration-manager.

The article’s 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 ms.subservice remains sdk.

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 now uses `ms.service: configuration-manager` with `ms.subservice: sdk`, replacing `microsoft-endpoint-configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The documentation now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page’s ms.service metadata changed from microsoft-endpoint-configuration-manager to configuration-manager.

The `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` when paired with `ms.subservice: sdk`.

The document metadata changed ms.service from microsoft-endpoint-configuration-manager to configuration-manager while retaining ms.subservice as sdk.

The page now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager` for the SDK service classification.

The documentation changes the ms.service value from microsoft-endpoint-configuration-manager to configuration-manager while retaining the sdk subservice pairing.

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 ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager while ms.subservice remains sdk.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The documentation now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page metadata changed its ms.service value from microsoft-endpoint-configuration-manager to configuration-manager; ms.subservice remains sdk.

The documentation 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 now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`; `ms.subservice: sdk` remains unchanged.

The documentation now pairs `ms.subservice: sdk` with `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The documentation now uses `ms.service: configuration-manager` with `ms.subservice: sdk`, replacing `microsoft-endpoint-configuration-manager`.

The page metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for `ms.service`.

The documentation now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.

The documentation now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.

The documentation now uses `configuration-manager` instead of `microsoft-endpoint-configuration-manager` for the `sdk` service classification.

The page’s ms.service metadata changed from microsoft-endpoint-configuration-manager to configuration-manager.

The page metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for `ms.service`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, paired with the existing `ms.subservice: sdk` value.

The documentation now pairs `ms.subservice = sdk` with `ms.service = configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`, while retaining `ms.subservice: sdk`.

The page’s ms.service metadata changed from microsoft-endpoint-configuration-manager to configuration-manager.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `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 documentation changes the ms.service value from microsoft-endpoint-configuration-manager to configuration-manager.

The documentation now pairs ms.subservice=sdk with ms.service=configuration-manager instead of microsoft-endpoint-configuration-manager.

The documentation now pairs ms.subservice=sdk 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 page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` while remaining paired with `ms.subservice = sdk`.

The page now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`, while retaining `ms.subservice: sdk`.

The documentation changes the ms.service value from microsoft-endpoint-configuration-manager to configuration-manager while retaining ms.subservice=sdk.

The page changed its ms.service value from microsoft-endpoint-configuration-manager to configuration-manager, while retaining ms.subservice=sdk.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page’s ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager, while ms.subservice remains sdk.

The page now pairs ms.subservice=sdk with ms.service=configuration-manager instead of microsoft-endpoint-configuration-manager.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for `ms.subservice: sdk`.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for the SDK metadata pairing.

The page now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager` for the SDK subservice.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation metadata changed its service value from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page metadata now pairs the SDK subservice with `configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page’s ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager; the SDK subservice association remains.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

The page’s ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager; ms.subservice remains sdk.

The documentation metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The documentation metadata now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.

The page’s ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager.

The page’s ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager while remaining paired with ms.subservice=sdk.

The documentation now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager` when paired with `ms.subservice: sdk`.

The documentation now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.

The page now uses ms.service: configuration-manager with ms.subservice: sdk, replacing microsoft-endpoint-configuration-manager.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

The documentation now pairs the SDK subservice 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; ms.subservice remains sdk.

The documented ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager.

The page’s ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager; ms.subservice remains sdk.

The documentation changes the ms.service metadata value from microsoft-endpoint-configuration-manager to configuration-manager.

The documentation now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager` while retaining the SDK subservice association.

The `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`, while `ms.subservice` remains `sdk`.

The page metadata changes ms.service from microsoft-endpoint-configuration-manager to configuration-manager.

The documentation changes the `ms.service` value from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining `ms.subservice=sdk`.

The page’s service metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; the `sdk` subservice pairing remains.

The documentation changes the `ms.service` value from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining the SDK subservice pairing.

The page metadata now pairs ms.subservice=sdk 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 page’s service metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation changes the ms.service value from microsoft-endpoint-configuration-manager to configuration-manager while retaining the sdk subservice pairing.

The page now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`, while retaining `ms.subservice: sdk`.

The page’s ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager; ms.subservice remains sdk.

The page’s ms.service metadata changed from microsoft-endpoint-configuration-manager to configuration-manager.

The documentation metadata changed `ms.service` from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining `ms.subservice: sdk`.

The documentation tag changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining the `sdk` subservice.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while remaining paired with `ms.subservice: sdk`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while the `sdk` subservice pairing remains.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation changes the ms.service value from microsoft-endpoint-configuration-manager to configuration-manager.

The `ms.service` value paired with `ms.subservice: sdk` changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager` for the SDK classification.

The documentation metadata changed its ms.service value from microsoft-endpoint-configuration-manager to configuration-manager; ms.subservice remains sdk.

The documentation now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager` when paired with `ms.subservice: sdk`.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager` while retaining the SDK subservice.

The page’s ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager.

The documentation changes the `ms.service` value from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while `ms.subservice` remains `sdk`.

The documentation now pairs the SDK subservice with `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 documentation’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining the `sdk` subservice.

The `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`; its `ms.subservice` remains `sdk`.

The documentation’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while `ms.subservice` remains `sdk`.

The documentation now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.

The documentation metadata now pairs `ms.subservice: sdk` with `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The documentation metadata changed from `ms.service: microsoft-endpoint-configuration-manager` to `ms.service: configuration-manager` while retaining the SDK subservice.

The service label changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page metadata changed its ms.service value from microsoft-endpoint-configuration-manager to configuration-manager.

The page metadata changed ms.service from microsoft-endpoint-configuration-manager to configuration-manager.

The page now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`, paired with `ms.subservice: sdk`.

The documentation metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`, while retaining the SDK subservice classification.

The ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager while remaining paired with ms.subservice = sdk.

The documentation now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`; `ms.subservice: sdk` remains unchanged.

The page metadata changes `ms.service` from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation changes the `ms.service` metadata from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining the `sdk` subservice.

The `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for the `SMS_EULACONTENT` server WMI class reference.

The article’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, paired with `ms.subservice=sdk`.

The `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation changes the ms.service value from microsoft-endpoint-configuration-manager to configuration-manager while retaining ms.subservice as sdk.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The documentation now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while the `ms.subservice=sdk` pairing remains.

The page’s ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager.

The documentation changes the ms.service value from microsoft-endpoint-configuration-manager to configuration-manager while retaining ms.subservice=sdk.

The ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager for the SDK documentation classification.

The page now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager` for the SDK classification.

The page changed its ms.service value from microsoft-endpoint-configuration-manager to configuration-manager while retaining ms.subservice as sdk.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while its SDK subservice remains unchanged.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while `ms.subservice` remains `sdk`.

The page now uses ms.service: configuration-manager with ms.subservice: sdk instead of microsoft-endpoint-configuration-manager.

The page’s ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager; ms.subservice remains sdk.

The page metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for `ms.service`.

The page’s service metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for the SDK classification.

The page now pairs ms.subservice: sdk 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`, while retaining the SDK subservice classification.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while `ms.subservice` remains `sdk`.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while the `sdk` subservice remains unchanged.

The page metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for `ms.service`.

The page’s ms.service metadata changed from microsoft-endpoint-configuration-manager to configuration-manager.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while remaining paired with the SDK subservice.

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`; `ms.subservice` remains `sdk`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The WMI class documentation changes the `ms.service` value 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` for the SDK classification.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page now pairs ms.subservice=sdk with 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`, paired with the existing SDK subservice classification.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

The page’s ms.service metadata changed from microsoft-endpoint-configuration-manager to configuration-manager.

The documentation now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager` for the SDK service metadata.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s metadata now pairs ms.subservice=sdk 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 page now uses `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 `sdk` subservice.

The documentation now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

The documentation now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager` while retaining the `sdk` subservice.

The documentation now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager` while retaining the SDK subservice classification.

The documentation metadata changed ms.service from microsoft-endpoint-configuration-manager to configuration-manager, while retaining ms.subservice as sdk.

The page’s ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager, while the sdk subservice association remains.

The documentation metadata now uses `ms.service: configuration-manager` with `ms.subservice: sdk`, replacing `microsoft-endpoint-configuration-manager`.

The page now pairs `ms.subservice: sdk` with `ms.service: configuration-manager` instead of `microsoft-endpoint-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 documentation metadata now uses `configuration-manager` instead of `microsoft-endpoint-configuration-manager` for the service classification.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

The documentation now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for `ms.service`.

The documentation’s service tag changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining the `sdk` subservice tag.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while `ms.subservice` remains `sdk`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while its `sdk` subservice association remains.

The documentation now uses `ms.service: configuration-manager` with the SDK subservice metadata.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

The documentation metadata changed `ms.service` from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining the `sdk` subservice.

The documentation now pairs ms.subservice=sdk with ms.service=configuration-manager instead of microsoft-endpoint-configuration-manager.

The documentation 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 documentation changes `ms.service` from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining `ms.subservice: sdk`.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while `ms.subservice` remains `sdk`.

The article’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 document’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

The documentation now pairs ms.subservice=sdk with ms.service=configuration-manager instead of microsoft-endpoint-configuration-manager.

The documented pairing changes ms.service from microsoft-endpoint-configuration-manager to configuration-manager while retaining ms.subservice=sdk.

The ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation metadata changes `ms.service` from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining the SDK subservice classification.

The documentation's ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager.

The page now uses `ms.service: configuration-manager` with the SDK subservice instead of `microsoft-endpoint-configuration-manager`.

The documentation now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.

The documented ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager while retaining ms.subservice: sdk.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while remaining paired with `ms.subservice: sdk`.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The documentation 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 documentation changes the `ms.service` metadata value from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining the `sdk` subservice.

The page metadata now pairs ms.subservice=sdk 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 page's `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining the SDK subservice pairing.

The documentation changes the `ms.service` value from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

The documentation metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for `ms.service`, while retaining `ms.subservice: sdk`.

The `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

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 now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page changes the ms.service value from microsoft-endpoint-configuration-manager to configuration-manager; ms.subservice remains sdk.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation replaces `ms.service: microsoft-endpoint-configuration-manager` with `ms.service: configuration-manager` for the SDK subservice.

The documentation metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The documentation metadata changes `ms.service` from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining `ms.subservice: sdk`.

The page’s ms.service metadata changed from microsoft-endpoint-configuration-manager to configuration-manager.

The documentation now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The `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 now uses `configuration-manager` for `ms.service` instead of `microsoft-endpoint-configuration-manager`, paired with `ms.subservice: sdk`.

The documentation now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The documentation now pairs the sdk subservice with ms.service: configuration-manager instead of microsoft-endpoint-configuration-manager.

The ms.service value paired with ms.subservice=sdk changed from microsoft-endpoint-configuration-manager to configuration-manager.

The documentation’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining the `sdk` subservice.

The documentation metadata now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.

The article’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while `ms.subservice` remains `sdk`.

The page now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.

The ms.service value paired with ms.subservice = sdk changed from microsoft-endpoint-configuration-manager to configuration-manager.

The documentation changes the ms.service value from microsoft-endpoint-configuration-manager to configuration-manager while retaining ms.subservice=sdk.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` while remaining paired with `ms.subservice: sdk`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page 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 reference 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; ms.subservice remains sdk.

The documentation now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager` for the SDK subservice.

The documentation metadata changed its service value from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining the SDK subservice.

The documentation metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager` while retaining the SDK subservice.

The reference 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`.

The documentation metadata changes `ms.service` from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining `ms.subservice: sdk`.

The `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for the `SMS_SoftwareDistributionAgentConfig` WMI class page.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The documentation metadata changed its ms.service value from microsoft-endpoint-configuration-manager to 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; ms.subservice remains sdk.

The documentation metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for `ms.subservice: sdk`.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The documentation metadata now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.

The documentation metadata changes ms.service from microsoft-endpoint-configuration-manager to configuration-manager while retaining the sdk subservice.

The ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager; ms.subservice remains sdk.

The page’s service metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for the SDK subservice.

The documentation now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The documented ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager.

The documentation now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The service value paired with `ms.subservice = sdk` changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager.

The page’s ms.service metadata changed from microsoft-endpoint-configuration-manager to configuration-manager.

The documented ms.service value paired with ms.subservice = sdk changed from microsoft-endpoint-configuration-manager to configuration-manager.

The `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining the `sdk` subservice.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for the `sdk` subservice.

The page’s ms.service metadata changed from microsoft-endpoint-configuration-manager to configuration-manager.

The article’s ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager, paired with ms.subservice = sdk.

The WMI class documentation now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.

The service metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for the SDK classification.

The documentation metadata changed `ms.service` from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining `ms.subservice: sdk`.

The documentation metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for `ms.service`.

The documentation changes the `ms.service` metadata value from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining the `sdk` subservice pairing.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for the SDK subservice.

The page now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`, paired with the existing `sdk` subservice.

The documented `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation's `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining the `sdk` subservice.

The page now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager` while retaining the SDK subservice classification.

The documentation metadata changed its ms.service value from microsoft-endpoint-configuration-manager to configuration-manager.

The page metadata changes `ms.service` from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining `ms.subservice: sdk`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

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` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for the `ms.subservice: sdk` pairing.

The page’s ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager; ms.subservice remains sdk.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s service metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining the SDK subservice.

The documentation service label changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation now uses `ms.service: configuration-manager` with `ms.subservice: sdk`, replacing `microsoft-endpoint-configuration-manager`.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, paired with the existing `sdk` subservice.

The page’s `ms.service` value 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 documentation changed its `ms.service` value from `microsoft-endpoint-configuration-manager` to `configuration-manager`; the `ms.subservice` value remains `sdk`.

The page metadata now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

The page’s ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while the `ms.subservice` remains `sdk`.

The documentation now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while remaining paired with `ms.subservice: sdk`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining `ms.subservice: sdk`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while the `sdk` subservice remains paired with it.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page’s service value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining the `sdk` subservice.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while remaining paired with `ms.subservice: sdk`.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The documentation now pairs the SDK subservice with `configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

The page metadata changed ms.service from microsoft-endpoint-configuration-manager to configuration-manager while retaining ms.subservice as sdk.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, paired with `ms.subservice: sdk`.

The page metadata changed its ms.service value from microsoft-endpoint-configuration-manager to configuration-manager.

The `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; the `ms.subservice: sdk` pairing remains.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while the `sdk` subservice association remains.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for this WMI class documentation.

The page now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`, while retaining the SDK subservice designation.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`, while retaining the SDK subservice classification.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining the SDK subservice classification.

The page's `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.

The page's ms.service metadata changed from microsoft-endpoint-configuration-manager to configuration-manager.

The documentation metadata changed its service value from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining the `sdk` subservice.

The page now pairs ms.subservice=sdk 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, while the sdk subservice remains paired with it.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s ms.service metadata changed from microsoft-endpoint-configuration-manager to configuration-manager.

The documentation metadata changed its ms.service value from microsoft-endpoint-configuration-manager to configuration-manager; ms.subservice remains sdk.

The `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for the SDK-tagged page.

The documentation changes the ms.service value from microsoft-endpoint-configuration-manager to configuration-manager.

The page’s ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager.

The `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining `ms.subservice: sdk`.

The reference now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The documentation now pairs ms.subservice=sdk with ms.service=configuration-manager instead of microsoft-endpoint-configuration-manager.

The reference now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation changes the `ms.service` value from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining the `sdk` subservice.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s service metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; the SDK subservice pairing remains.

The page now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager` with the SDK subservice.

The documentation now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while remaining paired with the SDK subservice.

The page’s service metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while the SDK subservice association remains.

The ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager while retaining the sdk subservice pairing.

The documentation’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation changed its `ms.service` metadata from `microsoft-endpoint-configuration-manager` to `configuration-manager`; the `ms.subservice` value remains `sdk`.

The documentation changed its ms.service value from microsoft-endpoint-configuration-manager to configuration-manager.

The page’s ms.service metadata changed from microsoft-endpoint-configuration-manager to configuration-manager while remaining paired with ms.subservice=sdk.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

The documentation changes the `ms.service` metadata value from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining the `sdk` subservice.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation metadata changes the ms.service value from microsoft-endpoint-configuration-manager to configuration-manager while retaining the SDK subservice association.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining the `sdk` subservice.

The documentation’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.

The documentation now uses `configuration-manager` instead of `microsoft-endpoint-configuration-manager` for `ms.service`, paired with the SDK subservice.

The documentation now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.

The page’s ms.service metadata changed from microsoft-endpoint-configuration-manager to configuration-manager.

The documentation now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` while paired with `ms.subservice: sdk`.

The documentation now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining `ms.subservice: sdk`.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

The page now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`, while retaining the SDK subservice association.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The reference now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The document's `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s service metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The title capitalization was standardized, and the description now highlights installing apps, software updates, and Windows upgrades, plus the required Software Center setting.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The deprecated functions page changes its service metadata from `microsoft-endpoint-configuration-manager` to `configuration-manager` for the SDK subservice.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation replaces `ms.service: microsoft-endpoint-configuration-manager` with `ms.service: configuration-manager`.

The article’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`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while the SDK subservice label remains.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page metadata now uses `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’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 article’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `ms.subservice` remains `sdk`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The documentation metadata changed ms.service from microsoft-endpoint-configuration-manager to configuration-manager while retaining ms.subservice as sdk.

The page metadata now uses `mdm` with `configuration-manager` instead of `mobile-device-management` with `microsoft-endpoint-configuration-manager`.

The page metadata now uses `mdm` with `configuration-manager` instead of `mobile-device-management` with `microsoft-endpoint-configuration-manager`.

The document’s service metadata changed to `configuration-manager`, and its subservice metadata changed to `mdm`.

The page now uses `mdm` and `configuration-manager` metadata values instead of `mobile-device-management` and `microsoft-endpoint-configuration-manager`.

The page metadata now uses `mdm` with `configuration-manager` instead of `mobile-device-management` with `microsoft-endpoint-configuration-manager`.

The page metadata now uses `mdm` and `configuration-manager` service values.

The page’s service metadata changed to `configuration-manager`, and its subservice metadata changed to `mdm`.

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`; `ms.subservice` remains `sdk`.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`, while retaining the SDK subservice classification.

The page’s ms.service metadata changed from microsoft-endpoint-configuration-manager to configuration-manager.

The documentation now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page metadata now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The article’s service metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; the `sdk` subservice remains unchanged.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`; the `sdk` subservice remains paired with it.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while the `sdk` subservice remains unchanged.

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 the SDK subservice.

The documentation changes the `ms.service` value from `microsoft-endpoint-configuration-manager` to `configuration-manager` for the SDK subservice.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The document now uses `ms.service: configuration-manager` with `ms.subservice: sdk`.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The article’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The article’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page metadata now uses `configuration-manager` instead of `microsoft-endpoint-configuration-manager` for the SDK service association.

The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while its SDK subservice association remains.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page metadata now pairs `ms.subservice=sdk` with `ms.service=configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The page now uses `ms.service: configuration-manager` with `ms.subservice: sdk`, replacing `microsoft-endpoint-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 `sdk`.

The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-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 `ms.subservice` value remains `sdk`.

The release-notes page now uses `configuration-manager` instead of `microsoft-endpoint-configuration-manager` for the `ms.service` metadata value.

The documentation now pairs `ms.subservice: sdk` with `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The documentation now identifies the service as `configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` in the AppContentInfo structure reference.

The documentation metadata changed its ms.service value from microsoft-endpoint-configuration-manager to configuration-manager.

The page now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager` while retaining the SDK subservice.

The documentation now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager while retaining ms.subservice=sdk.

The page metadata changes `ms.service` from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining the `sdk` subservice.

The article’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while `ms.subservice` remains `sdk`.

The page now pairs `ms.subservice: sdk` with `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.

The documentation now pairs `ms.subservice: sdk` with `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.