Azure Artifacts for packages - Mini Project: Build & Apply

Azure Artifacts for packages

📖 Scenario: You are working on a software project that requires managing and sharing packages securely within your team using Azure DevOps.You want to create an Azure Artifacts feed to store your packages and configure access permissions.

🎯 Goal: Build an Azure Artifacts feed configuration with proper access control to manage packages for your team.

📋 What You'll Learn

Create an Azure Artifacts feed named team-packages

Set the feed visibility to project

Add a user group called Developers with Contributor role to the feed

Enable upstream sources to allow pulling packages from public registries

💡 Why This Matters

🌍 Real World

Teams use Azure Artifacts to securely share and manage packages within their organization, ensuring consistent dependencies and controlled access.

💼 Career

Knowing how to configure Azure Artifacts is essential for DevOps engineers and cloud architects managing CI/CD pipelines and package management in Azure.

1

Create an Azure Artifacts feed

Create an Azure Artifacts feed named team-packages using the Azure CLI command az artifacts feed create with the parameter --name team-packages.

Azure

# Use az artifacts feed create --name team-packages to create the feed
# Your code here

Hint

Use the Azure CLI command az artifacts feed create with the --name option to create the feed.

2

Set feed visibility to project

Update the feed team-packages to have project visibility by adding the parameter --visibility project in the Azure CLI command.

Azure

az artifacts feed create --name team-packages \
# Set the feed visibility to project below
# Your code here

Hint

Add --visibility project to the feed creation command to restrict access.

3

Add Developers group with Contributor role

Add the user group Developers to the feed team-packages with the role Contributor using the Azure CLI command az artifacts feed collaborator add with parameters --feed team-packages, --collaborator Developers, and --role Contributor.

Azure

az artifacts feed create --name team-packages --visibility project
# Add Developers group with Contributor role below
# Your code here

Hint

Use az artifacts feed collaborator add to assign roles to groups.

4

Enable upstream sources

Enable upstream sources on the feed team-packages by updating the feed with the parameter --upstream-enabled true using the Azure CLI command az artifacts feed update.

Azure

az artifacts feed create --name team-packages --visibility project
az artifacts feed collaborator add --feed team-packages --collaborator Developers --role Contributor
# Enable upstream sources below
# Your code here

Hint

Use az artifacts feed update with --upstream-enabled true to allow pulling packages from public sources.

Practice

1. What is the primary purpose of Azure Artifacts in a development project?

easy

A. To monitor application performance

B. To deploy virtual machines automatically

C. To manage user identities and access

D. To store and share code packages securely

Solution

1. Step 1: Understand Azure Artifacts role

   Azure Artifacts is designed to store and share packages like libraries or tools used in development.

2. Step 2: Compare with other Azure services

   Other options relate to different Azure services: virtual machines, monitoring, and identity management.

3. Final Answer:

   To store and share code packages securely -> Option D

4. Quick Check:

   Azure Artifacts = package storage [OK]

Hint: Remember: Artifacts = packages storage and sharing [OK]

Common Mistakes:

• Confusing Azure Artifacts with Azure Monitor
• Thinking it manages virtual machines
• Mixing it up with Azure Active Directory

2. Which of the following is the correct way to configure a package manager to use an Azure Artifacts feed?

easy

A. Create a virtual machine in Azure

B. Add the feed URL to the package manager's configuration file

C. Enable Azure Monitor alerts

D. Set up Azure Active Directory users

Solution

1. Step 1: Identify configuration for package managers

   Package managers like npm or NuGet require the feed URL in their config to publish or consume packages.

2. Step 2: Eliminate unrelated options

   Creating VMs, enabling alerts, or setting up users are unrelated to package manager configuration.

3. Final Answer:

   Add the feed URL to the package manager's configuration file -> Option B

4. Quick Check:

   Feed URL in config = correct setup [OK]

Hint: Configure package manager with feed URL in config file [OK]

Common Mistakes:

• Trying to configure unrelated Azure services
• Forgetting to add the feed URL
• Confusing user setup with package feed setup

3. Given this snippet configuring npm to use Azure Artifacts feed:

npm set registry https://pkgs.dev.azure.com/contoso/_packaging/feed/npm/registry/

What will happen when you run npm install after this?

medium

A. npm will fetch packages from the Azure Artifacts feed

B. npm will fail because the URL is invalid

C. npm will install packages only from the public npm registry

D. npm will delete local packages

Solution

1. Step 1: Understand npm registry setting

   Setting the registry URL tells npm to fetch packages from that feed instead of the default public registry.

2. Step 2: Predict npm install behavior

   After setting, npm install will pull packages from the Azure Artifacts feed URL provided.

3. Final Answer:

   npm will fetch packages from the Azure Artifacts feed -> Option A

4. Quick Check:

   npm registry set = fetch from feed [OK]

Hint: npm registry URL points to Azure feed for installs [OK]

Common Mistakes:

• Assuming npm uses default registry ignoring config
• Thinking URL is invalid without checking format
• Confusing install with delete commands

4. You configured your NuGet client to use an Azure Artifacts feed but get authentication errors when restoring packages. What is the most likely cause?

medium

A. You have no internet connection

B. The feed URL is missing from NuGet.config

C. You did not authenticate with Azure DevOps before restoring

D. Your local packages folder is full

Solution

1. Step 1: Understand authentication requirement

   Azure Artifacts feeds require authentication to access private packages.

2. Step 2: Identify cause of authentication errors

   If you get authentication errors, it means you likely did not sign in or provide credentials to Azure DevOps.

3. Final Answer:

   You did not authenticate with Azure DevOps before restoring -> Option C

4. Quick Check:

   Authentication missing = errors [OK]

Hint: Always authenticate to Azure DevOps before package restore [OK]

Common Mistakes:

• Ignoring authentication step
• Assuming URL missing causes auth errors
• Blaming internet or disk space without checking auth

5. You want to share a private package with your team using Azure Artifacts. Which steps should you take to ensure only your team can access it?

hard

A. Create a private feed, add team members with permissions, publish package to feed

B. Publish package to public npm registry, share URL with team

C. Upload package to a public GitHub repo

D. Email the package files to team members

Solution

1. Step 1: Create a private feed in Azure Artifacts

   This feed restricts package access to authorized users only.

2. Step 2: Add team members with proper permissions

   Granting permissions ensures only your team can access the feed and packages.

3. Step 3: Publish the package to the private feed

   Publishing here keeps the package secure and accessible only to your team.

4. Final Answer:

   Create a private feed, add team members with permissions, publish package to feed -> Option A

5. Quick Check:

   Private feed + permissions = secure sharing [OK]

Hint: Use private feed and permissions to control package access [OK]

Common Mistakes:

• Publishing to public registries for private packages
• Sharing packages by email or public repos
• Not setting permissions on the feed