Team Foundation Server (TFS) 2017 End of Life: January 11, 2027
The end of life date for Team Foundation Server (TFS) 2017 is January 11, 2027. That is the Extended End Date on Microsoft's lifecycle page for Visual Studio Team Foundation Server 2017, the last day of Extended Support. The page says the product follows the Fixed Lifecycle Policy. It gives a Start Date of November 16, 2016, a Mainstream End Date of January 11, 2022 and an Extended End Date of January 11, 2027. Team Foundation Server is the product Microsoft renamed Azure DevOps Server, so every upgrade target carries the newer name.
Key Dates at a Glance
- Team Foundation Server 2017: start 2016-11-16; mainstream end 2022-01-11; extended end 2027-01-11
- Team Foundation Server 2018: mainstream end 2023-01-10; extended end 2028-01-11
- Azure DevOps Server 2019: mainstream end 2024-04-09; extended end 2029-04-10
- Azure DevOps Server 2020: mainstream end 2025-10-14; extended end 2030-10-08
- Azure DevOps Server 2022: mainstream end 2028-01-11; extended end 2033-01-11
- Azure DevOps Server (Modern Lifecycle Policy): start 2025-12-09
- Team Foundation Server 2015: extended end 2025-10-14
- Team Foundation Server 2013: extended end 2024-04-09
- Team Foundation Server 2012: extended end 2023-01-10
- Team Foundation Server 2010: extended end 2020-07-14
- Team Foundation Server 2005: extended end 2016-07-12
Every Team Foundation Server and Azure DevOps Server version: end of life dates
Each row is from that version's own Microsoft lifecycle page. We read all eleven pages twice on the day of publication. Microsoft's pages say support dates are shown in the Pacific Time Zone, and the day here is the last supported day. On this site, the end-of-life date of a version under the Fixed Lifecycle Policy is its Extended End Date. Microsoft lists Azure DevOps Server 2022, 2020 and 2019 as one product each. This site also tracks their updates as separate versions, and the rows above use the product-level dates Microsoft publishes. Microsoft's page for Azure DevOps Server 2019 has a Releases table as well: Update 2019.1 carries the Extended End Date, and the Original Release has an earlier End Date. Live status for every version is on our Azure DevOps Server page.
What Microsoft's Fixed Lifecycle Policy says ends
Microsoft's lifecycle page says Team Foundation Server 2017 follows the Fixed Lifecycle Policy. That policy has two phases, Mainstream Support and Extended Support, and a column for what Microsoft calls Beyond End of Support.
- Mainstream Support is over. For Team Foundation Server 2017 it ended on January 11, 2022. The policy's phase table shows requests to change product design and features, and non-security updates, as available in Mainstream Support and not available after it.
- Extended Support is the phase that ends on the end date. The policy says Extended Support includes paid support and security updates at no additional cost. It also says Microsoft will not accept requests for warranty support, design changes, or new features during the Extended Support phase.
- The end date is January 11, 2027. Microsoft's Ending Support in 2027 list names Visual Studio Team Foundation Server 2017 under that day. The list says: "Upon retirement or end of support, there will be no new security updates, non-security updates, free or paid assisted support options or online technical content updates."
- Beyond End of Support. In the policy's phase table, security updates in this column are available through the Extended Security Update Program. That applies to products that have such a program. The policy says self-help online support stays available for a minimum of 12 months after a product reaches the end of its support.
Nothing on Microsoft's lifecycle pages says an installed server stops running on that day. What ends is the supply of updates and assisted support.
The policy ties support to the update level. It says both the Mainstream Support and Extended Support phases require a product's supported service pack to be installed to continue to receive full support. It also says that when support for a product ends, support of all the service packs for that product also ends. For Team Foundation Server 2017, the Releases table on Microsoft's page names Update 3 as the release that lasts to the Extended End Date.
Does Microsoft list Extended Security Updates for TFS 2017?
Microsoft's lifecycle page for Team Foundation Server 2017 lists none. Here is what the pages show.
- The Team Foundation Server 2017 page. It has one Support Dates row with a Start Date, a Mainstream End Date and an Extended End Date. It has a Releases table with two rows, Update 3 and Original Release. It has no Extended Security Update row and no row dated after January 11, 2027.
- The policy. The Fixed Lifecycle Policy says security updates beyond end of support are available through the Extended Security Update Program. The policy page does not name the products that have such a program.
- The Extended Security Updates FAQ. Microsoft's Lifecycle FAQ on Extended Security Updates did not name Team Foundation Server or Azure DevOps Server when we read it.
We report what Microsoft's pages list. If Microsoft adds an Extended Security Update row for Team Foundation Server 2017, it will appear on the product's lifecycle page and we will update this guide. Until then, plan on what Microsoft's 2027 list says: no new security updates after end of support. The same list says customers with questions about support for a product should contact their Microsoft Account Representative.
Team Foundation Server and Azure DevOps Server are one product line
Microsoft's product information page says Azure DevOps Server was previously named Visual Studio Team Foundation Server (TFS). The lifecycle pages show where the name changes. The 2018 version is listed as Visual Studio Team Foundation Server 2018. The 2019 version is listed as Azure DevOps Server 2019.
The newest release drops the year. Microsoft's lifecycle page for Azure DevOps Server says it follows the Modern Lifecycle Policy. The page gives a Start Date of December 9, 2025, shows the words In Support, and lists no retirement date. The Modern Lifecycle Policy says a product remains in support if customers stay current as per the servicing and system requirements published for it. That is a different model from the fixed dates of the 2022 version and every version before it.
Your options, in Microsoft's terms
- Stay supported until the date. Team Foundation Server 2017 is in Extended Support to January 11, 2027 at the Update 3 level. Keep each server on an update level Microsoft supports.
- Upgrade on your own servers. Microsoft's upgrade guide for Azure DevOps Server says upgrades are supported only from TFS 2015 and later. TFS 2017 is inside that range. The guide says a deployment on TFS 2013 or an earlier release must first be upgraded to TFS 2015.
- Prepare the way the guide says. It lists prerequisites: review the system requirements for the target server, which may include updates to operating systems, SQL Server versions and hardware. Create a complete and consistent set of backups for all databases. It recommends a trial run in a pre-production environment for an in-place upgrade. It says the deployment is offline during the upgrade. The guide also carries an upgrade matrix, published as an image, for the path from each earlier version.
- Move to the cloud service. Microsoft's migration overview describes three approaches to Azure DevOps Services: a manual migration, the Azure DevOps Data Migration Tool, and an API-based migration. The Data Migration Tool process starts with prerequisites such as updating Azure DevOps Server to one of the two most recent releases. A TFS 2017 collection therefore needs an on-premises upgrade before that tool can move it.
- If you cannot move before the date: Microsoft's page lists no Extended Security Updates for Team Foundation Server 2017. Microsoft's 2027 list says end of support means no new security updates and no free or paid assisted support options. Ask your Microsoft Account Representative what applies to your agreement, and get the answer in writing before you plan around it.
Choose the target by its dates
| Version | Lifecycle policy | Mainstream End Date | Extended End Date (end of life) |
|---|---|---|---|
| Team Foundation Server 2018 | Fixed | January 10, 2023 | January 11, 2028 |
| Azure DevOps Server 2019 | Fixed | April 9, 2024 | April 10, 2029 |
| Azure DevOps Server 2020 | Fixed | October 14, 2025 | October 8, 2030 |
| Azure DevOps Server 2022 | Fixed | January 11, 2028 | January 11, 2033 |
| Azure DevOps Server (no year in the name) | Modern | Not a phase of the Modern Lifecycle Policy | No retirement date listed |
Column names are Microsoft's. Each row is a version with a later end date than Team Foundation Server 2017. Microsoft's upgrade guide is written for the move to the newest Azure DevOps Server. The EOL Checker looks up one product and version. Our Azure DevOps Server page carries the live status and EOL Risk Score for each version.
Frequently Asked Questions
When does Team Foundation Server 2017 reach end of life?
January 11, 2027. Microsoft's lifecycle page for Visual Studio Team Foundation Server 2017 gives that day as the Extended End Date. Mainstream Support ended on January 11, 2022. Microsoft's Ending Support in 2027 list names the product under the same day.
Is Team Foundation Server 2017 still supported?
Yes, until January 11, 2027. Team Foundation Server 2017 is in the Extended Support phase of Microsoft's Fixed Lifecycle Policy. Microsoft says that phase includes paid support and security updates at no additional cost. The Releases table on Microsoft's page gives that end date to Update 3, and the Original Release row has an End Date that has already passed.
What ends when Team Foundation Server 2017 reaches end of life?
Microsoft's Ending Support in 2027 list says that upon end of support there will be no new security updates, non-security updates, free or paid assisted support options or online technical content updates. The Fixed Lifecycle Policy says self-help online support stays available for a minimum of 12 months after a product reaches the end of its support.
Does Microsoft list Extended Security Updates for Team Foundation Server 2017?
Microsoft's lifecycle page for Team Foundation Server 2017 lists none. It shows one Support Dates row and two Releases rows, and no Extended Security Update row. Ask your Microsoft Account Representative in writing before you plan around security updates after the end date.
Is Team Foundation Server the same product as Azure DevOps Server?
Yes. Microsoft's documentation says Azure DevOps Server was previously named Visual Studio Team Foundation Server (TFS). Team Foundation Server 2018 is the last version with the old name on Microsoft's lifecycle pages, and the 2019 version is named Azure DevOps Server 2019.
Can Team Foundation Server 2017 be upgraded directly to Azure DevOps Server?
Microsoft's upgrade guide says upgrades are supported only from TFS 2015 and later, so TFS 2017 is a supported source version. The guide says to review the system requirements for the target server, to create complete backups, and to run a trial upgrade in a pre-production environment. It also says the deployment is offline during the upgrade.
Can Team Foundation Server 2017 be moved to Azure DevOps Services in the cloud?
Not directly with Microsoft's Data Migration Tool. Microsoft's migration overview lists updating Azure DevOps Server to one of the two most recent releases as a prerequisite for that tool. The same page describes a manual migration and an API-based migration as the other approaches.
When does Team Foundation Server 2018 reach end of life?
January 11, 2028. That is the Extended End Date on Microsoft's lifecycle page for Visual Studio Team Foundation Server 2018. Its Mainstream Support ended on January 10, 2023.
Is Team Foundation Server 2015 still supported?
No. The Extended End Date on Microsoft's lifecycle page for Visual Studio Team Foundation Server 2015 was October 14, 2025.
Which Azure DevOps Server version has the latest end date?
Among the versions with fixed dates, Azure DevOps Server 2022 has Mainstream Support to January 11, 2028 and Extended Support to January 11, 2033. The newest release is named Azure DevOps Server, with no year. Its lifecycle page says it follows the Modern Lifecycle Policy, gives a Start Date of December 9, 2025 and lists no retirement date.
Sources
- Microsoft Lifecycle: Visual Studio Team Foundation Server 2017, the Support Dates and Releases tables
- Microsoft Lifecycle: Ending Support in 2027
- Microsoft Lifecycle: Fixed Lifecycle Policy and Modern Lifecycle Policy
- Microsoft Lifecycle FAQ: Extended Security Updates
- Microsoft Lifecycle pages for Azure DevOps Server, Azure DevOps Server 2022, 2020, 2019, and Visual Studio Team Foundation Server 2018, 2015, 2013, 2012, 2010 and 2005
- Microsoft Learn: Upgrade your deployment to the latest version of Azure DevOps Server
- Microsoft Learn: Migration overview for Azure DevOps Services
- Microsoft Learn: What's new for Azure DevOps Server
Related
- Azure DevOps Server: every tracked version, live status and EOL Risk Score
- Visual Studio 2017 end of support: the development environment of the same generation
- Microsoft's January 2027 end of support dates: the other products that end in the same two days
- System Center 2016 end of support: in the same row of Microsoft's 2027 list
- Windows Server 2016 end of life: in the next row of Microsoft's 2027 list
- EOL Checker and How we verify our dates
Vendor source for the Azure DevOps Server dates on this page: Microsoft. We read it twice a day and publish every correction. How we check dates.