Microsoft Configuration Manager (Microsoft SCCM) is Microsoft's platform for managing endpoints, distributing updates, enforcing security policies, and inventorying devices in enterprise environments. Maintaining the installed version within the active support period is a requirement for compliance, security, and eligibility for critical patches—out-of-support versions do not receive patches or incident support.
This guide compiles the complete table of Microsoft Configuration Manager versions with start and end support dates, updated with versions released through 2025–2026, as well as the key features of the most recent releases.
Microsoft Configuration Manager lifecycle
The product follows the Modern Life Cycle Policy From Microsoft: each version receives support for approximately 18 months from release. There is no additional paid extended support—after support ends, no security patches, new features, or incident handling are provided.
Rebranding note: Starting with version 2303 (April 2023), the product was renamed to Microsoft Endpoint Configuration Manager to Microsoft Configuration Manager. Versions prior to 2303 were still being marketed as Endpoint Configuration Manager or SCCM.
| Version | Start Date | End Date | Status |
|---|---|---|---|
| Version 2509 | November 12, 2025 | May 12, 2027 | ✅ In support |
| Version 2503 | March 31, 2025 | September 30, 2026 | ✅ In support |
| Version 2409 | December 4, 2024 | June 6, 2026 | ✅ In support |
| Version 2403 | April 22, 2024 | October 22, 2025 | ⚠️ Closed |
| Version 2309 | October 9, 2023 | April 9, 2025 | ❌ Out of support |
| Version 2303 | April 10, 2023 | October 10, 2024 | ❌ Out of support |
| Version 2211 | December 19, 2022 | June 5, 2024 | ❌ Out of support |
| Version 2207 | August 12, 2022 | February 12, 2024 | ❌ Out of support |
| Version 2203 | April 8, 2022 | October 6, 2023 | ❌ Out of support |
| Version 2111 | December 1, 2021 | June 1, 2023 | ❌ Out of support |
| Version 2107 | August 2, 2021 | February 2, 2023 | ❌ Out of support |
| Version 2103 | April 5, 2021 | October 5, 2022 | ❌ Out of support |
| Version 2010 | November 30, 2020 | May 30, 2022 | ❌ Out of support |
| Version 2006 | August 11, 2020 | February 11, 2022 | ❌ Out of support |
| Version 2002 | April 1, 2020 | October 1, 2021 | ❌ Out of support |
| Version 1910 | November 29, 2019 | May 29, 2021 | ❌ Out of support |
| Version 1906 | July 26, 2019 | January 26, 2021 | ❌ Out of support |
Source: Microsoft Lifecycle — Microsoft Configuration Manager (updated in Dec/2025).
Versions actively supported in 2026
As of June 2026, three versions remain within the active support period:
- Version 2509 (Nov. 2025 – May 2027): latest version, with support until May 2027.
- Version 2503 (March 2025 – September 2026): still in support, but will enter the end of its cycle in September 2026.
- Version 2409 (Dec. 2024 – Jun. 2026): End of support in June 2026 — immediate upgrade recommended.
Organizations operating version 2409 should plan to migrate to 2503 or 2509 immediately, given the end of support in June 2026.
New features in Version 2509 (November 2025)
Version 2509 is the latest release of Microsoft Configuration Manager and is recommended for environments requiring extended support until 2027. Key enhancements in this version include:
- Improvements to co-management with Microsoft Intune.
- Performance improvements in the large-scale content distribution process.
- Compatibility updates for Windows 11 24H2 and Windows Server 2025.
- Refinements to the software update compliance monitoring dashboard.
For the complete list of changes, please refer to the official Microsoft release notes.
New features in Version 2503 (March 2025)
- Expanded support for Windows 11 deployment on ARM64 devices.
- Improvements to the hardware inventory mechanism for assets nearing the end of their lifecycle.
- Enhanced integration with Microsoft Entra ID (formerly Azure AD) for device authentication.
- New license compliance audit parameters to support Software Asset Management (SAM) scenarios.
What's new in Version 2403 (April 2024)
Version 2403 ended its support cycle in October 2025. Its main features were:
- Azure Active Directory rebranding for Microsoft Login ID within the Configuration Manager console.
- Automated Diagnostic Dashboard for Windows Server Update Services.
- Centralized search box in the Management Server console.
- Mandatory adoption of HTTPS or Enhanced HTTP — traditional HTTP deprecated.
- Native support for Windows Server 2012 and 2012 R2 has ended.
- ARM64 support for Windows 11 deployment, including ARM64 boot images.
End of support: relevant previous versions
The versions below will end their support on dates that deserve special attention because they are still in use in many organizations:
- Version 2309: closed in April 2025.
- Version 2303: closed in October 2024.
- System Center 2012 Configuration Manager / 2012 R2Support ended in July 2022, with no security patches available since then.
Microsoft SCCM, SAM, and ITAM: Strategic Integration
Microsoft Configuration Manager is frequently used as a source of inventory data in strategies of Software Asset Management (SAM) and IT Asset Management (ITAM). Its integration with platforms such as ServiceNow SAM It allows you to consolidate the inventory collected by SCCM with data from license agreements, network discovery, and usage metrics — eliminating silos between endpoint management and asset governance.
Organizations that use SCCM as the sole source of truth for software inventory frequently face compliance gaps in Microsoft licensing audits. Adopting a SAM layer on top of Configuration Manager data is the recommended approach to mitigate this risk.
To keep Microsoft Configuration Manager up-to-date and within active support, it is recommended to schedule semi-annual updates and monitor the Microsoft's official lifecycle page and to assess the maturity of the integration between SCCM and the asset governance tools in use in the organization.