About SharePoint integration

TFS 2017 | TFS 2015 | TFS 2013

SharePoint products are a valuable resource to users of Azure DevOps and Team Foundation Server (TFS). With a SharePoint site, teams can easily store and share Office documents. SharePoint sites can be configured to show all kinds of information. We expect and encourage Azure DevOps and TFS teams to use SharePoint and will continue to look for ways to make the integration of Azure DevOps and SharePoint Server and SharePoint online, be better together.

TFS 2017 and earlier versions

Since its inception in 2005, TFS has integrated with SharePoint. That integration included SharePoint site templates and automatic site provisioning as well as support for browsing document libraries from inside Visual Studio Team Explorer. This integration works for SharePoint Server 2010 and 2013. It does not integrate with SharePoint Online nor support integration with Azure DevOps Services.

With TFS 2013, TFS-SharePoint integration required you to install the TFS Extension for SharePoint on the SharePoint server and configure both servers to recognize each other. This integration provided the following features:

• Automatically create a SharePoint site when creating a team project
• Provision dashboard pages on that SharePoint site
• Install SharePoint web parts that display TFS information such as work item query results and latest build results.
• Support for browsing your SharePoint document libraries directly from Visual Studio Team Explorer.

However, you should consider the following before moving forward with this integration:

• You can create your SharePoint site using SharePoint itself. Microsoft Teams also creates a team SharePoint site for sharing information
• TFS 2017 Update 2 and later versions support Dashboards. Dashboards provide a very practical replacement for the TFS-SharePoint dashboards.
• TFS dashboards offer an extensive catalog of widgets which replace all of the SharePoint web parts offered by this integration. Additionally, you can find widgets developed by our partners from the VSTS Marketplace.
• Starting with TFS 2018, we are deprecating the tightly-coupled TFS-SharePoint integration in favor of integration using public APIs and extensibility frameworks.

You may want to ask yourself whether the integration benefits outweigh the costs of configuration.

If you are running TFS 2017 or earlier and want to configure your integration with SharePoint 2010 or 2013, read Configure SharePoint Integration - TFS 2017 and Earlier

If you are running TFS 2017, configured to integrate with SharePoint 2013, and want to upgrade to SharePoint 2016, you will need to disable SharePoint integration during the SharePoint upgrade, or your upgrade will fail. For more information, read Upgrade from SharePoint 2013 with TFS integration to SharePoint 2016.

TFS-SharePoint version compatibility

SharePoint is a collaboration product. Although SharePoint integration isn't a requirement for using SharePoint with Azure DevOps Server or TFS, some teams find SharePoint integration useful. If you want to use SharePoint Products, you must use a supported version that has the TFS extension for SharePoint installed.

Authentication

NTLM is the recommended authentication provider. Team Foundation Server Extensions for SharePoint Products doesn't support Basic authentication or anonymous authentication. In SharePoint Server 2013, Microsoft deprecated Windows classic authentication to move to claims-based authentication. TFS supports both, but for claims-based authentication, the authentication provider must be NTLM. TFS supports only NTLM-based claims.

You can configure the TFS extension for SharePoint Products on your SharePoint server in the TFS administration console.

Dashboard requirements

TFS contains dashboards that use SharePoint Products features to display team data. The dashboards that are available to you depend on the version of SharePoint Products you use:

• If you use any supported Enterprise edition of SharePoint Server, you get five dashboards that are based on Microsoft Excel.
• If you use any other SharePoint Products (including the Standard editions of SharePoint Server), you get two dashboards that are based on SQL Server Reporting Services.

SharePoint hardware requirements

If you install SharePoint Products, you must have more robust hardware than what is listed in the preceding table. For example, SharePoint Foundation 2013 requires a 64-bit, four-core CPU and a base minimum of 8 GB of system memory. If you install SharePoint 2013 on a server that's also running SQL Server, SharePoint recommends that you have 24 GB of system memory.

For complete SharePoint hardware requirements, see the following articles:

• Hardware and software requirements for SharePoint 2013 (SharePoint Foundation 2013/SharePoint Server 2013)
• Hardware and software requirements (SharePoint Foundation 2010)
• Hardware and software requirements (SharePoint Server 2010)

TFS 2018, Azure DevOps Server 2019, and later versions

Starting with TFS 2018, we no longer offer the TFS Extension for SharePoint. Additionally, we won't support TFS 2017 integration with SharePoint 2016 (the TFS Extension for SharePoint only supports Sharepoint 2013 and earlier versions). TFS 2017 and earlier versions will continue to work with their supported versions of SharePoint. For more information, read Discontinue TFS 2017 (and earlier versions) SharePoint integration.

If you are upgrading to TFS 2018 from a previous version configured to integrate with SharePoint 2010 or 2013, you will need to disable the SharePoint integration after upgrade, or your TFS SharePoint sites will fail to load. For more information, read Disable SharePoint integration after TFS 2018 upgrade.

Referenced topics

• Add and manage dashboards
• Widget catalog
• Configure SharePoint Integration: TFS 2017 and earlier versions
• Discontinue SharePoint integration: TFS 2017 and earlier versions
• Upgrade from SharePoint 2013 with TFS integration to SharePoint 2016
• VSTS Marketplace