---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-service-management
Release :
- australia
ft:locale :
- en-US
ft:publication_title :
- Australia IT Service Management
ft:clusterId :
- itsm
bundleId :
- itsm
workflow :
- Technology
---
# Managing Azure DevOps artifacts
# Managing Azure DevOps artifacts {#ariaid-title1}
Release version: Australia
Updated March 12, 2026
 3 minutes to read
Summarize
 Summarized using AI
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.
## Summary of Managing Azure DevOps Artifacts
Managing Azure DevOps artifacts through DevOps Change Velocity simplifies the process of tracking and importing artifacts from Azure DevOps build pipelines.
This feature supports various artifact sources, allowing customers to efficiently manage their packages and historical data.
Show full answer Show less
## Key Features
* **Automatic Artifact Creation:** Build artifacts published via the *PublishBuildArtifacts* and *PublishPipelineArtifacts* tasks are automatically created in your DevOps Change Velocity instance.
* **Historical Data Import:** Customers can import historical data for build artifacts without needing extension-based registration if the aforementioned tasks are utilized.
* **Azure Artifacts Support:** Only Universal packages can be imported and tracked through Azure DevOps Artifacts, available from DevOps version 1.35 and later.
* **Scheduled Job for Artifact Association:** Azure Artifact information is linked to a build pipeline within 24 hours via a scheduled job, which is performance-intensive and should not be run frequently.
* **Real-time Tracking:** To track artifact repositories in real-time, the Track column must be set to True.
## Key Outcomes
By managing Azure DevOps artifacts, customers can expect streamlined tracking of their builds and releases, improved rollback capabilities, and efficient artifact organization. This ensures that all necessary information, such as work items and change data, is readily accessible for both current and historical artifacts.
Limitations include support for project-specific feeds with a maximum of 4000 feeds, 800 packages, and a pipeline limit of 200 packages published. Artifacts not linked to any pipeline are not supported.
DevOps Change Velocity makes it easy to manage artifacts published through Azure DevOps build pipelines. You can import and track these artifacts and manage the packages in DevOps Change Velocity.
Types of artifact sources supported by DevOps Change Velocity:
* Build
* Azure Artifacts
{#importing-azure-artifacts__ul_qzj_wzx_31c}
## Build Artifacts {#importing-azure-artifacts__section_hfh_r2t_25b}
Build and pipeline artifacts published using the Publish Build Artifacts (PublishBuildArtifacts) and Publish Pipeline Artifacts (PublishPipelineArtifacts) tasks respectively on the Azure DevOps are automatically created in your DevOps Change Velocity instance. You can also import historical data for build artifacts.
Build artifacts created using the Publish Build Artifacts task will
be part of the artifact repository whose name will be defaulted to the build pipeline name.
Note:
If two artifacts with the same name, belonging to the same repository, and having different versions are used as release triggers for a release pipeline, then the related lists (like work items, commits, test summaries, and so on) will include DevOps data related to both the artifact versions when a change exists in the release pipeline. For example, if artifact-1.0 and artifact-2.0 are release triggers to manage rollback scenarios in deployment, then change (if part of the release pipeline) will include related lists data for both the versions.
You can also continue to leverage the existing Extension-based artifact registration and import. For more information, see [Use the ServiceNow DevOps extension for Azure DevOps and Azure DevOps custom actions](https://www.servicenow.com/docs/1xZN23j5GCbNyKMulIHDzA#config-dev-ops-extensions-azure "Install and configure DevOps extension for Azure DevOps to send build and release notifications from your Azure pipeline to DevOps Change Velocity.") and [Artifacts and packages](https://www.servicenow.com/docs/ZGDdOnEWq330BJleYqX2_g "Artifacts and packages enable DevOps Change Velocity to track development and testing activities across a wide range of deployment and release models. This feature ensures that pipeline activity stored in the DevOps data model can be retrieved and applied when artifacts are created and released at different times or in different pipelines.").
Important:
Using Extension-based artifact registration isn't required if the PublishBuildArtifacts and PublishPipelineArtifacts tasks mentioned above are used.
## Azure Artifacts {#importing-azure-artifacts__section_b1w_42t_25b}
You can import and track the artifacts to your DevOps Change Velocity instance. You can import Azure DevOps artifacts that are published to the Azure Artifacts using the Universal Package task only.
Note:
Only Universal packages are currently supported for importing and tracking.
(DevOps 1.35 and later versions) The Feed connection alias field is available on the Azure DevOps Tools form. This field is auto-populated with an alias for the feed connection. For more information about connecting a DevOps tool, see [Integrating DevOps Change Velocity with third party tools](https://www.servicenow.com/docs/pViQYW50q3XmI0CgMeO7rA "Integrate your orchestration, planning, coding, artifact, software quality, and security tools with DevOps Change Velocity for end to end change traceability and automation.").
After upgrade, to select and add the artifact repositories using App Onboarding, you must select Discover to discover existing artifact repositories. The records are added to the Artifact Repositories
related list. For more information about the adding artifact repositories, see [Associate tool objects to applications - Workspace](https://www.servicenow.com/docs/d~RLHHIdnkfXhP1np3FsoQ "After creating an application, you can associate plans, repositories, and pipelines with it. Applications group plans, repositories, and pipelines from DevOps tools, which provides traceability to user stories, commits, test results, and so on.").
For tracking the artifact repositories, change the value of the Track
column to True (default value, False).
When an Azure Artifact is published via the Universal Package Task, the artifact information is associated with a build pipeline within 24 hours using the ADO Artifacts Daily scheduled job.
Note:
* As Azure DevOps Artifact creation is not dependent on Build Pipeline completion. If Azure DevOps Artifact is used as Trigger for a Release Pipeline, it would be triggered even if Build pipeline is pending completion due to a change request.
* The scheduled job is executed every 24 hours by default and can also be executed on-demand. However, as the scheduled job is performance intensive, it shouldn't be executed frequently.
{#importing-azure-artifacts__ul_kbn_yjq_g5b}
The following points must be considered while importing Azure DevOps artifacts:
1. Artifacts can't be published from the Release Pipelines due to Azure DevOps limitations.
2. Artifact Repositories are tracked as follows:
* Historical Import of Azure DevOps artifacts is accomplished using the App Onboarding. For more information, see [Associate tool objects to applications - Workspace](https://www.servicenow.com/docs/d~RLHHIdnkfXhP1np3FsoQ "After creating an application, you can associate plans, repositories, and pipelines with it. Applications group plans, repositories, and pipelines from DevOps tools, which provides traceability to user stories, commits, test results, and so on.").
* For real-time tracking of the artifacts, the value for the Track column must be changed to True (default value, False). Otherwise, the Feed or Artifact Repository won't be tracked.
{#importing-azure-artifacts__ul_rlk_vzl_25b}
3. The application supports the project-specific feeds but not the Organization specific feeds. Azure DevOps artifacts when published through Azure DevOps pipeline are only supported.
4. Azure DevOps artifacts not linked to any build or release pipeline (orphan artifacts) aren't supported.
5. Azure DevOps Artifacts are stored in the following format:
* Azure DevOps artifact linked to only Build Pipeline (or) Build and Release Pipeline:
<artifact-name>-<1.build-number.0> (Build Number of Build Pipeline)
* Azure DevOps artifact linked only to Release Pipeline:
<artifact-name>-<1.build-number.0> (Build Number of Release Pipeline)
{#importing-azure-artifacts__ul_jn1_fzl_25b}
{#importing-azure-artifacts__ol_am1_w2t_25b}
## Azure DevOps Artifact mapping with DevOps Change Velocity {#importing-azure-artifacts__section_ik5_1cm_25b}
The following table explains the mapping of Azure DevOps artifacts with ServiceNow DevOps fields:{#importing-azure-artifacts__table_cx5_zcm_25b__entry__2}
| Azure DevOps Artifact | DevOps Change Velocity |
|-|-|
| Feeds | Artifact Repositories |
| Packages | Artifacts |
| Provenance/build number | Versions |
[ ]
{#importing-azure-artifacts__table_cx5_zcm_25b}
## Limitations {#importing-azure-artifacts__section_knx_mrt_25b}
* Azure DevOps Artifact Project with 4000 Feeds (or less) is supported.
* Azure DevOps artifact Feed with 800 packages or artifacts (or less) is supported.
* Azure DevOps pipeline with 200 packages or artifacts (or less) publishing is supported.
{#importing-azure-artifacts__ul_b3k_nrt_25b}