Microsoft has announced that Microsoft Configuration Manager (Current Branch) version 2503 will reach its end of support on September 30, 2026 (Pacific Time). Organisations still running this version should begin planning to upgrade to version 2603 well before the deadline to ensure continued security, support, and access to new product improvements.
Configuration Manager 2503 is a Current Branch release that became available in March 2025. Like all Current Branch releases, version 2503 follows Microsoft’s modern servicing model and receives support for a limited lifecycle
Microsoft documentation and community guidance commonly refer to the support deadline for version 2503 as September 30, 2026 PT, which aligns with the lifecycle retirement date. The support start and end dates for last three versions of SCCM are provided in the table below.
| Version | Start Date | End of Support |
|---|---|---|
| 2503 | March 31, 2025 | October 1, 2026 (Lifecycle listing) |
| 2509 | November 12, 2025 | May 13, 2027 |
| 2603 | May 5, 2026 | November 6, 2027 |
Why the End-of-Support Date Matters
Once Configuration Manager 2503 reaches the end of its lifecycle:
- Microsoft will no longer provide technical support for the version.
- Security updates will cease.
- Critical bug fixes will no longer be released.
- Organizations may face increased security and compliance risks.
- Future integrations and platform features may not be supported.
Running an unsupported management platform can expose enterprise environments to operational and cybersecurity risks, particularly when managing Windows devices at scale.
Recommended Upgrade Path
Organizations running Configuration Manager 2503 should proactively upgrade before September 30, 2026.
Preparing for the Upgrade
IT teams should begin preparations well ahead of the deadline:
Assess Current Environment
- Review current Configuration Manager hierarchy.
- Validate site health and replication status.
- Inventory custom integrations and extensions.
Review Microsoft Documentation
- Study supported upgrade paths.
- Verify operating system and SQL Server compatibility.
- Review known issues and prerequisites.
Test in a Non-Production Environment
- Validate business-critical applications.
- Test task sequences and operating system deployments.
- Confirm co-management workloads function as expected.
Schedule Production Rollout
- Coordinate with change-management teams.
- Communicate maintenance windows to stakeholders.
- Plan phased deployments where appropriate.
Conclusion
The retirement of Microsoft Configuration Manager version 2503 on September 30, 2026 is a significant milestone for IT organizations managing Windows endpoints. Microsoft recommends staying on a supported Current Branch release, and most organizations should view Configuration Manager 2603 as the strategic upgrade target. By planning early, validating compatibility, and implementing a structured upgrade process, enterprises can maintain security, supportability, and operational stability beyond the 2503 lifecycle.