Blog Post

Configuration Manager Blog
3 MIN READ

Announcing the Annual Release Cadence for Microsoft Configuration Manager

Danny_Guillory's avatar
Nov 05, 2025

Starting with version 2609, Microsoft Configuration Manager will transition to an annual release cadence. This change is a formalization of the direction we’ve communicated at events and in customer conversations. 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.

 

Why Move to an Annual Release Cadence?

Historically, Configuration Manager followed a semi-annual release schedule. As the industry shifts toward cloud-native management, we’re aligning our release cycle to better support your long-term planning and operational stability. This annual cadence allows IT teams to:

  • Plan upgrades with confidence - knowing when to expect new releases.
  • Focus on stability and security - with each release prioritizing reliability over new features.
  • Transition at your own pace - while Microsoft Intune receives all future investments and innovations.

What Does This Mean for You?

Here’s what you can expect from upcoming 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 (details to be determined).

Focus on Security and Stability

Annual releases will align with the Windows client security and stability cadence (H2). Our top priority is to maintain a secure, reliable Configuration Manager experience. This means:

  • Applying critical updates and patches as needed.
  • Providing hotfix rollups only when absolutely necessary (e.g., for critical security or functionality issues).
  • Continuing to support existing environments, with advance notice for any feature deprecations.

Support Lifecycle

The support lifecycle remains unchanged; each version receives 18 months of support from its release date. Here’s a quick reference:

Version

Support Start

Support End

2403

March 2024

September 2025

2409

September 2024

March 2026

2503

March 2025

September 2026

2509

September 2025

March 2027

Frequently Asked Questions

Q: Is this a new direction for Configuration Manager?

A: No. While we’ve discussed this shift publicly for some time, this is the first time we’re formally documenting it. The only “new” aspect is the official annual cadence and the clarity it brings to your planning.

Q: Will there be hotfixes or out-of-band updates?

A: Only if absolutely necessary - such as for critical security or functionality issues. Otherwise, updates will be bundled into the annual release.

Q: What about support for existing environments?

A: We remain committed to supporting your Configuration Manager environments. Any changes or deprecations will be communicated well in advance.

Looking Ahead

This annual release cadence is designed to give you predictability, stability, and the confidence to plan for the future. As you consider your long-term device management strategy, remember that Microsoft Intune is where all new innovation happens.

Whether you’re getting started with Intune or currently using Configuration Manager, Microsoft provides clear guidance to help you modernize at your own pace. Explore the Intune deployment guide to set up or move to Intune, and see the section on using Configuration Manager for co-management or a phased transition.

We’re here to support your journey - wherever you are on the path to cloud-native Windows.

 

If you have any questions, leave a comment on this post or reach out on X @MSConfigMgrTeam

Updated Oct 30, 2025
Version 1.0

5 Comments

  • Dynas's avatar
    Dynas
    Copper Contributor

    ~ In the early 2000s MS strongly "encouraged" companies to use GPOs to push software until there was enough push back. 
    ~ 2009 they did the same thing with MDT which was later integrated into SCCM.

    MS could be making a significant mistake again here. Until INTUNE gets it's flexibility and feature set as flexible and stable as MECM they should be focusing on making MECM more CLOUD friendly. 

    At some point companies are going to purchase competing products that are mature and MS is going to lose out, as happened in my previous examples.  Some folks at MS should be getting canned over these calls. 

  • M_Wilkinson_'s avatar
    M_Wilkinson_
    Copper Contributor

    There was a time when ConfigMgr was invested in based on user feedback. Features such as CMPivot which is an extremely useful tool that came from feedback from the ConfigMgr community.  The same feature within Intune requires additional licensing. This doesn’t feel like a good idea to force organisations to a solution that isn’t as good as ConfigMgr.

  • Please dont forget to mention Azure Arc as the Server Management alternative. And please invest heavily in Arc Development so that it can be one day a serious management solution for a current ConfigMgr Customer, which uses the whole stack. 

  • AJ Hemsey's avatar
    AJ Hemsey
    Brass Contributor

    I think you guys are missing something important here...
    With ConfigMan, we have best in breed device management, with Intune, we have "Baby's First Deployment".

    Intune is a LONG way away from feature parity, let alone better in any way that matters, so I understand directing more resources to Intune, but it seems to me that you are prematurely abandoning on-prem.

    In my opinion, having the option of using ConfigMan and/or Intune to manage my clients is the best option. Having the option to choose which option fits which situation is best of both worlds. Limiting myself to only on-prem or Intune is a step backwards no matter which direction I go.

  • mdConfigMgr's avatar
    mdConfigMgr
    Copper Contributor

    will there be a new tech preview release for those of us still running TP and our instances are about to expire since the previous release?