FAQs - getting extensions for Azure DevOps

Azure Boards | Azure DevOps Server 2019 | TFS 2018 | TFS 2017 | TFS 2015

In this article, find frequently asked questions and answers about getting extensions for Azure DevOps. Included are FAQs about installing, requesting, assigning, and accessing extensions. You can also find links to get support.

Q: Who can install extensions for Azure DevOps?

A: The organization Owner and Project Collection Administrator can install extensions. If you don't have permissions, but you're an organization member, you can request extensions instead.

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.

  1. Go to your Organization settings.

    Open Organization settings

  2. Find the current owner.

    Find the current owner in organization information

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.

Q: Why don't I see my organization in the Visual Studio Marketplace?

A: If you don't see your organization when buying from the Visual Studio 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.

    Tip

    If you're asked to choose "work or school account" or "personal account", then 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 for the user in the organization that you want to select.

Q: Why can't I install extensions for Azure DevOps?

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

  • If you get an "already installed or requested" error check with your Project Collection Administrator or organization Owner, and ask them to assign the extension to you.

Q: What's the difference between free, preview, and paid extensions?

A: Extensions that are available during preview don't incur charges, aren't fully supported, and have no financially backed service level agreements.

Paid extensions require that you buy and assign them to users who need access but don't have it already, for example, through subscription benefits. You'll use an Azure subscription to pay for an extension. If you don't have an Azure subscription, you can create a new subscription when you install your extension. If you have multiple subscriptions, you can select the Azure subscription that you want to use.

Q: How do I get other help or support for Azure subscriptions and billing?

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

Q: What happened to my preview extension?

A: Your extension is no longer in preview and is now generally available as a paid extension, but offers a grace period before you have to buy the extension. All preview extensions will automatically convert to a free trial before you have to buy the extension.

Q: When do I choose Install for paid extensions?

A: You can just choose Install when:

  • You want to install a free or preview extension.
  • You paid for access, uninstalled the extension, and want to reinstall the extension.
  • You just need the extension for Visual Studio subscribers who have access for that extension included with their subscriptions. These subscribers get specific extensions included with their subscriptions as benefits. They can use these extensions after they're installed without paid access and assignment. You only have to buy and assign extensions for users who need access.

Q: Why can't I install extensions for TFS?

A: You can't install extensions for TFS for one of the following reasons:

Q: Why don't I see the project collection I want?

A: 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 TFS 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 TFS 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.

Q: Why doesn't the extension that I want show a download button?

A: Some extensions work only with Azure DevOps, not TFS, for one of the following reasons:

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

Q: Why can't I upload extensions to TFS?

A: You must be a member of the Team Foundation Administrators group with Edit instance-level information permissions for the Team Foundation Server where you want to upload extensions.

Q: Why can't users access extension features?

A: This can happen for 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 TFS. 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 not, assign the extension to the user.

Learn more about assigning extensions to users.

Q: How do I get support for the Visual Studio Marketplace?

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

Q: How do I get support for the Marketplace?

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