Thursday, 29 January 2026

Windows MAM guidance specifies Windows 11 23H2 and later for its Security Center connector

29 January was a documentation-heavy maintenance day: 33 pages were updated—23 for Intune, nine for Configuration Manager, and one for Enterprise App Management—with no new or removed items and no Message Center entries. The meaningful exceptions are concrete: Windows MAM now explicitly scopes the Windows Security Center Mobile Threat Defense connector to Windows 11 version 22631 (23H2) or later; the Defender for Endpoint integration guide spells out Security Management for Defender for Endpoint on unenrolled devices and its required toggle; and related runbooks refresh portal paths and labels. Configuration Manager also receives a more actionable SQL and database requirements table. Most remaining edits replace hard-coded Windows 10 or legacy build references with supported-version links, repair links or metadata, and clean up wording—documentation clarification rather than evidence of broad feature launches, previews, or retirements.

• Intune · App management

  Windows MAM clarifies Security app naming and connector support

  The page changes 'Windows Security Center client threat defense' to 'Windows Security app client threat defense,' points general Windows MAM availability to supported Windows versions, and says the Mobile Threat Defense (MTD) Connector for the Windows Security Center component is only supported on Windows 11 version 22631 (23H2) or later. It also states that App Protection Conditional Access is generally available. This is a support and terminology clarification in the supplied diff, not proof of a new MAM release.

• Intune · Device security

  Defender integration guidance covers unenrolled-device security management

  The revised integration guide says admins can manage Microsoft Defender for Endpoint security configurations on devices that are not enrolled in Intune—a scenario called Security Management for Microsoft Defender for Endpoint—and requires the `Allow Microsoft Defender for Endpoint to enforce Endpoint Security Configurations` toggle to be `On`. It also surfaces task-specific requirements and general integration prerequisites. The diff documents the workflow; it does not establish a new preview, GA event, or product-

• Intune · Device security

  Endpoint detection and response guidance changes navigation and sample-sharing labels

  The revised instructions direct admins to Endpoint security > Endpoint detection and response > Summary tab > Create Policy. They describe sample sharing as `All` for automatic sample sharing or `None` to disable it, replacing the prior `On` and `Off` wording. Update runbooks to match these labels; the evidence supports a documentation and UI-instruction change, not a claim about detection behavior.

• Configuration Manager · General

  Configuration Manager consolidates SQL and database prerequisites into required-value tables

  The updated guidance says Configuration Manager sets these configurations during setup and lists CLR integration (`clr enabled`) = True, nested triggers = True, and `max text repl size (B)` = 2147483647 under required SQL Server configurations. It separately lists database owner (`owner_sid`) = `sa` and `CHANGE_TRACKING` = True (ON), with the database guidance applying to standalone primary sites, hierarchies, and SQL Always On configurations. It says not to alter these settings unless instructed by Microsoft​​​​

• Configuration Manager · General

  Configuration Manager clarifies where high-impact non-OS task sequences appear

  The revised note says a non-OS deployment task sequence marked high-impact appears under Operating Systems in Software Center, alongside all OSD task sequence deployments. Normally, non-OSD task sequence deployments appear under Applications. This clarifies Software Center placement for ConfigMgr targeting and user instructions rather than announcing a new deployment mode.

This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.