This article provides information about release-cadence changes for Microsoft Configuration Manager, introducing a new release cycle starting after the release of a Configuration Manager baseline version in 2303. To learn about the changes introduced in previous updates for Configuration Manager, branding, and baselines, see What's new in Configuration Manager incremental versions, Microsoft Configuration Manager FAQ, and, Baseline and update versions.
As Windows is moving to a once-a-year update model, Configuration Manager will be better aligning to that cadence by moving from three to two updates a year. The next release of Microsoft Configuration Manager after 2303 will be in September 2023, version 2309. Effectively, the xx07 and xx11 updates are being merged into an xx09 update. The consolidation of updates will roll up enhancements into this release; another outcome is reducing the number of deployments customers must manage annually.
Along with better alignment to the Windows cadence and reducing CM deployment management, this change will also allow Configuration Manager to have a longer development cycle to address key customer feature asks while continuing to deliver high quality updates. With this change and the longer development cycle, the Configuration Manager 2309 update will be able to address key customer asks around policy sync, software update troubleshooting, improved alerts, dashboarding, and more. Hotfix rollups and security updates will continue to be made available as necessary to address any critical bugs.
Cadence Change Summary:
- Starting in the calendar year 2023 customers will now receive two releases of Configuration Manager, one in March (xx03), and another in September (xx09) rather than the previous release cadence of xx03, xx07, and xx11.
- Baseline versions can be used to install a new Configuration Manager site and hierarchy, or to upgrade from a supported version of Configuration Manager. 2303, 2403… will be baseline releases.
- There will be four Technical Preview (TP) releases per year. Two will be released before each production current branch release, and one of Technical Preview release would be a baseline release. (TP Baseline are 180 days evaluation)
- There is no change to current branch support cadence. Each current branch version remains in support for 18 months from its general availability release date. For more information, see Support for Configuration Manager current branch versions.
Microsoft
