SupportAPI docsProduct updatesSign up for free
Search…
Snyk User Documentation
Introducing Snyk
Getting started
Snyk Web UI
Snyk CLI
Snyk API
Snyk for IDEs
Snyk Apps
Snyk Integrations
SNYK PRODUCTS
Snyk Open Source
Snyk Code
Snyk Container
Snyk Infrastructure as Code
Snyk Cloud
USING SNYK
Snyk Broker
User and group management
Fixing and prioritizing issues
Snyk reports
Snyk Tools
SNYK INFO
Disclosing vulnerabilities
How Snyk handles your data
Snyk Partner workshops
Atlassian Integrations
AWS Integrations
Snyk Integrations
Snyk Account
CircleCI
Docker
Dynatrace
GCP
GitHub
Microsoft Azure
Getting started
Sign up for Snyk
Securing AKS
Securing ACR
Securing Azure Repos
Getting started
Provision Azure services
Working with repos
Configure the Azure Repos integration
Add Azure Repos repositories
Next steps
Securing Azure Pipelines
Notifications in Microsoft Teams
Oracle Cloud Infrastructure
Red Hat
SpringOne
Powered By GitBook
Getting started

Background

In Securing AKS with Snyk we learned how to quickly deploy an application to a Kubernetes cluster running on Microsoft Azure Kubernetes Service (AKS) using manifest templates. Then, in Securing ACS with Snyk, we learned how to build container images using Dockerfile and securely storing these in ACR for later consumption. This allowed us more visibility and control over our application as we are able to define which resources we will consume and from where we will consume those resources. However, when we examined our container images scanned by Snyk, we noticed the following alert:
In this module, we will expand on best practices for building container images. We will build upon previous modules that taught how to leverage Snyk to secure a Kubernetes cluster and scan a private registry like ACR. We will provide prescriptive guidance on securing source code management systems in order to provide comprehensive security of your entire workflow.

Azure DevOps CLI

In the main Getting started section of the Microsoft Azure series, we covered setting up the Azure CLI. Now, we will add the Azure DevOps extension for Azure CLI allowing you to work in a more streamlined manner.
Run the following command from your terminal:
az extension add --name azure-devops
You should see a confirmation message indicating these were installed successfully. Next, after creating your Azure DevOps account, you should have an Organization. Please refer to the following figure for where to find this from your Azure DevOps portal:
For more detailed instructions, refer to the Sign up, sign in to Azure DevOps Quickstart. The organization should be in the format https://dev.azure.com/MyOrganizationName Now, let's sign in on the terminal by running az login from the terminal and configure the CLI with our organization value by running the following command:
az devops configure --defaults organization=https://dev.azure.com/MyOrganizationName/
Be sure to substitute MyOrganizationNamewith the correct value.
Previous
Securing Azure Repos
Next
Provision Azure services
Last modified 1mo ago
Export as PDF
Copy link
Edit on GitHub
Outline
Background
Azure DevOps CLI