Skip to main content

Kendis Extension for Azure DevOps: Installation & Usage Guide

View Kendis’ enriched dependency details into ADO: summary, owner, due date, status, and color-coded alignment dependency links.

Kendis Team avatar
Written by Kendis Team
Updated this week

1. Overview

The Kendis Azure DevOps (ADO) extension brings Kendis dependency context into ADO. In ADO, teams link work items using Predecessor/Successor. Kendis visualizes those links as dependency lines where teams add a contextual summary, target dates, status, and ownership. With this Extension, those enriched Kendis details are visible inside ADO alongside the linked work items.

1.1 Who should configure it

  • Kendis Super Admin (one‑time setup)

  • After setup, any Azure DevOps user can read dependency information via the Kendis Extension in Azure DevOps.

1.2 Prerequisites

  • An Azure DevOps Organization with permission to install extensions

  • A Kendis workspace URL (e.g., https://yourcompany.kendis.io)

  • A Kendis API Token issued by a user account that will be used for the integration.


2. Install the extension in Azure DevOps

Extensions are only made available to selected Kendis customers, if you are interested in using Kendis Azure DevOps extension, reach out Kendis Support

2.1 Installation Steps

  • In ADO, go to Organization Settings → Extensions → Shared.

  • Install the Kendis Extension for your organization.

If your organization uses multiple ADO projects, installing at the Organization level ensures consistent access.


3. Configure the Extension (one‑time)

Open the Kendis Extension configuration screen in ADO.


3.1 Fill in the following fields:

  1. Kendis URL Prefix: Use the short subdomain from your Kendis URL. For example, if your Kendis URL is https://sampleboards.kendis.io, the prefix is sampleboards.

  2. Email: The email address of the Kendis user who will generate the API token.

  3. API Token: A personal API token generated from Kendis (see next section).

  4. Click Validate Credentials to confirm connectivity.

  5. Click Save.

Best Practice: Choose an API token with a longer validity (e.g., 1 year) and set a calendar reminder to renew it before expiry.

3.2 Generate a Kendis API Token

  1. Sign in to Kendis with the account you’ll use for the integration.

  2. Click your Profile.

  3. Go to API Key.

  4. Click Generate and copy the token.

  5. Return to ADO and paste the token in the extension configuration.


4. Visualization of Dependencies in Kendis and ADO Extension

This is a sample board where the feature 979 has 3 dependencies with other features and one of them is "Reverse Dependency" because the feature 988 is planned after the feature 979.

4.1 Dependency View in Kendis for a single Item

4.2 What users see in Kendis ADO Extension

Once configured, users can open the Kendis ADO Extension and:

  • View dependencies created in ADO directly within Kendis’ context.

  • See rich details for each dependency, including:

    1. Summary

    2. Target Resolution Date

    3. Status

    4. Responsible (Assigned To)

    5. Team & Sprint planning info

    6. Visual indicators if a dependency is aligned, reversed, or overdue (based on the line color)

In ADO, dependencies are represented as work item links. The Kendis Extension enriches this with planning context and visual cues.

Did this answer your question?