Does Watari really support Azure DevOps, or only GitHub?

Full parity with GitHub, not a limited port. Watari indexes your Azure Repos code, maps each bug to a file and function, opens draft pull requests, watches build validation, and confirms a production deploy before publishing the customer-facing RCA — every stage of the pipeline runs on Azure DevOps. Most support-to-code tools are GitHub-only; Watari is not.

Do I connect with a personal access token or OAuth?

OAuth through Microsoft Entra ID — the modern, tenant-backed flow. Entra tokens are short-lived and auto-refreshed, bound to your organization’s tenant, and revocable in one place by an administrator (Microsoft Entra → Enterprise applications, or your Azure DevOps OAuth authorizations). No personal access token to mint, share, or rotate. Depending on tenant policy, an admin may approve the connection once.

Does Watari respect Azure DevOps branch policies?

Yes. Azure DevOps runs build validation and required-reviewer policies once a PR leaves draft state, so Watari publishes the draft when the fix is ready — at which point your policies run exactly as they would for any human-opened PR. Watari never bypasses a policy: if you require build validation to pass or a minimum number of approvals, the PR will not complete until your pipelines and human reviewers satisfy them. Required reviewers from a branch policy take precedence over Watari’s inferred reviewers.

Can the pull requests be authored by a bot instead of a teammate?

Optionally, yes. By default a draft PR is authored by the user who connected Azure DevOps, because Entra sign-in acts on that user’s behalf. If you would rather PRs be authored by Watari, add Watari’s service principal to your organization once (Organization settings → Users → Add users, assign Basic access, add to Project Contributors). This mirrors how Renovate, Copilot, and Devin operate on Azure. It is entirely optional — skip it and everything still works, PRs are just authored by the connecting user.

Do you support Azure DevOps Server (on-premises)?

Today Watari connects to Azure DevOps Services on dev.azure.com (cloud). Azure DevOps Server, the self-hosted on-premises edition behind your own firewall, is out of scope for now — if that is a requirement for your team, tell us and we will scope it.

Is my source code safe?

Watari does not store your source code — only vector embeddings and metadata. The actual code is fetched from Azure Repos on demand and discarded after use. Tokens and secrets are AES-256-GCM encrypted before they hit the database, and tenant data is isolated via Postgres row-level security on every table. We never train models on your code. Full detail at watari.ai/security.

Azure DevOps · Source control

Watari for Azure DevOps

Q: Can I mix GitHub and Azure DevOps repositories in one workspace?

Yes. A bug is routed to whichever repositories its code actually lives in, regardless of provider, so you can run some products on Azure Repos and some on GitHub and Watari fans out across both. Multi-repo fan-out — including cross-provider — is available on Growth and above.

Not another GitHub-only tool. Full parity for Azure Repos.

Most tools that turn support tickets into code changes stop at GitHub. Watari supports Azure DevOps at the same depth: connect Azure Repos through Microsoft Entra ID, and your Zendesk, Intercom, and Freshdesk tickets become draft pull requests mapped to the exact file and function — behind your branch policies, with the customer-facing RCA held until your production pipeline confirms the fix is live.

Install Watari free See pricing

Connect from your Watari dashboard — sign up free, then Settings → Integrations → Connect Azure DevOps. The Entra flow, permissions, branch policies, and optional bot-author setup are documented at the Azure DevOps connection guide.

Trial: 14 days · 10 Mapped Bugs
Auth: Microsoft Entra · OAuth
GitHub parity: Full
Mismapped credit: 7 days

What is Watari for Azure DevOps?

Watari for Azure DevOps turns customer support tickets into draft pull requests in Azure Repos — at full parity with its GitHub support. It connects through Microsoft Entra ID, indexes your code, maps each bug to the responsible file and function at ≥ 0.7 confidence, and opens a draft PR behind your branch policies. The customer-facing RCA is published only after an Azure Pipelines production stage confirms the deploy.

Why Azure DevOps teams choose Watari

Azure DevOps at full GitHub parity

Most tools that turn support tickets into code changes are GitHub-only. Watari treats Azure Repos as a first-class target: everything the pipeline does on GitHub — index, map, draft PRs, watch build validation, deploy-gate the RCA — it does on Azure DevOps.

Mapped to the exact file and function

Watari indexes each connected Azure Repos repository and pins every bug to the responsible file and function, each with a 0–1 mapping confidence. A Mapped Bug clears a dual ≥ 0.7 gate — extraction and code-mapping both — before a PR is ever drafted.

Microsoft Entra ID, not a PAT

Watari authenticates through Microsoft Entra ID — tenant-backed OAuth with short-lived, auto-refreshed tokens revocable in one place by an admin. No personal access token to mint, share, or rotate. Entra is bound to your organization’s tenant.

Respects your branch policies

Azure DevOps runs build validation and required-reviewer policies once a PR leaves draft state — so Watari publishes the draft when the fix is ready, and your policies run exactly as they would for a human-opened PR. Watari never bypasses a policy.

Optional bot-authored pull requests

By default PRs are authored by the connecting user. Add Watari’s service principal to your org once — a one-time Basic-access add — and new drafts are authored by Watari instead, the way Renovate, Copilot, and Devin operate on Azure. Entirely optional; nothing depends on it.

Mix GitHub and Azure repos in one workspace

A bug is routed to whichever repositories its code actually lives in, regardless of provider. Run some products on Azure Repos and some on GitHub, and Watari fans out across both — one workspace, one support-to-PR loop.

How Watari turns a support ticket into a draft Azure Repos PR

Connect Azure DevOps via Microsoft Entra (OAuth)
From Settings → Integrations, click Connect Azure DevOps. You are redirected to Microsoft to sign in and approve the access Watari requests. Depending on your tenant’s policies, an administrator may approve the connection once on your behalf. This is Entra OAuth — no personal access token to mint or paste.
Pick the organization, project, and repository
Watari discovers the Azure DevOps organizations you belong to and links automatically if there is exactly one eligible; otherwise you choose. Then pick the project and repository to connect. Watari resolves your default branch automatically — master or main, there is nothing to configure — and indexing starts immediately.
Connect a support tool and let tickets flow in
Connect Zendesk, Intercom, or Freshdesk. From the next qualifying ticket onward, a vision-aware model extracts a structured bug — severity, reproduction steps, expected vs actual, customer impact, and original-language verbatim. Below 0.7 extraction confidence, the bug queues for review and is never billed.
Each bug mapped to the file and function in Azure Repos
Watari searches your indexed code and narrows to the exact file and function responsible, each with a 0–1 mapping confidence. A Mapped Bug requires both extraction and mapping at ≥ 0.7 — below that, the bug queues for review and is never billed. Reviewers are inferred from the commit history of the mapped files.
Draft PR opened, policies run, customer reply held for deploy
The draft pull request opens in Azure Repos with the patch, the test, and inferred reviewers. When the fix is ready Watari publishes the draft so your branch policies and build validation run. After the merge and your production pipeline stage both complete, the customer-facing RCA is posted back to the originating ticket in the customer’s language.

What Azure DevOps access Watari needs

Through Entra delegated access, Watari acts on the Azure DevOps REST API on your behalf, using only the operations the pipeline needs — scoped to the repositories you connect. Watari never deletes branches, force-pushes, or changes organization settings.

Read: Code in the repositories you connect (for indexing), pull requests, work items (Boards), and build & pipeline status — used to confirm CI and production deploys.
Write: Push the draft-PR patch to a new branch, open draft pull requests and request reviewers, subscribe to push / PR-merge / pipeline service hooks, and file Azure Boards work items only when that sync is enabled.
Store: Vector embeddings and metadata — never your source code, which is fetched on demand and discarded after use. The Entra token reference is AES-256-GCM encrypted before persistence. Tenant data is isolated via Postgres row-level security on every table.
Never used for: Model training. Your source code and tickets are not used to train any model — ours or any third party’s. Full detail at watari.ai/security.

Pricing

You only pay when Watari delivers a Mapped Bug — a structured bug paired with the file and function responsible, both at ≥ 0.7 confidence. Draft PRs, customer-facing RCA, and Jira / GitHub Issues sync are bundled. The Azure DevOps integration itself is never a surcharge.

Starter

$400/mo

20 Mapped Bugs included · $25/bug on-demand

For small teams shipping their first Mapped Bugs from a single Azure repo.

Growth

$900/mo

60 Mapped Bugs included · $20/bug on-demand

For teams running customer support against a multi-repo Azure DevOps product.

Scale

$1,800/mo

150 Mapped Bugs included · $15/bug on-demand

For multi-repo SaaS on Azure DevOps with a dedicated support function.

Indian buyers (with GSTIN) are billed in INR; everyone else in USD. 14-day free trial · 10 Mapped Bugs included · no credit card required. Annual billing saves 17%. Full plan comparison at watari.ai/pricing.

Security & privacy

Microsoft Entra ID — short-lived tokens, admin-revocable in one place.
We never store your source code — only embeddings and metadata.
Tokens and secrets AES-256-GCM encrypted at rest.
Postgres row-level security on every tenant-scoped table.
Your source code and tickets never train any model.
Full security posture at watari.ai/security.

Frequently asked questions

Your next support ticket arrives as a draft PR.

Connect Zendesk, Intercom, or Freshdesk, then GitHub or Azure DevOps. Tickets land mapped to the file, function, and line — ready for your reviewer to take over.

Start free trial

Trial length: 14 days
Bugs included: 10 Mapped
Card required: No
Mismapped credit: 7 days
Cancel: Any time

You only pay when we know what to change.