| ms.subservice | azure-devops-ecosystem |
|---|---|
| title | Package and Publish an Integration |
| description | How to package and publish your integration to the Visual Studio Marketplace |
| ms.assetid | 61550050-c6d7-40e1-9ea7-030b48b04e3b |
| ms.topic | how-to |
| monikerRange | <= azure-devops |
| ms.author | chcomley |
| author | chcomley |
| ms.date | 06/06/2025 |
[!INCLUDE version-lt-eq-azure-devops]
This article explains how to publish your tool, service, or product that integrates with Azure DevOps on the Visual Studio Marketplace. Publishing on the Marketplace helps users discover solutions that extend and enhance their Azure DevOps experience. The Marketplace serves as the central hub for individuals and teams to find integrations and extensions.
Browse the Marketplace to see examples of other integrations and extensions.
Note
For packaging and publishing information for extensions, see Package & Publish Extensions.
- At least one screenshot of your integration.
- Call-to-action or get started URL for users.
Note
- The term
extensionis used in referenced documentation. Extensions are another type of Marketplace item and share many similarities with integrations. - Need help getting your integration on the Marketplace? Contact us.
To organize your manifest and assets, do the following steps:
- Create a
homefolder to store required assets. - Create an
imagesfolder for:- Your integration logo (128x128 pixels)
- Screenshots (1366x768 pixels)
- Create an
overview.mdfile to describe your integration. For more information, see GitHub Flavored Markdown. - Create a
vss-integration.jsonfile, which is your Marketplace listing's manifest file. For more information, see the extension manifest reference.
Publishing to the Marketplace starts with creating a manifest file that defines your integration and its key discovery details (screenshots, logos, overview content). This information is used to present your integration to users on the Marketplace.
-
Fill your
vss-integration.jsonfile with the following JSON:[!code-javascriptJSON]
-
Update the JSON using the following references:
- 1 - description
- 2 - icon
- 3 - categories
- 4 - screenshots
- 5 - content (details)
- 6 - links
- 7 - branding
Warning
Set the public attribute to false or omit it to prevent your integration from becoming visible to all Marketplace users before you're ready.
Install or update the cross-platform CLI for Azure DevOps (tfx-cli) using npm:
npm i -g tfx-clitfx extension create --manifest-globs vss-extension.json
Note
Increment the version of your extension or integration with every update.
If you haven't updated the version in your manifest, use the --rev-version command line switch. This switch automatically increments the patch version number and saves the new version to your manifest.
[!INCLUDE Publish_extension]
Before installing an integration in an Azure DevOps organization, share it with that organization. Sharing is required for development and testing, as it's the only way to run an integration during these stages.
To share an integration do the following steps:
- Select an integration from the list of displayed items
- Select the Share button
- Specify the name of the organization to make this integration visible to. For example, to make an integration visible to the dev.azure.com/fabrikam-fiber-inc organization, specify
fabrikam-fiber-inc.
[!INCLUDE Update_extension]
For information on making your integration visible to everyone, see Make your listing public.
