The Azure DevOps Work Item Read Tool
Read projects, work items, and repository summaries from Azure DevOps Services through the Microsoft authorisation — delivery context for agents in tenants that run on Boards and Repos.
Agents can’t act on context they can’t reach
In Microsoft-first engineering organisations the delivery truth lives in Azure Boards, yet status still gets retyped into chat and slide decks. Retyped status is where work items go to become fiction.
Pasted snippets
Copied context is stale the moment it lands.
Swivel-chair work
People shuttle data between tools by hand.
Over-broad tokens
Shared credentials see far more than needed.
No audit trail
Nobody can say what a bot read, or when.
Azure DevOps Work Item Read, without the risk
Capability
What it does
Read Azure DevOps projects and work items.
it reads projects, work items, and repository summaries from Azure DevOps Services.
Assignable to any agent
How it works
Predictable, inspectable behavior
Designed to be reliable.
access rides the Microsoft sign-in your tenant already approved — Azure DevOps is consented as its own resource — and every query is scoped to that account and logged.
Every call logged
Governance
Private, governed, on-premise
Runs inside your perimeter.
Work item reads reuse the Microsoft authorisation your tenant granted, with Azure DevOps consented explicitly as its own resource, so scope is visible to your admins and every query is written to the audit trail.
Per-tenant, logged
Parameters
The azure_devops_workitem_read tool accepts these inputs when an agent calls it. Required inputs are flagged.
default: 50 Optional Maximum work items to return.
How the Azure DevOps Work Item Read tool works in practice
Azure DevOps Work Item Read lets a VDF AI agent answer delivery questions from Azure Boards itself. It is part of the Microsoft connector family: one tenant sign-in, with Azure DevOps consented as its own resource.
An agent can fetch a project’s work items, follow specific ids, and read repository summaries — enough to write a sprint status that names its sources, without anyone exporting a board to a spreadsheet first.
Estates that also run on-premises servers pair it with TFS Work Item Read; teams bridging trackers use it next to Jira Create Issue when findings must become tickets elsewhere.
Where Azure DevOps Work Item Read pays back
Sprint answers
Report what a board says right now, cited.
Escalation context
Pull the work items behind an incident.
Cross-team status
Read several projects into one summary.
Backlog triage
Surface aging items nobody has touched.
Assigned to agents, orchestrated as networks
On VDF AI, an industry’s use cases map to agents, and you assign tools like this one to those agents. Compose multiple agents into a governed, on-premise network.
- 1Industry Your sector Finance, healthcare, telecom, government, and more.
- 2Use Case A job to be done Concrete workflows the business needs solved.
- 3Agent A specialized worker Governed AI agents that execute the use case.
- 4Tool Azure DevOps Work Item Read The capability you assign to an agent.
- 5Network Agents, orchestrated Many use cases and agents, working as one.
What changes after you assign it
Questions about the Azure DevOps Work Item Read tool
What is the Azure DevOps Work Item Read tool?
It reads projects, work items, and repository summaries from Azure DevOps Services. Assigned to a VDF AI agent, it runs under role-based policy with full audit logging so the capability is safe to use in production.
Is this the same connector as TFS?
No. This reads Azure DevOps Services through the Microsoft sign-in; on-premises Azure DevOps Server and TFS use the separate token-based TFS connector.
What consent does it need?
Azure DevOps is consented as its own resource on the Microsoft connection, so approving file access alone does not silently include it.
What inputs does the Azure DevOps Work Item Read tool need?
It requires project, and optionally accepts ids, query, and limit. Each parameter is validated when an agent calls the tool, and the full call is logged for audit.
Which tools pair well with Azure DevOps Work Item Read?
Azure DevOps Work Item Read is commonly assigned alongside TFS Work Item Read, Jira Create Issue, and Bitbucket Repo Read. On VDF AI you compose several tools and agents into a single governed, on-premise network.
Does it run on-premise?
Yes. Like every VDF AI tool, it can run on-premise or in your sovereign cloud, scoped per user and audit-logged, so your data never leaves your perimeter.
How do agents use it?
You assign the tool to an agent under a role-based policy; the agent calls it as one step in a task, and several agents and tools can be orchestrated together as a governed VDF AI Network.
Assign Azure DevOps Work Item Read to these agents
These VDF AI agents can be assigned this tool. Open an agent to see the full toolkit it can run.
Tools that work well alongside this one
Where this tool delivers value
Put Azure DevOps Work Item Read to work
See the Azure DevOps Work Item Read tool assigned to an agent and orchestrated in a governed, on-premise network.