FAQs for acquiring Azure DevOps extensions

A member of the Project Collection Administrators group can install extensions. If you don't have permissions, but you're a project member, you can request extensions instead.

See Look up a project collection administrator.

If you don't see your organization when buying from the Azure DevOps Marketplace, try these steps:

1. Check the identity that you use to sign in to the Visual Studio Marketplace. In the upper-right corner, select your user name to view your profile.
2. On the left, make sure your email address and directory are correct.
3. Close all browser windows.
4. Open a private or incognito browsing session.
5. Sign in to the Visual Studio Marketplace. Use the identity of a user in the organization that you want.

You can't install extensions for one of the following reasons.

• You must a member of the Project Collection Administrators group or are the Organization owner. If you don't have permissions, but you're a project member, you can request extensions instead.
• If you get an "already installed or requested" error check with your Project Collection Administrator, and ask them to assign the extension to you.

Users may be unable to access an extension for one of the following reasons:

• Most extensions require that users have at least Basic access, not Stakeholder. For example, you can install the free Code Search extension, but each user must have at least Basic access to search for code. To help your team improve app quality, you can install the free Test & Feedback extension, but you'll get different capabilities based on your access level and whether you work offline or connected to Azure DevOps Services or on-premises Azure DevOps Server. For more details, see the extension's description in the Visual Studio Marketplace, Azure DevOps tab.

• If you're using an organization, and you started a free extension trial, your trial might have expired. To check whether your trial expired:

  1. On your organization toolbar, go to Users.
  2. Go to the extension pane.
  3. Check for an expiration message to find if or when your extension expired.

• If you're using an organization, and you paid for this extension, make sure that you assigned this extension to users.

  1. On your organization toolbar, go to Users.
  2. Go to the extension pane.
  3. Check whether the extension is assigned to the user. If it is not, assign the extension to the user.

Learn more about assigning extensions to users.

Your extension imay have been moved out of preview. After a preview period, an extension longer is generally available as a paid extension. A grace period may be offered before you have to buy the extension. All preview extensions automatically convert to a free trial before you have to buy the extension.

You can't install extensions for Azure DevOps Server for one of the following reasons:

• You must be a member of the Project Collection Administrators group or have the Edit collection-level information permission set to Allow in the project collection where you want to install extensions. If you don't have permissions, you can request extensions instead.
• If you get an error that your extension is already installed or requested, check with a member of the Project Collection Administrators group and ask them to assign the extension to you. To learn how, see Request an increase in permission levels.

You must be a member of your project collection. Follow these steps to check your identity that you use to sign in to the Marketplace.

1. On your Azure DevOps Server web portal home page (https://{server}:8080/tfs/), go to the top-right corner of the page, and select your user name to view your profile.
2. On the left side of your profile, make sure that your email address and directory are correct.
3. Close all browser windows.
4. Open a private or incognito browsing session.
5. Sign in to your Azure DevOps Server home page (https://{server}:8080/tfs/) with the identity that's a user in the project collection where you want to install the extension.

If you're asked to choose "work or school organization" or "personal account", this means you used an email address that's the same for a Microsoft account and a "work or school account" that's managed by your organization in Azure Active Directory. Although these identities have the same email address, they're still separate identities with different profiles, security settings, and permissions. Choose the identity that's the user in your project collection.

6. From your project collection, go to the Marketplace.

Some extensions work only with Azure DevOps Services for one of the following reasons:

• The extension uses Azure DevOps features that aren't released yet for Azure DevOps Server.
• The extension manifest indicates that the extension is an integration (targets = Microsoft.Visualstudio.Services.Integration).

You must be a member of the Team Foundation Administrators group. You must also have Edit instance-level information permissions for the Azure DevOps Server where you want to upload extensions.

See these articles about Azure billing and subscriptions, the Azure Billing and Subscription FAQ, or try Azure Support.

Depending on the support you need, choose from the following:

• Billing questions -- Azure billing support
• Visual Studio subscriptions -- subscriptions support
• Help with Azure DevOps -- Azure DevOps support
• General Marketplace help -- Contact the Azure DevOps Marketplace team

Depending on the support you need, choose from the following links:

• Billing questions - Azure billing support
• Visual Studio subscriptions - subscriptions support
• Help with Azure DevOps - Azure DevOps support
• General Marketplace help - Contact the Marketplace team

Related articles

• Azure DevOps billing overview
• How to pay for Azure DevOps Server users
• How to buy Visual Studio cloud subscriptions
• Visual Studio cloud subscription billing FAQ