Microsoft is reshaping the future of on-premises endpoint management by moving Microsoft Configuration Manager (ConfigMgr/SCCM) to a once-a-year release cycle, while continuing to position Microsoft Intune as the primary destination for new device-management innovation. This shift is set to begin with version 2609, with the annual cadence taking effect in Fall 2026.
What’s changing: from twice-yearly to annual releases
For years, ConfigMgr has followed a two releases per year rhythm. Microsoft is now moving to a predictable annual release model.
Why that matters
A yearly cadence for Configuration Manager generally means:
- More predictable planning for IT teams (budgeting, testing windows, change management)
- Reduced upgrade churn for environments that rely on careful validation
- A stronger emphasis on stability and security over frequent feature drops
Microsoft also indicated that hotfix rollups will be reserved for urgent security or critical functionality issues, while critical patches will still arrive when needed.
Intune is where new innovation happens
The release-cadence change isn’t just about scheduling—it’s a strategy signal.
Microsoft has been increasingly explicit that:
- Intune is the future of device management.
- New capabilities and innovation will land in Intune first.
- ConfigMgr will continue to serve on-premises needs, with emphasis on security, stability, and long-term support.
In practical terms, many organizations will treat ConfigMgr as the dependable on-prem platform for scenarios that still require it, while building a roadmap toward broader cloud management with Intune.
Conclusion
Microsoft’s shift to yearly ConfigMgr releases is a clear move toward stability and predictability for on-prem management—while reinforcing that Intune is the long-term center of gravity for endpoint management innovation. For most organizations, the winning strategy over the next two years will be pragmatic: keep ConfigMgr stable where it’s essential, and steadily expand Intune where cloud management fits.
If you tell me your environment (size, on-prem vs remote ratio, co-management status, Windows versions), I can suggest a simple migration/modernization plan aligned to this new cadence.