Overview of Artifacts in Azure Pipelines


In Microsoft Team Foundation Server (TFS) 2018 and previous versions, build and release pipelines are called definitions, runs are called builds, service connections are called service endpoints, stages are called environments, and jobs are called phases.

Azure Artifacts allow you to publish and consume different types of packages to your feed as well as to the public package managers (e.g. NuGet.org, npmjs.com). You can use Azure Pipelines to publish build artifacts, help store build outputs and integrate files between your pipeline steps. You can then add onto, build, test, or deploy those artifacts.


Build and Release artifacts remains available as long as that Build is retained in the system. For more information on retaining Build and Release artifacts, see the Retention Policies documentation.

Supported artifact types

The following table describes supported artifact types in Azure Pipelines.

Supported artifact types Description
Build artifacts Build artifacts are the files that your build produce. E.g. .dll, .exe, and .PDB symbols files.
Pipeline artifacts You can use pipeline artifacts to help store build outputs and move intermediate files between jobs in your pipeline. Pipeline artifacts are tied to the pipeline that they're created in. You can use them within the pipeline and download them from the build, as long as the build is retained. Pipeline artifacts are the new generation of build artifacts. They take advantage of existing services to dramatically reduce the time it takes to store outputs in your pipelines.
Maven You can publish Maven artifacts to Azure Artifacts feeds or Maven repository.
npm You can publish npm packages to Azure Artifacts feeds or npm registry.
NuGet You can publish NuGet packages to Azure Artifacts feeds or NuGet repository.
PyPI You can publish Python packages to Azure Artifacts feeds or PyPI repository.
Symbols Symbol files contain debugging information for compiled executables. You can publish symbols to symbol servers. Symbol servers enable debuggers to automatically retrieve the correct symbol files without knowing the specific product, package, or build information.
Universal packages Universal Packages store one or more files together in a single unit that has a name and version. Unlike pipeline artifacts that reside in the pipeline, Universal Packages reside within a feed in Azure Artifacts.


Artifacts can be produced by different types of sources. See Release Artifacts and Artifact sources to learn about the different types of sources and how to configure your Azure pipelines to deploy from them.

How do I publish and consume artifacts?

Each kind of artifact has a different way of being published and consumed. Some artifacts are specific to particular development tools, such as .NET, Node.js/JavaScript, Python, and Java. Other artifact types offer more generic file storage, such as pipeline artifacts and Universal Packages. Refer to the earlier table for specific guidance on each kind of artifact that we support.

To view the permissions involved, see feed permissions.

What's next?