azure-artifacts

You can integrate Azure Artifacts with CI/CD workflows by configuring your pipeline to authenticate to your feed using provided tokens, then running package restore and publish commands across NuGet, npm, Maven, or Python ecosystems during builds.

Best practices for package retention include configuring feed views to manage package visibility, setting retention policies to automatically delete old versions, and promoting specific package versions between views to control deployment readiness.

Azure Artifacts supports Python and Maven package management alongside npm and NuGet, providing unified feed management, upstream source proxying, and CI/CD integration for restoring and publishing across multiple package ecosystems.

Azure Artifacts limits and quotas define storage capacity boundaries and feed size restrictions, requiring teams to implement retention policies and manage upstream source caching to avoid exceeding organizational storage allocations.

Securing Azure Artifacts feeds requires configuring feed permissions to restrict access by user or group, managing authentication credentials for CI/CD pipelines, and auditing upstream source configurations to prevent unauthorized package consumption.