User and permissions management FAQs
Azure DevOps Services | Azure DevOps Server 2020 | Azure DevOps Server 2019 | TFS 2018 - TFS 2013
Learn the answers to the following frequently asked questions (FAQs) about user and permissions management in Azure DevOps. FAQs are grouped by the following subjects:
- General permissions
- Visual Studio subscriptions
- User access
- Change app access policies
- Leave your organization
- Group-based licensing
- Add members to projects
Q: What happens if I forget my password?
A: You can recover your Microsoft account password or recover your work or school account password if your organization turned on this feature. Otherwise, contact your Azure Active Directory administrator to recover your work or school account.
Q: Why can't I manage users?
A: You must be a Project Collection Administrator or organization Owner to manage users at the organization level. To get added, see Set permissions at the project- or collection-level
Q: How do I find the organization Owner?
If you have at least Basic access, you can find the current owner in your organization settings.
Go to your Organization settings.
Find the current owner.
Q: How do I find a Project Collection Administrator?
A: If you have at least Basic access, you can find your Project Collection Administrator in your organization's security settings.
For more information, see Show members of the Project Collection Administrators group.
For more information, see Show members of the Project Administrators group.
Visual Studio subscriptions
Q: When do I select "Visual Studio/MSDN Subscriber"?
A: Assign this access level to users who have active, valid Visual Studio subscriptions. Azure DevOps automatically recognizes and validates Visual Studio subscribers who have Azure DevOps as a benefit. You need the email address that's associated with the subscription.
If the user doesn't have a valid, active Visual Studio subscription, they can work only as a Stakeholder.
Q: Which Visual Studio subscriptions can I use with Azure DevOps?
Q: Why won't my Visual Studio subscription validate?
Q: Why do Visual Studio subscriber access levels change after a subscriber signs in?
A: Azure DevOps recognizes Visual Studio subscribers. Users automatically have access, based on their subscription, not on the current access level assigned to the user.
Q: What happens if a user's subscription expires?
A: If no other access levels are available, users can work as Stakeholders. To restore access, a user must renew their subscription.
Q: What does "Last Access" mean in the All Users view?
The value in Last Access is the last date a user accessed any resources or services. Accessing Azure DevOps includes using organizationname.visualstudio.com directly and using resources or services indirectly. For example, you might use the Azure Artifacts extension, or you can push code to Azure DevOps from a Git command line or IDE.
Q: Can a user who has paid for Basic access join other organizations?
A: No, a user can join only the organization for which the user has paid for Basic access. But a user can join any organization where free users with Basic access are still available. The user can also join as a user with Stakeholder access for free.
Q: Why can't users access some features?
A: Make sure that users have the correct access level assigned to them.
Some features are available only as extensions. You need to install these extensions. Most extensions require you to have at least Basic access, not Stakeholder access. Check the extension's description in the Visual Studio Marketplace, Azure DevOps tab.
For example, to search your code, you can install the free Code Search extension, but you need at least Basic access to use the extension.
To help your team improve app quality, you can install the free Test & Feedback extension, but you get different capabilities based on your access level and whether you work offline or connected to Azure DevOps Services.
Some Visual Studio subscribers can use this feature for free, but Basic users need to upgrade to Basic + Test Plans access before they can create test plans.
- Learn how to get extensions for Azure DevOps.
- Learn how to get extensions for Azure DevOps Server.
- Learn how to buy access to Azure DevOps Server Test.
Q: Why does a user lose access to some features?
A: A user can lose access for the following reasons (although the user can continue to work as a Stakeholder):
The user's Visual Studio subscription has expired. Meanwhile, the user can work as a Stakeholder, or you can give the user Basic access until the user renews their subscription. After the user signs in, Azure DevOps restores access automatically.
The Azure subscription used for billing is no longer active. All purchases made with this subscription are affected, including Visual Studio subscriptions. To fix this issue, visit the Azure account portal.
The Azure subscription used for billing was removed from your organization. Learn more about linking your organization.
Your organization has more users with Basic access than the number of users that you're paying for in Azure. Your organization includes five free users with Basic access. If you need to add more users with Basic access, you can pay for these users.
Otherwise, on the first day of the calendar month, users who haven't signed in to your organization for the longest time lose access first. If your organization has users who don't need access anymore, remove them from your organization.
Q: How does my user account inherit permissions from other Azure AD groups?
A: If a user is in more than one Azure AD group, a DENY permission set in one group applies to the user in all groups the user is in. Because the permission is set to DENY for the user at the lowest possible level, the user's usage of the resource is affected in all groups they are in because denial always takes precedence.
For example, if a user is in the Contributor group and in the Project Administrator group and DENY is set for a specific permission in the Contributor group, that permission is denied for the user in the Project Administrator group, too. In this scenario, you can use the Not set option.
For more information about permissions states, see Permission states.
Change app access policies for your organization
Q: How do personal access tokens differ from alternate authentication credentials?
A: Personal access tokens are a more convenient and secure replacement for alternate authentication credentials. You can limit a token's use to a specific lifetime, to an organization, and to scopes of activities that the token authorizes. Learn more about personal access tokens.
Q: If I deny access to one authentication method in one organization, does that affect all the organizations that I own?
A: No, you can still use that method in all the other organizations that you own. Personal access tokens apply to specific organizations or to all organizations, based on your selection when you created the token.
Q: If I deny access to an authentication method, then allow access again, will the apps that need access continue to work?
A: Yes, those apps continue to work.
Leave your organization
Q: How do I remove myself from an organization when the owner isn't available to remove me?
A: To remove yourself from an organization, do the following steps:
Go to aex.dev.azure.com.
Select the organization, and then choose Leave.
Confirm that you want to Leave the organization.
Q: Will my users lose their access level and project membership if I remove a group rule?
A: Users in the group TestGroup lose access to group resources if the users haven't been explicitly assigned to the resources or assigned via a different group rule.
Q: Will my Azure DevOps or Azure AD group be deleted if I remove its group rule?
A: No. Your groups won't be deleted.
Q: What does the option "Remove from all project level groups" do?
A: This option removes the Azure DevOps or Azure AD group from any project-level default groups, such as Project Readers or Project Contributors.
Q: What determines the final access level if a user is in more than one group?
A: Group rule types are ranked in the following order: Subscriber > Basic + Test Plans > Basic > Stakeholder. Users always get the best access level between all the group rules, including Visual Studio subscription.
See the following examples, showing how the subscriber detection factors into group rules.
Example 1: group rule gives me more access
If I have a Visual Studio Pro subscription and I'm in a group rule that gives me Basic + Test Plans – what happens?
Expected: I get Basic + Test Plans because what the group rule gives me is greater than my subscription.
Example 2: group rule gives me the same access
I have a Visual Studio Test Pro subscription and I'm in a group rule that gives me Basic + Test Plans – what happens?
Expected: I get detected as a Visual Studio Test Pro subscriber, because the access is the same as the group rule, and I'm already paying for the Visual Studio Test Pro, so I wouldn't want to pay again.
Add members to projects
Q: Why can't I add any more members to my project?
A: Your organization is free for the first five users with Basic access. You can add unlimited Stakeholders and Visual Studio subscribers for no extra charge. After you assign all five free users with Basic access, you can continue adding Stakeholders and Visual Studio subscribers.
To add six or more users with Basic access, you need to set up billing in Azure. Then, you can pay for more users who need Basic access, return to your organization, add these users, and assign them Basic access. When billing is set up, you pay monthly for the extra users' access. And can cancel at any time.
If you need more Visual Studio subscriptions, learn how to buy subscriptions.
Q: Why can't some users sign in?
A: This problem might happen because users must sign in with Microsoft accounts unless your organization controls access with Azure Active Directory (Azure AD). If your organization is connected to Azure AD, users must be directory members to get access.
If you're an Azure AD Administrator, you can add users to the directory. If you're not an Azure AD Administrator, work with the directory administrator to add them. Learn about controlling organization access with Azure AD.
Q: Why did some users lose access to certain features?
A: Loss of access might happen for different reasons.
Q: How do I remove users from my organization?
A: Learn how to delete users across all projects in your organization. If you paid for more users but don't need their organization access anymore, you must reduce your paid users to avoid charges.
Q: Why can't I find members from my connected Azure AD, even though I'm the Azure AD global admin?
A: You're probably a guest in the Azure AD instance that backs Azure DevOps. By default, Azure AD guests can't search in Azure AD. That's why you aren't finding users in your connected Azure AD to add to your organization.
First, check to see if you're an Azure AD guest:
Go to the Settings section of your organization. Look at the lower Azure Active Directory section. Make a note of the tenant that backs your organization.
Sign in to the new Azure portal, portal.azure.com. Check your user profile in the tenant from step 1. Check the User type value shown as follows:
If you're an Azure AD guest, do one of the following steps:
- Have another Azure DevOps admin, who isn't an Azure AD guest, manage the users in Azure DevOps for you. Members of the Project Collection Administrators group inside Azure DevOps can administer users.
- Have the Azure AD admin remove you from the connected Azure AD and readd you. The admin needs to make you an Azure AD member rather than a guest. See Can Azure AD B2B users be added as members instead of guests?
- Change the User Type of the Azure AD guest by using Azure AD PowerShell. We don't advise using the following process, but it works and allows the user to query Azure AD from Azure DevOps thereafter.
PS Install-Module -Name AzureAD
Open PowerShell and run the following cmdlets.
a. Connect to Azure AD:
b. Find the objectId of the user:
PS Get-AzureADuser -SearchString "YourUPN"
c. Check the usertype attribute for this user to see if they're a guest or member:
PS Get-AzureADUser -objectId This is the result of the previous command
d. Change the usertype from member to guest:
PS Set-AzureADUser -objectId <replacethe object ID for the result of the command to search> -UserType Member
Q: Why don't users appear or disappear promptly in Azure DevOps after I add or delete them in the Users hub?
A: If you experience delays finding new users or having deleted users promptly removed from Azure DevOps (for example, in drop-down lists and groups) after you add or delete users, file a problem report on Developer Community so we can investigate.
Q: Why do I have to choose between a "work or school account" and my "personal account"?
A: This happens when you sign in with an email address (for example, email@example.com) that's shared by your personal Microsoft account and by your work account or school account. Although both identities use the same sign-in address, they're still separate identities. The two identities have different profiles, security settings, and permissions.
Select Work or school account if you used this identity to create your organization, or if you previously signed in with this identity. Your identity is authenticated by your organization's directory in Azure AD, which controls access to your organization.
Select Personal account if you used your Microsoft account with Azure DevOps. Your identity is authenticated by the global directory for Microsoft accounts.
Q: Why can't I sign in after I select "personal Microsoft account" or "work or school account"?
A: When your sign-in address is shared by your personal Microsoft account and by your work account or school account, but your selected identity doesn't have access, you can't sign in. Although both identities use the same sign-in address, they're separate: they have different profiles, security settings, and permissions.
Sign out completely from Azure DevOps by completing the following steps. Closing your browser might not sign you out completely. Sign in again and select your other identity:
Close all browsers, including browsers that aren't running Azure DevOps.
Open a private or incognito browsing session.
Go to this URL:
You see a message that says, "Sign out in progress." After you sign out, you're redirected to the Azure DevOps @dev.azure.microsoft.com webpage.
If the sign-out page takes more than a minute to sign you out, close the browser and continue.
Sign in to Azure DevOps again. Select your other identity.
Q: How do I get help or support for Azure DevOps?
A: You have the following options for support:
- Report a problem with Azure DevOps on Developer Community.
- Provide a suggestion on Developer Community
- Get advice on Stack Overflow
- View the archives of the Azure DevOps forum on MSDN