Microsoft Configuration Manager End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Microsoft Configuration Manager versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Microsoft Configuration Manager 2609 is supported until March 28, 2028, its end-of-support date. The next Microsoft Configuration Manager version to reach end of life is 2509, on May 12, 2027. 5 of 8 tracked Microsoft Configuration Manager versions are past end of life; the most recent to reach it, 2503, did so on September 30, 2026. The full Microsoft Configuration Manager lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 2303 | 2303 | Apr 10, 2023 | Oct 10, 2024 | 729 days past EOL | EOL |
| 2309 | 2309 | Oct 9, 2023 | Apr 9, 2025 | 548 days past EOL | EOL |
| 2403 | 2403 | Apr 22, 2024 | Oct 22, 2025 | 352 days past EOL | EOL |
| 2409 | 2409 | Dec 4, 2024 | Jun 6, 2026 | 125 days past EOL | EOL |
| 2503 | 2503 | Mar 31, 2025 | Sep 30, 2026 | 9 days past EOL | EOL |
| 2509 | 2509 | Nov 12, 2025 | May 12, 2027 | 215 days remaining | Active |
| 2603 | 2603 | May 5, 2026 | Nov 5, 2027 | 392 days remaining | Active |
| 2609 | 2609 | Sep 28, 2026 | Mar 28, 2028 | 536 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/microsoft-configmgr)
Microsoft Configuration Manager lifecycle status — the real story
Microsoft Configuration Manager (ConfigMgr, formerly System Center Configuration Manager or SCCM, later Microsoft Endpoint Configuration Manager or MECM) is the on-premises endpoint management server that deploys software, updates and operating systems across Windows fleets. The current branch ships as numbered update versions named for year and month (2303, 2309, 2403 and so on), each installed in the console over the previous one or, for some versions, as a new baseline.
Microsoft supports each current branch version for 18 months from its general availability. Only the newest version is in the Security and Critical Updates phase; every older supported version receives security updates only, so a fix for a non-security defect requires being on the latest version. When a version leaves support, Microsoft's technical support will still help with upgrading to a supported version but gives no other assisted support.
Microsoft prints two different end dates for version 2409. The lifecycle product page and the end-of-support 2026 list both give June 6, 2026, while the Version details table on the Configuration Manager updates page gives June 4, 2026 (eighteen months from availability). This page serves June 6, the day the two lifecycle pages agree on; every other version reads the same on all three pages.
The practical trap is that sites upgrade once and stop: a site that is not current within the 18-month window is outside support even though Configuration Manager keeps running. CISA lists a Configuration Manager vulnerability (CVE-2024-43468) as known exploited, which makes an out-of-support site a live exposure rather than a paperwork problem.
Microsoft Configuration Manager release and support pattern
Across the 8 release lines with a published release date, Microsoft Configuration Manager has shipped a new line roughly every 6 months (median interval). A line typically stays supported for about 1.5 years from its release to its end-of-life date.
Of the 8 release lines tracked, 5 are past end of life and 3 are still within support. The newest line, 2609, was released September 28, 2026. The next scheduled end of life is 2509 on May 12, 2027 — 214 days from this build. The longest-supported line currently published is 2609, to March 28, 2028.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
What does Microsoft Configuration Manager end of life mean for your organization?
When a version of Microsoft Configuration Manager reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL Microsoft Configuration Manager should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Microsoft Configuration Manager reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Microsoft Configuration Manager versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Microsoft Configuration Manager has 5 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Microsoft Configuration Manager is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."