Integrations / Azure DevOps

Azure DevOps

Azure DevOps engineering system for projects, repositories, pipelines, builds, releases, work items, and engineering delivery signals.

OAuth 2.0

Indexes

Actions

Events

What Telara does

Capability matrix

Indexes Yes Tracks spend No Discovers shadow AI No Runs actions Yes Real-time events Yes

Before you connect

Prerequisites

An Azure DevOps organization you can administer.

Organization owner, or a user who can create personal access tokens and grant project access.

Vendor setup

Get the credential

Prefer Connect in Telara

Settings → Integrations → Azure DevOps. If Telara offers Microsoft sign-in, use it. You do not register a legacy Azure DevOps OAuth app — that path is deprecated.

Or create a personal access token

In Azure DevOps, open User settings (click your avatar) → Personal access tokens → New Token. Name it for Telara, pick the organization, and grant the permissions this page lists from the catalog. Copy the token once.

Paste in Telara

On the Connect form, enter the organization name and the token. Username stays empty when Telara asks for Basic auth — the token is the password.

In Telara

Connect in Telara

OAuth 2.0

Microsoft Entra ID OAuth app for Azure DevOps REST APIs. Azure DevOps' legacy OAuth app registration path is deprecated for new apps.

In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.

Basic auth

Azure DevOps PAT fallback using Basic Auth with an empty username and the PAT as password.

In Telara, open Settings → Integrations, choose this connector, and enter the username and password (or key) Telara asks for.

Fields Telara asks for

Organization
Personal Access Token

Knowledge

What gets indexed

Resource	Coverage
Projects	Partial — not every record the vendor holds is synced

Sync

Freshness & sync

Resource	Lag	Deletions
Projects	Up to 1 day	Removed records disappear on the next full sync

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

Excluded from semantic search: Projects.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

A token scoped to the wrong organization connects and then lists no projects.

Microsoft Entra guest users often cannot create PATs. Use a member of the home tenant.