Skip to main content
Skip table of contents

Azure DevOps

Supported Versions

Please note that using a supported version is mandatory.

Product

Supported Deployment Types

Supported Versions

Azure DevOps

All

All

Environmental Prerequisites

Confirm the prerequisites of the corresponding integration template before continuing further, as some templates may not require all environmental prerequisites.

How to create a Private Access Token in Azure DevOps?

  1. Sign in to your organization in Azure DevOps. For example, https://dev.azure.com/{yourOrganization}.

  2. Open your user settings, select Personal Access Tokens, and select the + New Token button.

  3. Name your token, select the organization where you want to use the token, and then choose a lifespan for your token.

  4. Select the scopes for this token to authorize for your specific tasks. For example, to create a token to enable a build and release agent to authenticate to Azure DevOps Services, limit your token's scope to Agent Pools (Read & Manage). To read audit log events, manage and delete streams, select Read Audit Log, and select Create.

  5. Use this token as your password. When you're done, make sure to copy the token. For your security, it won't be shown again.

Connected System Configuration

Follow the steps below to add your instance as a connected system.

  1. Log into your ZigiOps instance.

  2. Navigate to Connected Systems → Add New System → Azure DevOps and configure the following parameters: 

    • Server URL → Input the URL of your instance. For example, https://dev.azure.com.

    • Instance Type → Select the type of your instance.

    • Organization/Collection → Input the desired Organization or Collection.

    • Username → Input your username.

    • Private Access Token → Input your Private Access Token.

    • Proxy Settings → Enables the usage of a proxy server.

  3. Examine the settings and if they are correct, click the Save button to save the system.

Related Templates

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.