Microsoft are changing how Endpoint Detection and Response (EDR) updates are delivered to Windows endpoints. As detailed in message center update MC1381119, Microsoft Defender for Endpoint security updates will decouple from the standard monthly Windows cumulative security updates starting in late May 2026, moving over to the Microsoft Update channel instead.
This change initially applies to Windows 10, with plans to expand the rollout to Windows 11 and other supported operating systems by autumn 2026.
Technical Breakdown
Historically, core updates to the Defender for Endpoint EDR sensor component (MsSense.exe) arrived packaged within the monthly Windows cumulative patch cycle. Under the new model, these updates will download independently via the Microsoft Update service, matching the cadence currently used for Defender Antivirus platform and signature updates.
This change allows Microsoft to deploy EDR sensor updates quicker without requiring a full operating system cumulative update installation. It also reduces the footprint of the monthly Windows cumulative update package. Endpoints must be configured to accept updates for other Microsoft products to receive these standalone sensor payloads.
How to Audit Your Update Ring Configuration
To ensure your endpoints continue receiving EDR updates after this transition, you need to verify that your update policies allow updates from the Microsoft Update service alongside standard Windows updates.
In the Microsoft Intune Admin Centre, you can verify this by checking your Windows 10 and later update rings. Ensure the setting Update to other Microsoft products is set to Allow.
To audit this configuration across all update rings in your estate, you can query the Microsoft Graph API. Here is a ready PowerShell snippet below identifies your current update policies and highlights whether the Microsoft Update service is enabled.
Connect-MgGraph -Scopes "DeviceManagementConfiguration.Read.All"
$Uri = "/beta/deviceManagement/deviceConfigurations?`$filter=isof('microsoft.graph.windowsUpdateForBusinessConfiguration')"
$Response = Invoke-MgGraphRequest -Method GET -Uri $Uri
if ($Response.value) {
$Response.value | ForEach-Object {
[PSCustomObject]@{
PolicyName = $_.displayName
Id = $_.id
MicrosoftUpdate = if ($_.microsoftUpdateServiceAllowed) { "Allowed" } else { "Blocked" }
}
} | Format-Table -AutoSize
} else {
Write-Host "No Windows update ring policies found." -ForegroundColor Yellow
} The output of the script should look something like the below:
If the MicrosoftUpdate column shows blocked for your policies, then you should consider enabling this.
Next Steps for Administrators
If you manage an endpoint environment, you should take action before the full rollout begins to prevent endpoints from falling behind on security updates.
Review Intune Policies: Run the provided Graph PowerShell script to ensure all active Windows update rings permit updates for other Microsoft products.
Update WSUS Sync Rules: If you use on-premises update management, confirm that the Defender product classifications are explicitly ticked in your settings.
Validate Test Rings: Monitor the engine version of
MsSense.exeon your early adoption test devices during June to ensure the standalone payloads are applying correctly.

