AzentAzent

How It Works

Understanding the end-to-end flow helps you get the most out of Azent. Here is what happens when you trigger the agent.

1

Trigger

You @mention the Azent bot in a work item comment, PR comment, or click a trigger button in the DevOps extension.

2

Validation

Azent verifies that the requesting user is authorized and checks your plan limits (concurrent runs, agent hours).

3

Agent execution

The agent clones the repository, reads the full context (work item details, PR diff, project configuration, skills), and writes the code using your chosen AI provider (Claude or Codex).

4

Validation pipeline (optional)

If a validation pipeline is configured in .azent.json, the agent runs it after committing changes. If it fails, the agent reads the logs, fixes the issues, and retries.

5

Result

The agent opens a pull request (or pushes fixes to an existing one) and posts a status summary as a comment in Azure DevOps. You can monitor progress in real-time from the Dashboard or DevOps extension.

Security

  • •All secrets (PAT, API keys) are encrypted at rest and in transit
  • •Only members of the configured allowed group (default: Contributors) can trigger the agent
  • •Dashboard authentication uses Microsoft Entra ID (Azure AD)