The Public option is disabled in visibility section of create project page. When I move the mouse over the info icon of public option, it says that: Your enterprise is preventing you from selecting this option.
As I know, Enterprise in VSTS means the account that is currently selected, and each enterprise can contain many organizations.
My currently selected enterprise is Microsoft Account, and I can not create any public project in any organizations of my Microsoft account.
What is the problem with creating a public project from Microsoft Account and how can I create one?
Found the solution!
Go to Organization Settings ('Account Settings' for old UI of VSTS) -> Policy -> Security policies and turn on the Allow public projects.
Log in your VSTS account, and under settings|Policy
Related
Similar to Github Cloud is there a way in Azure Devops to create internal repos wherein multiple users can have access to some repos which have certain documents without adding them as users or groups to such repos? If we make RepoA as internal it should be available to all users under an org without specifically adding them.
In Azure DevOps, for public projects, any user can get access your public project and check Git repo without signing in or added as a user in your org. You can also refer to this doc: Make your private project public - Azure DevOps Services Public Project | Microsoft Learn .
If for private projects in Azure DevOps, firstly, users must be granted access to the specified private project also as Basic access level in your org via navigating to Organization Settings -> Users -> Select the specified user -> Manage user to set users' access level.
Users be with Stakeholder access level, they will not be able to use Azure Repos for your private project.
Otherwise, to set permissions for a specific repository or some specific users, navigating to Project Settings -> Repositories -> Security to manage the permissions.
You can also refer to: About access levels - Azure DevOps | Microsoft Learn and Set Git repository permissions - Azure Repos | Microsoft Learn
I want to add a group/user to an Azure DevOps project with just access to repositories and pipelines.
If I deny "View project-level information" they don't have access to the project at all.
If I allow the "View project-level information" it gives them a read-only access to the Project Settings including permissions to see users and members of other groups etc.
It seems unbelievable that such a basic security and privacy hole exists.
Am I missing something in the config because I have never seen this in any other application and I find it hard to believe that everyone else using Azure DevOps finds this acceptable.
The easiest equivalent is GitHub (that Microsoft now owns) and you can't see the project settings if you are just a contributor.
How do I give external contractors access to the project to work but prevent them from viewing the Project Settings?
There is no possibility to restrict access to the Team Project - Project Settings page. The only thing that comes close is the feature that is now in preview: Limit user visibility and collaboration to specific projects, which will enable you to restrict access to the Organization Settings. You could suggest this feature in the Microsoft Developer Community.
is a "Public" DevOps project accessible by
everyone on Azure DevOps
only by the organization members
all members of the Azure Active Directory that is linked to the organization.
What I want to achieve is 3. over 2. but not 1.
Thank you
A public project means "Anyone on the internet can view the project. Certain features like TFVC are not supported." which is the 1 in your list, this you can see when you create a new project in Azure DevOps service :
You can find more detailed informaion at the doc What is a public project?, it says "Users that aren't signed into the service have read-only access to public projects on Azure DevOps.".
What I want to achieve is 3. over 2. but not 1.
only by the organization members
all members of the Azure Active Directory that is linked to the organization.
What you are seeking for is a private project in fact, create a new private project and add the organization users to this project, or if your organization is connected to AAD then you can directly add anyone who's in the AAD to this project with no need to add them to your organization first.
This you can find more information at the doc Add members to your project.
It seems for public project to access, admin/project owner need to invite the required user.
Ref: https://learn.microsoft.com/en-us/azure/devops/organizations/public/invite-users-public?view=azure-devops
Public projects are not that public...
We are planning to use the Visual Studio Team Service for our DevOps process. But the problem is we can not give restriction in repository level. In Visual Studio Team Service , restriction can be implemented in project level, We want to create all repository in one project so that we can easily manage our scrum board. Now how can we give repository level restriction like GitHub or Bitbucket where only assigned team member can only see the repository ?
You can refer to these steps to set permission:
1.Add users to your VSTS (https://XXX.visualstudio.com/_user) (I turn off the feature of Streamlined User Management)
2.Go to your Git team project admin page and select version control (https://XXX.visualstudio.com/[teamproject]/_admin/_versioncontrol)
3.Select a repository
4.In Security page, click Add > Add user to add members
5.Grant these users Contribute and Read permission
Note: View instance-level information (For connection in Visual Studio) and View project-level information are needed too.
More information about permission, you can refer to this article: Permissions and groups defined for Team Services and TFS
You can set permissions at the repository level. Look at the "Version Control" section of the administration area.
I like VSO (Visual Studio Online) functionality and its abilities. But I want other users (anonymous) be able to view my repo of certain project.
I'was trying to work with the security stuff in project settings, but can't figure out how to set a public access to my repo.
Is it even possible?
At present, no. VSTS is not currently intended to be a public code repository like GitHub.
Update
As pointed out in the comments, public projects are an upcoming feature.
https://blogs.msdn.microsoft.com/devops/2018/04/27/vsts-public-projects-limited-preview/
You can now change project visibility to public at Azure DevOps.
First you set organization settings->Security-Policies -> Allow public projects
and then set project settings. It's well described at current Azure DevOps documentation here and here
Your best bet is to sync the two, as outlined in this post.