Annual Release Cadence for Configuration Manager

In this post, I will share the information about the latest SCCM release cadence changes announced by Microsoft. Starting with version 2609, Configuration Manager will transition to an annual release cadence pushing just one update every year.

As Windows is moving to a once-a-year update model, Configuration Manager will be better aligning to the same cadence. This means you will get only one current branch update every year instead of two updates. This change will come into effect after the release of Configuration Manager version 2609.

Microsoft in their announcement stated that “Microsoft Intune is the future of device management, and all new innovations will occur there. Configuration Manager will continue to serve your on-premises devices, with a renewed focus on security, stability, and long-term support.”

Is SCCM Dead?

No, SCCM is not dead. It’s still supported, updated, and widely used, especially in organizations with complex on-premises needs (OSD, task sequences, bare-metal imaging, software updates patching, on-premise app distribution).

Microsoft has just changed the release cadence to one current branch update per year. SCCM is very much alive but is gradually being overshadowed by Microsoft’s modern, cloud-first management solutions, i.e. Microsoft Intune.

Why the Annual Release Cadence for SCCM?

Many IT professionals are curious about why Microsoft chose to release only one current branch update per year. Previously, Configuration Manager adhered to a semi-annual release schedule. However, as the industry transitions to cloud-native management, Microsoft has adjusted its release cycle to better support long-term planning and ensure greater operational stability.

Benefits

Switching the SCCM release cadence to a single annual update provides several advantages.

1. Plan upgrades with confidence: A single CB update a year makes it easy to plan and upgrade. Instead of two upgrades, it’s just one upgrade and you know when it’s going to be released.
2. Focus on stability and security: With SCCM’s annual release schedule, Microsoft typically resolves critical issues through hotfixes. If not immediately addressed, these fixes are usually included in the next major upgrade. This also eliminates the need for administrators to spend time manually installing each hotfix.
3. Transition at your own pace: Many organizations are transitioning to the Cloud, but SCCM is not being retired anytime soon. It will continue to receive updates and fixes, allowing organizations to gradually shift to the Cloud at their own pace.

What’s coming in next releases

Here’s what you can expect from upcoming Configuration Manager releases:

• 2509 (December 2025): Stability and quality updates, including ARM64 support.
• 2603 (March 2026): Enhanced security aligned with the Microsoft Secure Future Initiative
• 2609 (September 2026): The first annual release under the new cadence.
• 2709 (September 2027): Future-focused release, current no details available.

What about hotfixes or out-of-band updates?

I normally test each and every hotfix released for Configuration Manager and document the changes as well. With the new release cadence, Microsoft will release the hotfixes and OOB updates only if absolutely necessary. Otherwise, updates will be bundled into the annual release.

Moving from Configuration Manager to Intune

If you’re heavily on-premises, then Configuration Manager is the tool for you. If you’re hybrid or remote-first, I recommend exploring the Intune deployment guide to set up or move to Intune and see how to use Configuration Manager for co-management or a phased transition.