What is a public project?

Azure DevOps Services - Public Projects

Create a public project, make an existing project public, or work in a public project to support your development of software applications.

An Azure DevOps Services public project provides support to share code with others and to support continuous integration/continuous deployment (CI/CD) of open-source software. Users aren't required to sign in to gain read-only access to many of the services.

Public versus private projects

Projects provide a repository for source code and a place for a group of developers and teams to plan, track progress, and collaborate on building software solutions. One or more projects can be defined within an organization in Azure DevOps.

Users that aren't signed into the service have read-only access to public projects on Azure DevOps. Private projects require users to be granted access to the project and signed in to access the services.

Supported services

Non-members of a public project have read-only access to a limited set of services, specifically:

For more information, see Differences and limitations for non-members of a public project.

To add or modify code, work items, pipelines, or more, add the user as a member of the project. For an overview of services contributors have access to, see What do I get with Azure DevOps?

Get started with a public project

To get started:

To share code:

To define pipelines:

Migrate a private project to public

As the creator of a project, you can change your project's visibility from public to private and the other way around. When you choose to make a project public, all of its contents are included. You can't choose specific repositories, area paths, or build folders to keep private.

Before you change the visibility of your private project, we recommend you review Private-to-public migration checklist.