---
title: "Azure DevOps (Microsoft Entra ID OAuth) connector for agents — authorization and setup — AgentSky"
description: "Plan smarter, collaborate better, and ship faster with a set of modern dev services Connect Azure DevOps (Microsoft Entra ID OAuth) to AgentSky with managed OAuth."
url: https://agentsky.dev/connectors/azure_devops_microsoft_entra_id_oauth
---

# Azure DevOps (Microsoft Entra ID OAuth)

Plan smarter, collaborate better, and ship faster with a set of modern dev services Connect your account through managed OAuth to use the available operations in an agent task.

[Repo](https://agentsky.dev/auth/start?returnTo=%2Fconnectors%2Fazure_devops_microsoft_entra_id_oauth%3Fresume%3D1)

Connect Azure DevOps (Microsoft Entra ID OAuth) using the Connectors control before sending. Authorization opens separately and your draft stays here.

Setup

## Connect Azure DevOps (Microsoft Entra ID OAuth) with an explicit scope.

You need an AgentSky account and authority to connect the application account. Start with a read-only task before allowing changes.

01

### Find the application

Open connector settings and search for Azure DevOps (Microsoft Entra ID OAuth). If the catalog is unavailable, retry its load; an unavailable list is not proof the app is unsupported.

02

### Review authorization

Review the Azure DevOps (Microsoft Entra ID OAuth) account, workspace and permissions on the authorization screen. Your organization's policies or administrator approval may limit which resources the connection can access.

03

### Verify a bounded task

Name one Azure DevOps (Microsoft Entra ID OAuth) resource you can already access and ask the agent to check whether a read operation is available. If it is, retrieve and summarize that resource without changing it. If it is not, ask the agent to explain the missing operation or permission.

Verify access and results

## A connected account is the start of the workflow.

Open the same resource in Azure DevOps (Microsoft Entra ID OAuth) and compare it with the agent's result. Check the account, resource identifier and current content before using the output for another task.

- Access troubleshooting If Azure DevOps (Microsoft Entra ID OAuth) access fails, check the connected identity, resource sharing and requested permissions. Reconnect an expired or revoked account in connector settings. If the connection is healthy but an operation is unavailable, changing accounts may not resolve it.
- Available actions The runtime discovers the connector's current operations and input requirements. Do not assume every feature in the application's website is available as an agent action.
- Authorize changes explicitly For writes, specify the target and the allowed change. An instruction to draft or analyze is not permission to publish, send or delete.

## Azure DevOps (Microsoft Entra ID OAuth) connector questions

## Related resources

[Claude Code + Azure DevOps (Microsoft Entra ID OAuth)Use Azure DevOps (Microsoft Entra ID OAuth) with Claude Code in the shared Composer.](https://agentsky.dev/agents/claude-code/connectors/azure_devops_microsoft_entra_id_oauth) [Codex + Azure DevOps (Microsoft Entra ID OAuth)Use Azure DevOps (Microsoft Entra ID OAuth) with Codex in the shared Composer.](https://agentsky.dev/agents/codex/connectors/azure_devops_microsoft_entra_id_oauth) [OpenClaw + Azure DevOps (Microsoft Entra ID OAuth)Use Azure DevOps (Microsoft Entra ID OAuth) with OpenClaw in the shared Composer.](https://agentsky.dev/agents/openclaw/connectors/azure_devops_microsoft_entra_id_oauth) [OpenCode + Azure DevOps (Microsoft Entra ID OAuth)Use Azure DevOps (Microsoft Entra ID OAuth) with OpenCode in the shared Composer.](https://agentsky.dev/agents/opencode/connectors/azure_devops_microsoft_entra_id_oauth) [Hermes + Azure DevOps (Microsoft Entra ID OAuth)Use Azure DevOps (Microsoft Entra ID OAuth) with Hermes in the shared Composer.](https://agentsky.dev/agents/hermes/connectors/azure_devops_microsoft_entra_id_oauth) [Kimi Code + Azure DevOps (Microsoft Entra ID OAuth)Use Azure DevOps (Microsoft Entra ID OAuth) with Kimi Code in the shared Composer.](https://agentsky.dev/agents/kimi-code/connectors/azure_devops_microsoft_entra_id_oauth) [DeepSeek Harness + Azure DevOps (Microsoft Entra ID OAuth)Use Azure DevOps (Microsoft Entra ID OAuth) with DeepSeek Harness in the shared Composer.](https://agentsky.dev/agents/dsh/connectors/azure_devops_microsoft_entra_id_oauth) [pi + Azure DevOps (Microsoft Entra ID OAuth)Use Azure DevOps (Microsoft Entra ID OAuth) with pi in the shared Composer.](https://agentsky.dev/agents/pi/connectors/azure_devops_microsoft_entra_id_oauth) [All connectorsUnderstand managed application access.](https://agentsky.dev/connectors) [ChannelsChoose where the agent conversation happens.](https://agentsky.dev/channels) [PricingReview charges before running work.](https://agentsky.dev/pricing)

## Connect the right Azure DevOps (Microsoft Entra ID OAuth) account.

[Open connector settings](https://agentsky.dev/connectors)

## Frequently asked questions

### How do I connect Azure DevOps (Microsoft Entra ID OAuth) to AgentSky?

Sign in to AgentSky, open Connectors in the Composer and search for Azure DevOps (Microsoft Entra ID OAuth). Choose Connect, complete the provider's authorization flow, and return to your draft. Check that the intended account appears as connected before sending.

### Do I need a Azure DevOps (Microsoft Entra ID OAuth) API key?

This listing uses managed OAuth. Authorize the account in the provider's flow; do not paste a password or API key into the Composer. Any account, plan or administrator requirements are determined by Azure DevOps (Microsoft Entra ID OAuth).

### What can my agent do in Azure DevOps (Microsoft Entra ID OAuth)?

The runtime discovers current operations and their required inputs. A catalog listing does not promise every feature of Azure DevOps (Microsoft Entra ID OAuth). Start by asking which operation supports your task, and specify the resources and changes you authorize.

### Does connecting Azure DevOps (Microsoft Entra ID OAuth) make agent tasks free?

No. Account authorization and task usage are separate. AgentSky bills compute and model usage according to its pricing. Any Azure DevOps (Microsoft Entra ID OAuth) subscription, API quota or provider charge remains separate; review those limits before running a task.

---

Markdown copy of https://agentsky.dev/connectors/azure_devops_microsoft_entra_id_oauth. Every agentsky.dev page has one: add `.md` to its address or send `Accept: text/markdown`. Start from https://agentsky.dev/llms.txt.
