Azure DevOps is not an integration.It is where the agents run.
Agents4DevOps installs from the marketplace into your Azure DevOps organization and lives under the Boards tab. Agents read and write work items, pull requests, pipelines, test results, wiki pages and package feeds directly, under the permissions you already maintain. Outputs land on the artifact where your team already looks.
Installs from the marketplace. No separate portal, no sync, no new login.
- install Azure DevOps Marketplace
- reads Boards · Repos · Pipelines
- writes where the team works
Six services. One system of record.
Each agent is scoped to the services, projects and paths its workflow needs. Tool calls are enabled per agent, and write actions follow the approval policy you set.
| Service | Agents read | Agents write |
|---|---|---|
| Boards | Work items, fields, states, links, discussion history, saved queries, area and iteration paths. | Acceptance criteria drafts, field and tag updates, new tasks and defects, trace links, and questions posted to the owner on the item. |
| Repos | Pull requests, changed files, commits, branch policies and the work items linked to each change. | Inline review comments, commit and PR links to work items, and follow-up work for gaps the review found. |
| Pipelines | Run history, stages, logs, approvals, the last green run and the merges since, plus build artifacts. | Failure classifications with evidence, proposed fixes held for approval, approved reruns, and tags on build artifacts. |
| Test Plans | Test cases, runs, results, pass rates and the requirements each test covers. | Test cases drafted from criteria, test results, per-step Passed/Failed outcomes, and defects from failed runs. |
| Wiki | Wiki pages used as reference, and as BYOD knowledge for grounding when your organization enables it. | Readiness reports, release notes and documentation pages kept current from work items and criteria. |
| Artifacts | Feeds, feed views (Local, Prerelease, Release), feed permissions, packages and deleted packages. | Created and updated feeds, restored feeds, package version lifecycle changes, all reflected directly in Azure Artifacts. |
No sync. No new login. No shadow automation.
There is no second system to keep aligned with Azure DevOps. Agents operate on your project as the system of record, so requirements, work items and traceability never move to an external database to be drafted against. Your team configures, runs and reviews agents in the same organization where the work happens, and the work item history notes when an AI agent made a change.
- Installs from the marketplace, built by Modern Requirements, a Microsoft Solutions Partner.
- Lives under the Boards tab in your Azure DevOps organization.
- Same security and trust model as Copilot4DevOps.
- Existing Azure DevOps permissions, project scope and tool permissions enforced on every run.
- Outputs written to the work item, the PR or the wiki page, not a separate dashboard.
- Every run recorded as a job in the Job Explorer.
FIG 1
FIG 2
FIG 3
Permissioned tools across the lifecycle.
Agents are composed from a reusable skills library and Azure DevOps tool calls. Each tool call is enabled or disabled per agent from Tools, Add tool, Tool Calls, so an agent can only use what its workflow needs.
Work items and queries
Run saved queries, find blockers, create tasks, validate states and fields, and maintain links across the backlog.
Build automation
Read stages, logs, approvals and build artifacts with GetBuildArtifacts and GetBuildsArtifacts, so agents can trace build outputs to the change that produced them.
Test management
Create and update test results, and record per-step Passed/Failed outcomes with UpdateTestStepResults, shown in the Runs, Result, Steps view. Batch calls cover many results at once.
Artifacts management
26 tool calls across six sections: feeds, feed views, packages, package lifecycle, downloads and the recycle bin. Most support batch operations.
Wiki and documentation
Publish readiness reports and keep documentation pages aligned with the work items and criteria they describe.
Policy, gates and evidence
Evaluate thresholds and exceptions, then index proof links into an evidence pack for review.
Call any agent from chat.
The prebuilt system agents from Agents4DevOps can be used directly in Copilot4DevOps Chat, alongside your organization's custom agents. Click + in the chat input and choose All agents, or type + to open the agent picker inline. Each agent shows its name, a short description and, for system agents, a System badge. Replies are labelled with the agent that produced them, so the conversation keeps a clear record of which agent handled each part. Agents run from chat in single-agent or multi-agent orchestrator mode, and the same scope and approval rules apply.
From install to first verified run.
Setup happens inside Azure DevOps, by the people who already administer it.
Install from the marketplace
Add Agents4DevOps to your Azure DevOps organization. It appears under the Boards tab, with the build version shown next to the title so you can confirm what is installed.
Set permissions
Allow or Deny Manage Agents, Delete Agents, Job Explorer and Manage Skills per team or security group, at project level with organization inheritance.
Pick an agent and align it
Start from the Agent Library or describe a new agent in plain language. Compatibility Alignment maps the library agent's work item types, fields and allowed values to your process template, and flags anything that needs review before you save.
Scope, trigger and approve
Set scope, tools and model. Choose a manual, event-based or scheduled trigger, add conditions so it runs only on matching work items, and turn on Required Approval where a person must sign off. Opt in to BYOD knowledge if your organization has enabled it.
Run and review
Run the agent on a real item. Open the job in the Job Explorer to read the timestamped log, the agent response, any Open Task and the verification result.
[ Trusted by Microsoft and industry leaders ]
Native questions.
Under the Boards tab in Azure DevOps, installed from the marketplace into your organization. There is no separate portal and no new login.
No. Agents read and write your Azure DevOps project directly. There is no sync job and no external copy of your requirements or trace links.
Library agents are built on predefined process templates. Compatibility Alignment detects mismatched work item types, fields and allowed values, auto-maps what matches, and lets you map the rest before the agent is saved. For agents that respond to repository events, you also pick the target repository on the Trigger tab.
It installs alongside Copilot4DevOps and follows the same security and trust model. System agents from Agents4DevOps can be picked directly in Copilot4DevOps Chat.
Yes, with BYOD. An organization administrator activates it in Organization Settings, Copilot4DevOps, BYOD, and builds the knowledge base from uploaded files, work item queries and wiki pages. Each agent can opt in with Use BYOD.
Agents work through permissioned Azure DevOps tool calls. Agent responses can be saved as PDF, Word or Markdown for sharing outside Azure DevOps. Ask in a demo about the specific external system you need.
See it run in your own organization.
Start the free trial with 2,000 credits and no card, or bring one Azure DevOps workflow to a 30-minute technical demo and watch an agent read, act, pause for approval and record the run.
