Change the project visibility, public or private
Azure DevOps Services
Learn how to change the visibility of your project to and from public or private. Users who aren't signed in to your organization have read-only access to public projects on Azure DevOps. Private projects, on the other hand, require users to be granted access to the project and signed in to access the services. You can easily switch a private project to a public project, and vice-versa. Before you do so, review the notes provided in Private-to-public migration checklist.
Look through our migration checklist before you make an existing project public. It has tips and ideas for exposing a limited set of data, in case you don't want your entire history available.
- You must have an organization created in Azure DevOps. If you don't have one, do that now.
- As an organization owner, you can change policies and change project information. If you're not the owner, then you must be a member of the Project Collection Administrators group.
Enable anonymous access to projects for your organization
Before you can change a private project, to a public project, you must enable anonymous access for your organization.
From your web browser, sign in to Azure DevOps. You must be signed in to create a public project.
Choose Azure DevOps to open Projects. Then choose Organization settings.
Choose the Policies page, and select On for Allow public projects.
Make a private project public, or a public project private
Choose Project Settings in the sidebar.
To switch from private to public, choose Public from the Visibility menu of options.
To switch from public to private, choose Private from the Visibility menu of options.
Submit and view feedback for