Configuration Manager moved to an annual release cadence with version 2609, released on 28 September 2026. Every time Microsoft changes the shape of ConfigMgr, someone reads it as a deprecation notice. It is not one, and the actual signal is more useful than the panic: Configuration Manager co-management has become a destination rather than a staging post.
What Microsoft announced
From version 2609, released on 28 September 2026, Configuration Manager releases once a year rather than three times. The releases align with the Windows client H2 security and stability cadence. Support terms do not change: each version still gets 18 months from its release date, and the Configuration Manager updates and servicing page lists every version with its availability and support end dates. Microsoft has said each release prioritises reliability over new features, with hotfix rollups only where genuinely necessary.
| Version | Available | Support ends |
|---|---|---|
| 2409 | 4 December 2024 | 4 June 2026 (out of support) |
| 2503 | 31 March 2025 | 30 September 2026 (out of support) |
| 2509 | 12 November 2025 | 12 May 2027 |
| 2603 | 5 May 2026 | 5 November 2027 |
| 2609 | 28 September 2026 | 28 March 2028 |
Dates are from Microsoft’s updates and servicing page, checked on 6 November 2026. Microsoft notes that the availability date is when the early update ring was released, so the update can reach some consoles after that date.
Caution
Annual releases with unchanged 18 month support means your upgrade window gets wider, not narrower, but the consequence of missing one gets worse. On a three-a-year cadence a skipped release cost you a few months of headroom. On an annual cadence it costs you a year.
Configuration Manager 2609: release date, support end and what changed
Configuration Manager 2609 (version 5.00.9152.1000) became available on 28 September 2026 and is supported until 28 March 2028. It ships both as an in-console update and as baseline media, so a new site can install 2609 directly instead of installing an older baseline and updating.
Two items in what’s new in version 2609 matter before you schedule the upgrade. Configuration Manager no longer supports Windows Server 2012, Windows Server 2012 R2, or their Windows Storage Server editions as clients, so find any of those still carrying the client first. It also now verifies that its SQLCLR assemblies are Microsoft-signed. I have not run the 2609 upgrade in production; read the full list against your own site before you plan the window.
If you are on 2503 or earlier, 2609 is the version to target. 2503 support ended on 30 September 2026, and 2609 carries the longest support window of the three supported versions.
What it actually signals
Reliability-first releases on a yearly clock is what a product looks like when it has stopped growing and started being maintained. That is not the same as being killed. Microsoft has been explicit that new investment goes to Intune while Configuration Manager remains supported, and current lifecycle dates run to at least March 2029.
The honest reading: ConfigMgr is a stable dependency now, not a platform you should expect new capability from. Plan for it the way you plan for any stable dependency, which means fewer upgrades and no new architecture built on top of it.
Configuration Manager co-management is a valid end state
The part most migration advice gets wrong is treating co-management as a corridor you pass through on the way to pure cloud. Microsoft’s page on co-management for Windows devices says you control which workloads, if any, you switch from Configuration Manager to Intune, and Configuration Manager continues to manage every workload you do not switch. Nothing on that page sets a date by which the rest must move. That makes permanent co-management a legitimate destination, and for a lot of estates it is the correct one.
You keep co-management permanently when you have something ConfigMgr does that Intune does not do as well for you. Usually that is one of three things: deep OS deployment and imaging, complex application sequencing with real dependency chains, or the reporting and inventory depth people have built a decade of process around. If imaging is the one holding you, Autopilot device preparation is where the cloud native replacement now sits.
A cloud management gateway is a separate decision. Microsoft’s co-management page is explicit that a CMG is not required for co-management, and co-management is not required to use a CMG, although the two can be used together. Do not let a CMG project hold up a co-management decision, or the other way round. If internet-based clients are the real problem, scope the gateway on its own merits. I have not run a CMG in production, so weigh its hosting cost against how many of your clients actually sit off the corporate network before you build one.
The mechanics of getting there are seven sliders with a fixed order, set out in the workload order an SCCM to Intune migration forces.
Moving workloads in the right order
Workloads move independently, which is the whole point of co-management. Move them in order of blast radius, smallest first.
- Compliance policies. Reporting only until Conditional Access consumes them, so a mistake is visible and harmless.
- Windows Update policies. Reversible, and the failure mode is a delayed patch rather than a broken device.
- Resource access policies. Certificates, Wi-Fi, VPN. Test on real hardware before widening, because failure here locks people out of the network.
- Endpoint Protection. Straightforward once Defender is already the engine.
- Device configuration. Higher risk because settings conflict silently.
- Client apps. Usually last, and often the one that never fully moves.
Once device configuration has moved, Defender Controlled Configuration is what stops the old channel quietly winning that workload back.
The newsletter
Free PDF: the Intune troubleshooting field guide
Subscribe and get the free 8-page Intune troubleshooting field guide (PDF), then new fixes about twice a month. From a Microsoft MVP.
Checking where your workloads actually sit
The console shows the intended slider position. This shows what the devices believe, which is not always the same thing. If a client is not reporting at all, that is a check-in problem, and the order to work through it is in forcing an Intune sync.
# Run on a co-managed client. Returns the workload bitmask the client is
# actually honouring, not the value the console thinks it pushed.
$cm = Get-CimInstance -Namespace rootccmComanagementInfo -ClassName CCM_ComanagementInfo
[PSCustomObject]@{
Enabled = [bool]$cm.ComanagementEnabled
MDMWorkloads = $cm.MDMWorkloads # bitmask: which workloads Intune owns
ComgmtPolicy = $cm.ComgmtPolicyState
CapabilityMask = $cm.Capabilities
} | Format-List
# Decode the workload bitmask.
$map = [ordered]@{
1 = 'Compliance policies'
2 = 'Resource access policies'
4 = 'Device configuration'
8 = 'Windows Update policies'
32 = 'Endpoint Protection'
64 = 'Client apps'
128 = 'Office Click-to-Run apps'
}
$map.GetEnumerator() | ForEach-Object {
[PSCustomObject]@{
Workload = $_.Value
OwnedBy = if ($cm.MDMWorkloads -band $_.Key) { 'Intune' } else { 'ConfigMgr' }
}
} | Format-Table -AutoSize
What I would do
If you are on 2503 or earlier, the cadence change is not your problem. Being unsupported is: 2503 lost support on 30 September 2026 and 2409 on 4 June 2026. Get current first. And whatever you eventually decommission, retire it in the right order: Intune wipe vs retire.
If you are current and co-managed, do nothing differently. Annual releases make your life easier, not harder. Use the extra room to move one workload properly rather than three badly.
If you are planning a full decommission, be honest about which of the three ConfigMgr strengths you actually rely on. If the answer is none of them, finish the migration. If the answer is any of them, permanent co-management is a supported end state and choosing it deliberately beats drifting into it.
Certificates are usually the last dependency holding an estate to on-premises servers, and the licensing under that decision moved in July 2026. What Intune Cloud PKI now costs, and when it actually replaces NDES, covers where that line falls.
Last verified: 6 November 2026.



