Configuration Manager’s Annual Release Cadence: What It Means for Third-Party Patching
Direct Answer
Microsoft Configuration Manager moved to one release per year, starting with version 2609 in September 2026. The next planned release is 2709 in September 2027. Each version still receives 18 months of support from its release date, and hotfix rollups are issued only when necessary, such as for critical security or functionality issues. Nothing changes mechanically for third-party patching: the software update point still works. What changes is the planning horizon, because Microsoft states that Intune is where new innovation happens.
Key Takeaways
- Configuration Manager is not being discontinued; it is moving to a slower, stability-focused release cycle.
- Releases: 2509 (December 2025), 2603 (March 2026), 2609 (September 2026, the first annual release), 2709 (September 2027).
- Each version is supported for 18 months from its release date, so upgrade windows now need to be scheduled, not improvised.
- Third-party update publishing through the software update point is unaffected, but new capability will land in Intune, not ConfigMgr.
What Microsoft announced
Microsoft announced on the Configuration Manager blog that the product moves to an annual release cadence, aligning with the Windows client security and stability cadence. The post sets out the schedule: 2509 in December 2025 with stability and quality updates including ARM64 support, 2603 in March 2026 focused on security aligned with the Secure Future Initiative, 2609 in September 2026 as the first annual release, and 2709 in September 2027.
Microsoft also states plainly that Intune is the future of device management and that all new innovations will occur there, while Configuration Manager continues to serve on-premises devices with a focus on security, stability and long-term support.
What changes, and what does not
| Unchanged | Changed |
|---|---|
| The software update point and WSUS foundation keep working. | One feature release per year instead of two or three. |
| Third-party software update catalogs continue to publish and deploy. | Hotfix rollups and out-of-band updates only when absolutely necessary. |
| Automatic deployment rules, collections and Software Center behave the same. | New capability is being built in Intune rather than Configuration Manager. |
| Each version is supported for 18 months from its release date. | Fewer upgrade opportunities, so each upgrade window matters more. |
The support arithmetic you now have to plan around
Eighteen months of support per version, with one release a year, leaves a narrower margin than the old cadence did. Version 2609 was released in September 2026, so its support runs into early 2028, and 2709 arrives in September 2027. In practice that means roughly a six-month overlap in which to validate and deploy each annual upgrade.
If an upgrade slips past that window, the site runs on an unsupported version until the next annual release arrives, which could be months away. Put the upgrade in the annual plan rather than treating it as an opportunistic task. Confirm exact support end dates for your version on Microsoft Learn before you commit the plan.
What it means for third-party patching
Nothing breaks. Configuration Manager can still subscribe to third-party software update catalogs, publish signed updates to the software update point and deploy them like Microsoft updates, including through automatic deployment rules.
The strategic point is different. If your third-party patching depends on capabilities that only exist in Configuration Manager, you are building on a platform that will receive stability and security work rather than new features. Tooling that publishes to both Configuration Manager and Intune keeps your options open and avoids a second migration later.
Three realistic paths
| Path | Best for | What to do about third-party updates |
|---|---|---|
| Stay on Configuration Manager | Stable on-premises estates, disconnected or regulated environments | Keep catalogs and ADRs running. Schedule the annual upgrade. Document the long-term plan so it is a decision, not an accident. |
| Co-management | Organizations moving workloads to Intune in phases | Use one catalog and one process that publishes to both systems, so coverage does not drop while workloads move. |
| Intune-first | Organizations with most devices already in Intune | Move application delivery to Intune and keep ConfigMgr for what still needs it. |
Planning checklist
- Record your current Configuration Manager version and its support end date.
- Put the annual upgrade in next year’s calendar with a validation window before it.
- List every third-party update workflow that runs through Configuration Manager today.
- Decide which device groups will move to Intune, and when.
- Confirm your patching tooling supports both systems during the overlap.
- Align reporting so compliance can be measured across both environments.
How Easy2Patch fits
E2P Patch Manager publishes third-party application updates to Configuration Manager, WSUS and Microsoft Intune from the same catalog, with no additional agent on endpoints. For organizations managing devices in more than one system during a transition, that means one catalog and one process rather than two parallel ones. For Intune-only environments, PatchInCloud publishes and updates third-party applications directly in Intune.
Frequently Asked Questions
No. Microsoft announced a move to an annual release cadence, not an end-of-life date. Configuration Manager continues to serve on-premises devices with a focus on security, stability and long-term support. Microsoft does state that Intune is the future of device management and that new innovations will occur there, so long-term plans should account for that direction.
Version 2609 shipped in September 2026 as the first release under the annual cadence, and version 2709 is planned for September 2027. Between annual releases, Microsoft issues hotfix rollups and out-of-band updates only when absolutely necessary, such as for critical security or functionality issues.
The support lifecycle is unchanged: each version receives 18 months of support from its release date. With only one release a year, that leaves a narrower overlap than the previous cadence, so organizations should schedule validation and upgrade windows in advance rather than treating the upgrade as optional work.
Yes. The software update point, third-party software update catalogs, automatic deployment rules and Software Center all continue to work exactly as before. The annual cadence changes how often new features arrive, not whether existing update workflows function. The practical change is strategic: new capability is being built in Intune, so plan tooling that works across both systems.
Not immediately. Configuration Manager keeps receiving security and stability work, so on-premises estates can continue. The practical implication is that new capability will appear in Intune, so a plan that assumes Configuration Manager will gain significant new features over the next few years is unlikely to hold.
Conclusion
An annual cadence is a planning signal. Schedule the upgrade, know your support end date, and choose third-party patching tooling that works across both Configuration Manager and Intune so the platform decision stays yours.
IT Automation Key Benefits and Best Practices

What Is Vulnerability Management?

Ultimate IT Risk Management Guide 2024: Best Practices, Strategies, and Tools

Best Practices for IT Infrastructure Management in 2024

What is Windows Patch Management? Features, Challenges, and Best Practices in 2024

What are the Cybersecurity Risks Associated with Outdated Software and Operating Systems?
