In Development
The page now lists Apple OS 27 DDM inventory data, MEFERI OEMConfig support for Android Enterprise, removal of legacy Apple MDM software-update workloads, and two Administrator protection settings for Windows 11 24H2 and 25H2.
A cross-product view of Microsoft Intune changes related to General.
The page now lists Apple OS 27 DDM inventory data, MEFERI OEMConfig support for Android Enterprise, removal of legacy Apple MDM software-update workloads, and two Administrator protection settings for Windows 11 24H2 and 25H2.
The archive page now links to the Admin tasks content under Governance instead of Device management.
The device overview instructions now direct administrators to select Remove data, then Autopilot reset.
The article was retitled and updated to explain how to change or remove a device’s primary user from the Properties tab, along with how Intune assigns and uses the primary user.
The article now defines device categories as labels, explains their relationship to dynamic Microsoft Entra security groups, and covers creating categories, building groups, and assigning categories to devices.
The documentation consistently renames the action to “Remove apps and configurations” and updates the steps to select Remove data > Remove apps and configurations.
The instructions now say to select **Secure** before choosing **Disable Activation Lock** in the device overview action menu.
The instructions now direct administrators to select **Remove data** before selecting **Fresh Start** in the device overview pane.
The documented steps changed from selecting **Full scan** directly to selecting **Microsoft Defender** > **Run full malware scan**.
The index now links to the device management overview, uses updated titles for device categories and primary-user tasks, and removes links for endpoint security device management, admin tasks, and encryption status details.
The Intune What’s new page was updated, including a new metadata date, and the entry describing bulk eSIM actions for corporate-owned Android Enterprise devices was removed.
The instructions specify selecting **Locate device** on Windows and **Locate** > **Locate device** on iOS and Android. Location details remain available from the map pin.
The instructions now direct administrators to select **Remote actions** before choosing **Logout current user** from the device overview pane.
The instructions now direct administrators to select **Locate** and then **Lost mode (supervised only)** from the device overview action icons.
The documentation now links to the centralized Admin tasks pane under the governance path instead of the device-management path.
The documented steps now direct administrators to select Remote actions > Pause Config Refresh from the device overview pane.
The instructions now direct administrators to select Locate before choosing either Play Lost Mode sound or Play lost device sound.
The instructions now direct administrators to select Microsoft Defender > Run quick malware scan from the device overview action icons.
The instructions now direct administrators to select **Secure** > **Remote lock** from the device overview action icons.
The instructions now direct administrators to select **Secure** and then **Remove passcode** from the device overview action icons.
The page documenting the Rename device action, including supported platforms, role requirements, and admin-center steps, was deleted.
The new guidance explains how to rename managed devices from the Intune admin center, supported platforms, platform-specific naming rules, bulk-renaming variables, and limitations such as hybrid-joined Windows devices not being supported.
The instructions now direct administrators to select **Secure** > **Reset passcode** from the device overview action icons.
The restart procedure now instructs administrators to select **Remote actions** > **Restart** > **Yes** from the device overview pane.
The instructions now direct administrators to select Remote actions > Restore Managed Home Screen from the device overview pane.
The instructions now direct administrators to select **Remove data** > **Retire** from the device overview action icons, instead of selecting **Retire** directly.
The instructions now direct administrators to select **Secure** > **BitLocker key rotation** from the device overview action icons.
The action is now accessed through **Secure** > **Rotate FileVault recovery key** in the device overview pane.
The device overview instructions now direct admins to select **Secure** before choosing **Rotate Local admin password**.
The instructions now direct administrators to select Secure > Rotate Recovery Lock Passcode from the device overview action icons.
The documented path changed from selecting Shut down directly to selecting Remote actions > Shut down > Yes.
The instructions now direct administrators to select **Remote actions** before choosing **Suspend Managed Home Screen**.
The Company Portal help page now links to “Rename a device in Microsoft Intune” at a new documentation location.
The article now links to `/device-management/inventory-and-status/rename-device` instead of `/device-management/actions/rename`.
The article now explains how to open a device’s Device details tab, distinguishes read-only inventory from editable Properties, and documents hardware and software inventory refreshing every seven days from enrollment.
The documented steps now direct administrators to select Remove data > Wipe from the device overview action icons.
The documentation now states that built-in Asset Intelligence reports are removed from Monitoring > Reporting > Reports in version 2609. References apply to version 2603 and earlier.
The documentation now states that all SQL Server versions currently supported by Configuration Manager support TLS 1.1 and TLS 1.2. Secondary site servers now require SQL Server 2017 Express with CU2 or later, replacing the previous SQL Server 2016 Express SP2 minimum.
The index now includes Configuration Manager 2609 and links to KB 2377842. Entries for versions 2107 through 2211 were removed, and the page date was updated.
The documentation states that version 2609 removes the Catalog Synchronization and Inventoried Software Status sections from the Asset Intelligence home page and removes Asset Intelligence reports from Monitoring > Reporting > Reports.
The documentation now requires ODBC Driver 18.6.2.1 or later for Configuration Manager 2609 and later, and SQL Server 2017 CU2 or later starting with 2609. Unsupported versions can block installation or upgrades; it also identifies version-specific incompatible ODBC releases and adds a non-blocking warning about automatic client approval.
Starting in version 2609, the Catalog Synchronization and Inventoried Software Status sections, along with Asset Intelligence reports, are removed. The page instead provides deprecation information and links to the product lifecycle dashboard and Asset Intelligence client settings. Earlier procedures apply only to version 2603 and earlier.
The page date changed to September 22, 2026, and the “What’s new” link changed from version 2503 to version 2609.
The documentation now specifies Microsoft ODBC Driver for SQL Server and links to minimum, validated, and blocking versions. Starting in version 2609, Configuration Manager automatically installs the Microsoft OLE DB Driver for SQL Server and no longer requires SQL Server Native Client; versions 2603 and earlier retain the previous Native Client behavior.
The guidance now requires TRUSTWORTHY for Configuration Manager 2603 and earlier, but says it isn't needed and should be skipped for version 2609 and later when loading SQLCLR assemblies.
The documentation marks SQL Server 2016 and SQL Server 2016 Express as deprecated in version 2609. SQL Server editions earlier than SQL Server 2017 CU2 must be upgraded before installing or updating to 2609; the Visual C++ Redistributable on secondary sites must also be updated.
The documentation no longer lists Windows Server 2012 R2, Microsoft Hyper-V Server 2012, or Windows Server 2012. The page date was updated to September 21, 2026.
Starting with Configuration Manager version 2609, the TRUSTWORTHY database property is not required to load Microsoft-signed SQLCLR assemblies, including for databases using SQL Server Always On availability groups. Version 2603 and earlier still require TRUSTWORTHY to be enabled.
Starting with Configuration Manager version 2609, Windows Server 2012, Windows Server 2012 R2, and their Windows Storage Server editions will no longer be supported as client operating systems.
The page now lists version 2609 (5.00.9152.1000), released September 28, 2026, with support through March 28, 2028. Version 2503 is now shown as plain text.
The documentation now lists SQL Server 2025 and removes SQL Server 2016, SQL Server 2014, and the SQL Server 2016 upgrade link.
The Configuration Manager version 2309 documentation now links to the prerequisite-checks page for minimum required versions, validated versions, and known blocking issues for the ODBC driver for SQL Server.
The planning guide now links to `integrate-windows-update-client-policies.md` instead of the previous `integrate-windows-update-for-business-windows-10.md` article.
The article now revises its explanation of how Configuration Manager distinguishes Windows Update client policies from WSUS, including the UseWUServer attribute.
The application documentation now uses `core-infra` and `configuration-manager` metadata values instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The documentation replaces `ms.subservice: core-infrastructure` and `ms.service: microsoft-endpoint-configuration-manager` with `core-infra` and `configuration-manager`.
The page replaces `core-infrastructure` with `core-infra` and `microsoft-endpoint-configuration-manager` with `configuration-manager`.
The page now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous metadata values.
The page’s metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The article metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The article metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous values.
The page metadata changes `ms.subservice` from `core-infrastructure` to `core-infra` and `ms.service` from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page now uses `core-infra` and `configuration-manager` metadata values instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The documentation metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page’s service classification changed from `core-infrastructure` / `microsoft-endpoint-configuration-manager` to `core-infra` / `configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `configuration-manager` with `core-infra` instead of `microsoft-endpoint-configuration-manager` with `core-infrastructure`.
The article’s service metadata changed from `microsoft-endpoint-configuration-manager` to `configuration-manager`, and its subservice metadata changed from `operating-system-deployment` to `osd`.
The document metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page’s metadata values changed from `core-infrastructure` to `core-infra` and from `microsoft-endpoint-configuration-manager` to `configuration-manager`.
The page metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` metadata values.
The documentation metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous values.
The page now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`, replacing the previous metadata values.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous values.
The page now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`, replacing the previous metadata values.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`, replacing the previous metadata values.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager` instead of the previous values.
The page now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous metadata values.
The page metadata changed from `microsoft-endpoint-configuration-manager`/`core-infrastructure` to `configuration-manager`/`core-infra`.
The page metadata now uses `core-infra` with `configuration-manager` instead of `core-infrastructure` with `microsoft-endpoint-configuration-manager`.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The article now uses `ms.subservice: osd` and `ms.service: configuration-manager` metadata values.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` in place of the previous metadata values.
The page’s service metadata changed to `configuration-manager` and its subservice metadata changed to `core-infra`.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager`.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`, replacing the previous values.
The page metadata now uses `ms.subservice: core-infra` and `ms.service: configuration-manager` instead of the previous values.
The article’s metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `ms.subservice=core-infra` and `ms.service=configuration-manager` instead of the previous values.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page now uses `core-infra` and `configuration-manager` service metadata values instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The document’s service metadata changed from `core-infrastructure` and `microsoft-endpoint-configuration-manager` to `core-infra` and `configuration-manager`.
The page metadata now uses `ms.subservice: core-infra` with `ms.service: configuration-manager`, replacing the previous values.
The page metadata now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.
The page now uses `core-infra` and `configuration-manager` instead of `core-infrastructure` and `microsoft-endpoint-configuration-manager`.