Skip to main content

Connect Azure DevOps

To integrate Azure DevOps with your environment, follow the step-by-step instructions below.

1. Basic Configuration Follow below steps

  1. Once you logged in you will navigate to Dashboard.
  2. Go to the integration and click on Connect button to add Azure Devops Datasource.
  3. Enter Account Name (e.g., Production-Azure-devops).
  4. Environment: Click the dropdown menu and select the environment type (e.g., Production, Staging, Development).
  5. Enter Organization URL (e.g. https://dev.azure.com/your-organization).
  6. Enter Personal Access Token (Click on view guide to generate Personal Access Token).
  7. Click on Verify Credential Button.
  8. Click on Connect button .

Step-by-Step Azure DevOps Credential Generation

Step 3.1: Locate Your Organization URL

  • Navigate to https://dev.azure.com and sign in.
  • Select your Organization from the left sidebar.
  • Note your Organization URL from the browser address bar. It follows one of two standard formats:
Modern format:
Example:
Legacy format:
Example:

Step 3.2: Open User Settings

  • In the top-right corner of the Azure DevOps interface, click the User Settings icon (gear icon next to your profile avatar).
  • Select Personal access tokens from the dropdown menu.

Step 3.3: Create a New Personal Access Token (PAT)

  • Click + New Token.
  • In the Create a personal access token panel, configure the following:

Step 3.4: Configure Token Scopes & Permissions

Under the Scopes section, select Custom defined and enable the following Read scopes:
TIP Alternative (Quick Setup): Selecting Full access will automatically cover all required read operations across every current and future Azure DevOps service.

Step 3.5: Save and Copy Your Token

  • Click Create at the bottom of the drawer.
  • Copy the generated PAT string immediately.
WARNING Azure DevOps will never display this token value again after you close this drawer. Store it securely in your password manager or configure it directly in Zero-X.

How to generate keys follow below steps

ZERO-X SECURITY ยท AZURE DEVOPS EXTENSION

Run Zero-X Security scans in your Azure DevOps pipelines.A step-by-step guide for adding the ZeroXSecurity@1 task to a pipeline in your own Azure DevOps organization and project โ€” from installing the extension to gating pull requests on findings.

Extension

Zero-X.zero-x-security

Task

ZeroXSecurity@1

Version

1.0.1

Minimum Agent

3.232.1

Setup Time

~20 minutes

In this guide

  • How it works
  • Before you start
  • Setup steps 1โ€“8
  • Configuration reference and failure threshold
  • More examples
  • Output variables
  • Troubleshooting
  • Security practices and getting help

How it works

The Zero-X Security Scan task runs as a normal step in your pipeline. It asks Zero-X to scan the repository and branch being built, waits for the results, reports them in the pipeline, and fails the build if findings reach the severity you choose.
  1. Pipeline runs
  2. Task calls Zero-X
  3. Scans complete
  4. Results reported
A push or pull request triggers your Azure pipeline.Using your API key, over HTTPS, the task starts a scan for this repository and branch.Vulnerability, IaC, SAST, malware, SBOM and secrets are scanned depending on which scanners are enabled.Results include counts in the log, a summary tab, a SARIF artifact, and a pass/fail gate.It works with repositories hosted in Azure Repos or GitHub, as long as the repository is connected to Zero-X Cloud.

Before you start

Make sure you have the following:
  • An Azure DevOps organization and project containing or connected to the repository you want to scan.
  • Permission to install extensions in that organization.
  • Permission to create pipelines and variable groups in the project.
  • A Zero-X Cloud account with access to your tenant, permission to connect datasources, and permission to create Platform API keys.
  • A build agent.
Microsoft-hosted agents such as ubuntu-latest work out of the box.Self-hosted agents need:
  • Agent version 3.232.1 or newer
  • Node 20 or 24 task support
  • Outbound HTTPS access to your Zero-X URL
Default Zero-X URL: