This article describes how to use Azure DevOps to create a project and establish a repository for source code. You can manage and structure each project to support your business needs. Each project you create provides boundaries to isolate data from other projects. To learn more about projects and when to create one, see About projects and scaling your organization.
Important
To view the content available for your platform, make sure that you select the correct version of this article from the version selector which is located above the table of contents. Feature support differs depending on the on-premises version of TFS you are using. .
To learn which on-premises version you are using, see What platform/version am I using?
If you don't want to create a project in Azure DevOps, you can create Azure DevOps Projects.
You create a project within a project collection. If you haven't created a project collection yet, do that now. For more information, see Create a project collection.
You must be a member of the Project Collection Administrators group or have the Create new projects permission set to Allow. For more information, see Change project collection-level permissions.
Ask your administrator about the following resources and get additional permissions as needed:
Which project collection should you connect to when you create your project? If you installed TFS using the Basic Server Configuration Wizard, you have only one project collection named DefaultCollection. Unless you support hundreds of projects, you should create all your projects within a single project collection. If you need to create additional collections, see Manage project collections.
Have you configured SQL Server Analysis Services and SQL Server Reporting Services for the deployment? If so, ask your administrator to add you as a member of the Team Foundation Content Managers group. You must be a member of this group on the server that hosts SQL Server Reporting Services. Without these permissions, you can't create a project. For more information, see Grant permissions to view or create SQL Server reports.
Have you configured a SharePoint Web application for your deployment? You can configure a SharePoint portal when you create your project. To do so, contact your SharePoint administrator to give you Full Control permissions on the server that hosts SharePoint Products. Otherwise, you can skip this step and configure a portal at a later time.
Choose the Current page tab for information on creating a project.
Creating a project from the web portal is supported for TFS 2015.2 and later versions. For earlier versions, use Team Explorer to create a project.
Important
When you create a project from the web portal, several process template files are ignored. Specifically, the files that would create a Report Manager site and a SharePoint project portal aren't supported. You can still set up Reporting and SharePoint manually after project creation.
If you have TFS 2015.2 or a later version, select the gear button to open the Projects page.
Then choose New project.
Otherwise, for TFS 2015 or TFS 2015.1, open the administration overview page by choosing
settings. Then, select Server settings and choose New project.
Select the collection administration page for the collection you want to create the project in from the left pane. Select Create a new project.
Enter information into the form provided. Provide a name for your new project, a short description, and select its initial source control type and work item tracking process.
Azure DevOps CLI commands aren't supported for Azure DevOps Server on-premises versions.
You can create a project from Visual Studio/Team Explorer after you've connected to an on-premises Azure DevOps Server.
Open the same version of Visual Studio as the version of TFS that you're connecting to. If you don't see the Team Explorer pane, select View > Team Explorer from the menu.
Connect to the server and project collection where you want to create your project.
Connect from a client that is at the same version level as TFS. That is, you must connect to TFS 2015 from a version of Visual Studio 2015.
Tip
If you run Team Explorer from a server that hosts SharePoint Products and SQL Server Reporting Services, you might need to run Visual Studio as an administrator.
If it's your first time connecting to TFS, you need to add TFS to the list of recognized servers.
Open the New Project Wizard.
Name the project. Don't specify more than 64 characters.
Choose a process template. For a comparison of the default process templates, see Choose a process.
Choose your version control, either Git distributed repositories or TFVC, one centralized repository.
Unless your project collection supports a SharePoint project portal, you're done.
If the Next button is active, you can configure your project portal.
If you have a problem, you receive an error message and a link to the project creation log. See Troubleshoot creating a project for specific errors and exceptions.
When you're finished, you can see your project in Team Explorer. You can also choose the Web Access link to connect to your project from the web portal.
Azure DevOps CLI commands aren't supported for Azure DevOps Server on-premises versions.
From Team Explorer, you can view a list of projects by connecting to an organization or server. For more information, see Connect to a project.
Visual Studio 2019
Visual Studio 2017
Visual Studio 2015
Add a repository to your project
From the admin context of the web portal, you can add additional repositories to a project. Add either Git (distributed) or TFVC (centralized) repositories. You can create many Git repositories, but only a single TFVC repository for a project. Additional steps to address permissions may be required. For more information, see Use Git and TFVC repos in the same project.
Note
The ability to work from both Git and TFVC repositories from the same project is supported when you connect to TFS 2015.1 and later versions.
Then choose New project.
