EOL/EOS Dates

Woodard, Matthew 20 Reputation points
2024-08-26T22:01:44.7166667+00:00

I am currently conducting an audit of the software versions used in our organization to ensure compliance and maintain our systems' security and stability.

As part of this process, I am reaching out to inquire about the End of Life (EOL) dates for several different Microsoft Edge versions.

Unfortunately, I was unable to locate this information, explicitly, on your website or through other available resources.
What I do see is an explanation of the lifecycle and release dates. There is a table with support timeframes. In the case of listing EOL dates for reporting purposes, is it appropriate to take the release date, add the correct timeframe and list that as the EOL/EOS date?

If there are any additional details or documentation available that could assist us in understanding the lifecycle of these software versions, I would be grateful if you could share them.

Thank you for your support and prompt attention to this matter. Please let me know if you require any further information from our side to facilitate this request.

Thank you,

Matthew Woodard

Microsoft Edge
Microsoft Edge
A Microsoft cross-platform web browser that provides privacy, learning, and accessibility tools.
2,311 questions
0 comments No comments
{count} votes

Accepted answer
  1. Marcin Policht 23,545 Reputation points MVP
    2024-08-26T22:19:17.33+00:00

    You are correct - it would be appropriate to take the release date of a Microsoft Edge version and add the correct support timeframe to estimate the End of Life (EOL) or End of Support (EOS) date. Microsoft typically follows a fixed lifecycle policy for Edge, where each version receives security updates and support for a defined period.

    For example, Microsoft Edge Stable usually receives updates every 4 weeks, and support continues as long as a new version is available, meaning the lifecycle is tied to the release cycle rather than fixed dates. The EOL for each version can be calculated based on when the next stable version is released.

    For information regarding past versions, refer to https://learn.microsoft.com/en-us/deployedge/microsoft-edge-relnote-archive-stable-channel?source=recommendations


    If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

    hth

    Marcin

    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Jinxin Wang (Shanghai Wicresoft Co Ltd) 2,175 Reputation points Microsoft Vendor
    2024-08-27T06:29:31.96+00:00

    Hi @Woodard, Matthew,

    I read your description. I can provide you with some documents to understand the lifecycle and release plan of Microsoft Edge.

    Microsoft provides four options, called channels, to manage how often Microsoft Edge is updated with new features. For more information about our channels, their release cycle, and support levels, see the Channel overview. The table of the link lists the planned and actual release dates for major releases in the Beta, Stable, and Extended Stable channels. Please note that release dates are approximate and might vary based on build status. You can also refer to this link to view the Microsoft Edge Lifecycle Policy.

    As for the End of Life (EOL) or End of Support (EOS) date of each version of Edge, Microsoft has not added detailed information to the document. You can also refer to the archived release notes before the stable version provided by Marcin Policht.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    Best Regards,

    Jinxin Wang

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.