Setup Teamviewer
The documented navigation now directs administrators to select a device and choose **Remote actions** > **Begin a remote assistance session**.
A cross-product view of Microsoft Intune changes related to Compliance.
The documented navigation now directs administrators to select a device and choose **Remote actions** > **Begin a remote assistance session**.
Windows Autopatch enhancements, rolling out Sept 1–Oct 15, 2026, offer improved control over Windows quality, .NET Framework, and quick machine recovery updates. Features include customizable automatic/manual approvals, deferral settings, update pausing, and detailed per-device reporting for better update management.
Security Copilot is now included with Microsoft 365 E5/E7 plans, integrating agents across Defender, Entra, Intune, Purview, and its portal. No purchase or action is needed. Organizations get monthly Security Compute Units, developer tools, and can explore additional paid features or opt out by contacting support.
The conditional access quickstart now uses `ms.service: configuration-manager` with the co-management subservice instead of `microsoft-endpoint-configuration-manager`.
The servicing information page changed the callout from Caution to Important; its message about impacts to updates, reliability, security mitigations, and feature enablement remains the same.
The documentation metadata now uses `core-infra` and `configuration-manager` for the service and subservice tags.
The documentation metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` for `ms.subservice: sdk`.
The page’s Microsoft 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`; `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 `microsoft-endpoint-configuration-manager` for the SDK subservice metadata.
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’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` while retaining the SDK subservice.
The documentation now uses `ms.service: configuration-manager` instead of `ms.service: microsoft-endpoint-configuration-manager`, while retaining the SDK subservice classification.
The page now uses `ms.service: configuration-manager` with `ms.subservice: sdk`, replacing `microsoft-endpoint-configuration-manager`.
The page changes its ms.service value 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 `ms.subservice` remains `sdk`.
The documentation metadata changed its `ms.service` value 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 example’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The example’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page metadata changes `ms.service` from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining the `compliance` subservice.
The page’s service metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager` while retaining the compliance subservice.
The page metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager` for the compliance subservice.
The documented ms.service value paired with ms.subservice=sdk changed from microsoft-endpoint-configuration-manager to configuration-manager.
The page metadata now pairs ms.subservice: sdk with ms.service: configuration-manager instead of microsoft-endpoint-configuration-manager.
The page metadata changes `ms.service` from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page now 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 configuration baselines article 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 compliance subservice remains unchanged.
The page metadata now uses `configuration-manager` instead of `microsoft-endpoint-configuration-manager` for the service value.
The article’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The document’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page metadata now pairs the compliance subservice with `configuration-manager` instead of `microsoft-endpoint-configuration-manager`.
The example 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 GetEULA method page 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 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` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page metadata now uses `configuration-manager` instead of `microsoft-endpoint-configuration-manager` for `ms.service`.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`; `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 remaining paired with `ms.subservice: sdk`.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining the `compliance` subservice.
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 metadata now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`, paired with the existing SDK subservice.
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` 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 method documentation now uses `ms.service: configuration-manager` instead of `microsoft-endpoint-configuration-manager`.
The page metadata changed from `ms.service: microsoft-endpoint-configuration-manager` to `ms.service: configuration-manager`.
The page 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 compliance subservice remains associated with it.
The page metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The example’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page now uses `ms.service: configuration-manager` with `ms.subservice: compliance`, replacing `microsoft-endpoint-configuration-manager`.
The documentation now uses `configuration-manager` instead of `microsoft-endpoint-configuration-manager` for the `ms.service` metadata value.
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 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 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 metadata changes `ms.service` from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while retaining `ms.subservice: sdk`.
The documentation 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`, paired with `ms.subservice: sdk`.
The metadata now pairs ms.subservice=sdk with ms.service=configuration-manager instead of microsoft-endpoint-configuration-manager.
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`, paired with the existing SDK subservice label.
The documentation changes `ms.service` 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 documentation metadata changes the ms.service value 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.
The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The article’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page’s ms.service 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 page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page’s ms.service metadata changed from microsoft-endpoint-configuration-manager to configuration-manager.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page’s `ms.service` value changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, while its `ms.subservice` remains `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`, while the `sdk` subservice remains paired with it.
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 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 `ms.service: microsoft-endpoint-configuration-manager`.
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`, 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 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 the `sdk` subservice pairing remains.
The page’s ms.service value changed from microsoft-endpoint-configuration-manager to configuration-manager.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page’s `ms.service` metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page’s `ms.service` 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 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 `sdk` subservice pairing remains.
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`.
The page’s ms.service metadata changed from microsoft-endpoint-configuration-manager to configuration-manager.
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.
Updated Microsoft Intune documentation in intune/fundamentals/tenant-administration/add-groups.md.
Updated Microsoft Intune documentation in intune/configmgr/develop/compliance/about-application-configuration-items.md.