Lifecycle

Technology lifecycle and end of support

Which versions are supported, which receive security fixes only and which have ended, year by year across vendors, with the source of each date and the step that follows.

Read on

What the catalogue holds

Open a product to see each of its versions year by year, and a version to see its dates, its phases and where each date comes from. A product has no state of its own: its versions are counted by the state each is in.

25products
516versions
155end-of-life dates from the vendor's own publication
333end-of-life dates from the community source only
19versions whose source publishes no end date: 15 supported today, 4 on security fixes only
9versions with no end date from any source
Not covered, and why
  • Microsoft 365 Apps (Microsoft). Microsoft's lifecycle page says it follows the Modern Lifecycle Policy and shows "In Support" with no retirement date. It is serviced continuously by update channel, so there is no version of the product to give an end of support to. The page links a list of supported versions by channel; that list was not read into this catalogue. Where that was read.
  • Power Platform (Microsoft). An evergreen service with no versions to give an end of support to; the retirement of a feature is not the end of support of the product. Looked at: learn.microsoft.com/lifecycle/products/ has no page named power-platform, microsoft-power-platform, power-apps or power-automate (each answered 404 on 2026-11-12).
  • TypeScript (Microsoft). No versioned lifecycle source was found. Looked at on 2026-11-12: endoflife.date lists no typescript product (api/all.json, and api/typescript.json answered 404), and learn.microsoft.com/lifecycle/products/typescript answered 404. Where that was read.
  • Azure App Service and Azure Functions language runtimes (Microsoft). No source was read for them in this work: no machine-readable vendor feed was identified, and no Microsoft Learn page was recorded by hand.

Products, versions and years

25 products with 516 versions shown, of 516 versions in the catalogue.Read on . “Today” is the day of that reading.
Every product of the catalogue under its category, with its vendor, the number of its versions, and those versions counted by the state each is in.
ProductVendorVersionsVersions by state
Client application 1 product, 6 versions
OfficeMicrosoft6 versions2 Supported4 Ended
Container orchestration 2 products, 39 versions
KubernetesCloud Native Computing Foundation22 versions3 Supported19 Ended
Azure Kubernetes ServiceMicrosoft17 versions4 Supported3 Extended10 Ended
Database 3 products, 91 versions
SQL ServerMicrosoft36 versions2 Supported2 Security only3 Extended29 Ended
MySQLOracle23 versions2 Supported1 Supported, no end date published20 Ended
PostgreSQLPostgreSQL Global Development Group32 versions5 Supported27 Ended
Developer tool 2 products, 69 versions
Azure DevOps ServerMicrosoft15 versions3 Supported1 Supported, no end date published6 Security only5 Ended
Visual StudioMicrosoft54 versions4 Supported1 Supported, no end date published49 Ended
Framework 3 products, 32 versions
AngularGoogle14 versions1 Supported2 Security only11 Ended
ReactMeta5 versions1 Supported, no end date published4 Security only
.NET FrameworkMicrosoft13 versions2 Supported5 Supported, no end date published6 Ended
Infrastructure tool 2 products, 44 versions
Docker EngineDocker26 versions1 Supported1 Supported, no end date published24 Ended
TerraformHashiCorp18 versions2 Supported, no end date published16 Ended
Language 2 products, 16 versions
PowerShellMicrosoft10 versions1 Supported9 Ended
Windows PowerShellMicrosoft6 versions1 Supported, no end date published5 Ended
Operating system 6 products, 158 versions
UbuntuCanonical46 versions4 Supported2 Extended39 Ended1 Unreleased
DebianDebian20 versions1 Supported1 Security only3 Extended13 Ended2 Unknown
WindowsMicrosoft49 versions11 Supported1 Security only2 Extended35 Ended
Windows ServerMicrosoft20 versions1 Supported3 Security only16 Ended
Windows Server CoreMicrosoft16 versions1 Supported3 Security only12 Ended
Red Hat Enterprise LinuxRed Hat7 versions2 Supported1 Security only1 Extended3 Ended
Runtime 2 products, 44 versions
.NETMicrosoft14 versions2 Supported12 Ended
Node.jsOpenJS Foundation30 versions1 Supported2 Security only26 Ended1 Unreleased
Server product 2 products, 17 versions
Exchange ServerMicrosoft11 versions1 Supported, no end date published10 Ended
SharePoint ServerMicrosoft6 versions1 Supported, no end date published5 Ended

What each state means

  • SupportedInside the vendor's active or mainstream support, with an end date published.
  • Supported, no end date publishedA named source says the version is in support and publishes no end date. No last year is drawn for it.
  • Security onlyMaintenance: past mainstream support and before end of life. Security fixes only.
  • ExtendedPast end of life, inside an extended or paid support period the vendor publishes.
  • EndedPast the last day of any standard support.
  • UnreleasedBefore the release date the source gives.
  • UnknownNo source gives an end-of-life date or says there is none. It is never shown as supported.
  • Ended, day not publishedThe version has ended and no source gives the day. Shown for the years before the reading; it is never a statement of when support stopped.

In a product's table, a cell is the state on 1 January of its year, or on the release day when the version is released in that year. A line under the state says when it changes inside the year, with the date. A date is the last day of its phase.

Method and limits

A row is one version, never a product family. A family has no single support state, so a product is shown as its versions counted by state and never as one colour.Evergreen services have no versioned end of support. Power Platform and other software delivered as a continuously updated service have no version to run out, so they have no row here.A feature retirement is not a product's end of support. When a vendor retires one feature of a service, the service is still supported. That is a different fact and it is not drawn as an end of life.Unknown is shown as unknown. Where no source gives a date, the page says so. A date is never filled in from the calendar, and an unknown state is never shown as supported.No end date published is said only on evidence. It is shown where a named source states that the version is in support and publishes no end date, and nowhere else.

Where the dates come from

A vendor's own publication is the authority. The community source adds versions no vendor feed covers, is always named, and never replaces a vendor's date. Where the two disagree, both are shown.
The sources of the catalogue, the authority of each, and what happened to it in this reading.
SourceAuthorityThis reading
distro-info-data: debian.csvDebian (distro-info-data) · ISC licenceVendor sourceRead
.NET release metadata (releases-index.json)MicrosoftVendor sourceRead
endoflife.date, a community list of end-of-life datesendoflife.date · MIT licenceCommunity sourceRead
Kubernetes patch release schedule (schedule.yaml)The Kubernetes AuthorsVendor sourceRead
Azure DevOps Server lifecycleMicrosoftVendor sourceRead
Microsoft .NET Framework lifecycleMicrosoftVendor sourceRead
Ending Support in 2026MicrosoftVendor sourceRead
Exchange Server Subscription Edition lifecycleMicrosoftVendor sourceRead
Microsoft Office 2016 lifecycleMicrosoftVendor sourceRead
Microsoft Office 2019 lifecycleMicrosoftVendor sourceRead
Office 2021 lifecycleMicrosoftVendor sourceRead
Office 2024 lifecycleMicrosoftVendor sourceRead
Office LTSC 2021 lifecycleMicrosoftVendor sourceRead
Office LTSC 2024 lifecycleMicrosoftVendor sourceRead
PowerShell lifecycleMicrosoftVendor sourceRead
SharePoint Server Subscription Edition lifecycleMicrosoftVendor sourceRead
Visual Studio 2017 lifecycleMicrosoftVendor sourceRead
Windows 10 Enterprise LTSC 2021 lifecycleMicrosoftVendor sourceRead
Windows Server 2016 lifecycleMicrosoftVendor sourceRead
Node.js release schedule (schedule.json)Node.js Release working groupVendor sourceRead
PostgreSQL versions (versions.json)PostgreSQL Global Development GroupVendor sourceRead
distro-info-data: ubuntu.csvDebian (distro-info-data) · ISC licenceVendor sourceRead

Microsoft versions followed closely

The Microsoft server and client versions this site's readers run most, with the step that follows each.

Community dates read

No longer supported

Running any of these means running without security updates.

  • Windows11 23H2 Enterprise

    End of support · Microsoft

    Source: Microsoft, Ending Support in 2026, checked .

    Move to 11 26H2 Enterprise, supported until

    Ask us about this upgradeMicrosoft's lifecycle page
  • .NET9

    End of support · Microsoft

    Source: Microsoft, Microsoft .NET and .NET Core lifecycle, checked . Microsoft's list "Ending Support in 2026", consulted the same day, gives 12 May 2026 for this version.

    Move to 11, supported until

    Microsoft's lifecycle page
  • .NET8LTS

    End of support · Microsoft

    Source: Microsoft, Ending Support in 2026, checked .

    Move to 10, supported until

    Microsoft's lifecycle page
  • PowerShell7.5

    End of support · Microsoft

    Source: Microsoft, PowerShell lifecycle, checked .

    Move to 7.6, supported until

    Microsoft's lifecycle page
  • PowerShell7.4LTS

    End of support · Microsoft

    Source: Microsoft, Ending Support in 2026, checked .

    Move to 7.6, supported until

    Microsoft's lifecycle page
  • Windows11 24H2 Home/Pro

    End of support · Microsoft

    Source: Microsoft, Ending Support in 2026, checked .

    Move to 11 26H2 Home/Pro, supported until

    Ask us about this upgradeMicrosoft's lifecycle page
  • Office2021

    End of support · Microsoft

    Source: Microsoft, Ending Support in 2026, checked .

    Move to 2024, supported until

    Ask us about this upgradeMicrosoft's lifecycle page
  • Visual Studio18.10

    End of support · community source

    From endoflife.date, a community list, read . Not verified against Microsoft.

    Microsoft's lifecycle page
  • Visual Studio18.9

    End of support · community source

    From endoflife.date, a community list, read . Not verified against Microsoft.

    Microsoft's lifecycle page
  • Azure Kubernetes Service1.33

    End of support · community source

    From endoflife.date, a community list, read . Not verified against Microsoft.

    Move to 1.37, supported until

    Microsoft's lifecycle page
  • SharePoint Server2019

    End of support · Microsoft

    Source: Microsoft, Ending Support in 2026, checked .

    No supported successor version: the path is Subscription Edition or the cloud service.

    MigrateMicrosoft's lifecycle page
  • SharePoint Server2016

    End of support · Microsoft

    Source: Microsoft, Ending Support in 2026, checked .

    No supported successor version: the path is Subscription Edition or the cloud service.

    MigrateMicrosoft's lifecycle page
  • SQL Server2016

    End of support · Microsoft

    Source: Microsoft, Ending Support in 2026, checked .

    Move to 2025, supported until

    Microsoft's lifecycle page
  • Windows Server23H2 Annual Channel

    End of support · community source

    From endoflife.date, a community list, read . Not verified against Microsoft.

    Ask us about this upgradeMicrosoft's lifecycle page

Support ending next

Still supported. The date is the deadline to plan the move against.

  • Visual Studio15.9

    End of support · Microsoft

    Source: Microsoft, Visual Studio 2017 lifecycle, checked .

    Move to 17.14, supported until

    Microsoft's lifecycle page
  • Azure Kubernetes Service1.35

    End of support · community source

    From endoflife.date, a community list, read . Not verified against Microsoft.

    Move to 1.37, supported until

    Microsoft's lifecycle page
  • Windows10 21H2 LTSCLTS

    End of support · Microsoft

    Source: Microsoft, Windows 10 Enterprise LTSC 2021 lifecycle, checked .

    Move to 11 24H2 LTSC, supported until

    Ask us about this upgradeMicrosoft's lifecycle page
  • Windows Server2016LTS

    End of support · Microsoft

    Source: Microsoft, Windows Server 2016 lifecycle, checked .

    Move to 2025, supported until

    Ask us about this upgradeMicrosoft's lifecycle page
  • Windows Server Core2016LTS

    End of support · community source

    From endoflife.date, a community list, read . Not verified against Microsoft.

    Move to 2025, supported until

    Ask us about this upgradeMicrosoft's lifecycle page
  • .NET Framework4.6.2

    End of support · Microsoft

    Source: Microsoft, Microsoft .NET Framework lifecycle, checked .

    Microsoft's lifecycle page
  • Azure DevOps Server2017

    End of support · community source

    From endoflife.date, a community list, read . Not verified against Microsoft.

    Move to 2022.2, supported until

    Microsoft's lifecycle page
  • Azure Kubernetes Service1.34

    End of support · community source

    From endoflife.date, a community list, read . Not verified against Microsoft.

    Move to 1.37, supported until

    Microsoft's lifecycle page

Two kinds of date are shown and kept apart. A date marked Microsoft was read on Microsoft's own lifecycle pages, and each one names the page and the day it was consulted. A date marked community source comes from endoflife.date, a community project under the MIT licence, which this site reads once a day: it is not Microsoft's publication, and a version that carries only that date has not been verified against Microsoft. Which versions are listed, and under which heading, follows the community dates, and the date beside a recommended successor is a community date too. Before you act on any date, confirm it on the official Microsoft lifecycle site.

This tool is free, and it stays free. If it saved you time, you can support its maintenance.

Buy me a coffee (opens in a new tab)João Lívio's page on buymeacoffee.com