Udostępnij za pośrednictwem


Install extensions

Azure DevOps Server 2019

Install, assign, disable, and uninstall extensions, which add new features and capabilities for Azure DevOps.

For more information about extensions, see the developing and publishing overviews.

Prerequisites

Category Requirements
Permissions Member of the Project Collection Administrators group or Edit collection-level information permissions. Organization owners are automatically members of this group. If you don't have permissions, you can request extensions instead or look up a project collection administrator.
Extension sharing Private extensions shared with your organization.

Note

To use an existing Azure subscription for billing, have at least coadministrator permissions for that subscription. If you don't have permissions, an Azure Account Administrator or Service Administrator can add you as coadministrator to the Azure subscription in the Azure portal.

Your project collection reuses your Azure subscription for future Marketplace purchases. Where can I find more info about Azure billing?

Install an extension

Install an extension to your organization by doing the following steps.

  1. Go to Marketplace.visualstudio.com.

  2. Sign in using your Azure DevOps credentials.

  3. Find the extension that you want to install. Use the search box to filter the list of extensions.

    Screenshot of Selecting an extension.

  4. Select the extension and select Get or Get it free. Or, for some non-Microsoft extensions, select Get Started to show pricing information and extension-specific installation instructions.

    Screenshot of getting the extensions.

    If you don't have permission to install the extension, you can request an administrator to install it for you. Your request gets stored in Azure DevOps Server and is ready for attention from an administrator.

  5. Select Download to download the vsix file.

  6. Upload the vsix to your on premises local Marketplace. Open your Azure DevOps Server home page (https://{server}:DefaultCollection).

  7. Go to Collection settings > Browse local extensions.

    Screenshot of selection, Browse local extensions button.

  8. Select Manage extensions and then Upload the vsix file.

    Screenshot of selection, Manage extensions.

  9. Install the extension in your project collection on the Manage extensions page. Select the project collection where you want to install the extension and choose Install.

Screenshot of Select project collection and choose Install.

  1. After installation is complete, go to the project collection or return to the Marketplace to find other extensions.

Screenshot showing completed installation of extension.

High-risk extensions

Some extensions are flagged as high-risk. For more information and to understand the reasons behind this classification, see High risk extensions.

Uninstall or disable an extension


To uninstall extensions in a collection, do the following steps:

  1. Go to the local gallery management portal (http://{server}:8080/tfs/_gallery/manage).

  2. For the wanted extension, select the ellipses (...), and then select Remove.

    Screenshot showing Remove extension action.

Troubleshoot extension installation

To resolve common issues, follow these troubleshooting steps:

  • Extension fails to install:

    • Check permissions: To install extensions, ensure you're a Project Collection Administrator or have the necessary permissions granted by an administrator.
    • Verify extension compatibility: Ensure the extension is compatible with your version of Azure DevOps. Check the extension's details page for compatibility information.
    • Network issues: Verify that your network connection is stable and that there are no firewall or proxy settings blocking the installation process.
  • Extension crashes or causes errors:

    • Collect diagnostic information: If an extension crashes or causes errors, collect diagnostic information to help identify the issue. This information includes error messages, logs, and screenshots of the problem.
    • Check extension logs: Some extensions provide logs that can help diagnose issues. Check the extension's documentation for information on how to access and interpret these logs.
    • Contact support: If you can't resolve the issue, contact the extension's support team with the collected diagnostic information. Provide as much detail as possible to help them troubleshoot the problem.
  • Extension not visible after installation:

    • Refresh the page: Sometimes, the extension might not appear immediately after installation.
    • Check permissions: Ensure you have the necessary permissions to view and use the extension. Some extensions might require specific permissions to be visible.
    • Reinstall the extension: If the extension still isn't visible, try uninstalling and reinstalling it.

Frequently asked questions (FAQs)

Q: Why don't I see my organization from the Marketplace installation page?

A: If you don't see your organization when buying from the Azure DevOps Marketplace, try the following 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. 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

Azure DevOps might ask you to choose between "work or school account" or "personal account." If so, then you used an email address that's the same for a Microsoft account and a "work or school account" that your organization manages in Microsoft Entra ID. 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 an extension?

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

Q: Why can't users access extension features?

A: Users can't 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. You experience 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 information, 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 be expired. Check whether your trial expired.

    1. On your organization toolbar, select 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 isn't, assign the extension to the user.

For more information, see Assign extensions to users.

Q: What happened to my preview extension?

A: Your extension might be out of preview. After a preview period, an extension longer is generally available as a paid extension. A grace period might 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.

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

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

  • 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.
  • You might get an error that says you already installed or requested the extension. If so, check with a member of the Project Collection Administrators group and ask them to assign the extension to you. For more information, see Request an increase in permission levels.

Q: Why don't I see the project collection I want (on-premises)?

A: 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.
    Azure DevOps might ask you to choose between a "work or school organization" or "personal account." This message means that you used an email address that's the same for a Microsoft account and a "work or school account" managed by your organization in Microsoft Entra ID. 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 (on-premises)?

A: 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 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 Azure DevOps Server?

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

Next steps