Azure DevOpsIntermediate10 submodules

Azure Artifacts and Package Management

Create governed feeds for application and universal packages with predictable versioning, upstream controls, retention, and producer-consumer permissions.

From concept to production evidence

Publish immutable versions from trusted builds, separate read from publish rights, proxy external dependencies through approved upstream sources, and promote package views instead of overwriting versions.

Learning outcomes

  • Create and secure feeds
  • Publish NuGet, npm, Maven, Python, and universal packages
  • Choose versioning rules
  • Control upstream sources
  • Design package permissions and promotion

Azure Artifacts and Package Management end-to-end flow

Use this sequence as the operating backbone for every submodule note and hands-on exercise.

  1. 01
    Build packageAzure Artifacts and Package Management stage 1: build package with an auditable result before the next stage begins.
  2. 02
    Assign versionAzure Artifacts and Package Management stage 2: assign version with an auditable result before the next stage begins.
  3. 03
    Scan and publishAzure Artifacts and Package Management stage 3: scan and publish with an auditable result before the next stage begins.
  4. 04
    Promote viewAzure Artifacts and Package Management stage 4: promote view with an auditable result before the next stage begins.
  5. 05
    Consume with identityAzure Artifacts and Package Management stage 5: consume with identity with an auditable result before the next stage begins.
  6. 06
    Retain or deprecateAzure Artifacts and Package Management stage 6: retain or deprecate with an auditable result before the next stage begins.

Create a multi-ecosystem package feed

  1. Create feed and views
  2. Configure upstream sources
  3. Publish two package formats
  4. Assign producer and consumer permissions
  5. Promote and deprecate versions

10 full submodule notes

Read in order
01

Feeds

Feeds provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Azure Artifacts and Package Management. It is not an isolated definition: its value appears when it supports publish immutable versions from trusted builds, separate read from publish rights, proxy external dependencies through approved upstream sources, and promote package views instead of overwriting versions.

Open full notes
02

Packages

Packages moves a versioned change toward users through repeatable validation, immutable artifacts, controlled promotion, and recoverable release decisions within Azure Artifacts and Package Management. It is not an isolated definition: its value appears when it supports publish immutable versions from trusted builds, separate read from publish rights, proxy external dependencies through approved upstream sources, and promote package views instead of overwriting versions.

Open full notes
03

Universal Packages

Universal Packages moves a versioned change toward users through repeatable validation, immutable artifacts, controlled promotion, and recoverable release decisions within Azure Artifacts and Package Management. It is not an isolated definition: its value appears when it supports publish immutable versions from trusted builds, separate read from publish rights, proxy external dependencies through approved upstream sources, and promote package views instead of overwriting versions.

Open full notes
04

NuGet

NuGet provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Azure Artifacts and Package Management. It is not an isolated definition: its value appears when it supports publish immutable versions from trusted builds, separate read from publish rights, proxy external dependencies through approved upstream sources, and promote package views instead of overwriting versions.

Open full notes
05

npm

npm provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Azure Artifacts and Package Management. It is not an isolated definition: its value appears when it supports publish immutable versions from trusted builds, separate read from publish rights, proxy external dependencies through approved upstream sources, and promote package views instead of overwriting versions.

Open full notes
06

Maven

Maven provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Azure Artifacts and Package Management. It is not an isolated definition: its value appears when it supports publish immutable versions from trusted builds, separate read from publish rights, proxy external dependencies through approved upstream sources, and promote package views instead of overwriting versions.

Open full notes
07

Python packages

Python packages moves a versioned change toward users through repeatable validation, immutable artifacts, controlled promotion, and recoverable release decisions within Azure Artifacts and Package Management. It is not an isolated definition: its value appears when it supports publish immutable versions from trusted builds, separate read from publish rights, proxy external dependencies through approved upstream sources, and promote package views instead of overwriting versions.

Open full notes
08

Versioning

Versioning provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Azure Artifacts and Package Management. It is not an isolated definition: its value appears when it supports publish immutable versions from trusted builds, separate read from publish rights, proxy external dependencies through approved upstream sources, and promote package views instead of overwriting versions.

Open full notes
09

Upstream sources

Upstream sources provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Azure Artifacts and Package Management. It is not an isolated definition: its value appears when it supports publish immutable versions from trusted builds, separate read from publish rights, proxy external dependencies through approved upstream sources, and promote package views instead of overwriting versions.

Open full notes
10

Package permissions

Package permissions controls which actor may perform which action on which resource, under which conditions, with evidence that can be reviewed later within Azure Artifacts and Package Management. It is not an isolated definition: its value appears when it supports publish immutable versions from trusted builds, separate read from publish rights, proxy external dependencies through approved upstream sources, and promote package views instead of overwriting versions.

Open full notes