Skip to content
Azure DevOps integration

Sync Azure DevOps work items both ways

Mirror your Azure DevOps boards — per project and team — onto a faster surface. Drag a work item in Laya and its state changes in Azure DevOps; edit a field in Azure DevOps and it flows back to Laya. No exports, no cutover: Azure DevOps remains the system of record throughout.

Microsoft OAuth or PATTwo-way syncEvery work item typeNo migration
Connecting

Sign in with Microsoft, pick your organisation and boards

Connecting uses Microsoft Entra ID OAuth for work or school accounts — one consent, no token management, and refresh handled for you. Laya then lists your Azure DevOps organisations so you choose which to bind, and which project and team boards to mirror.

1 · Authorise with Microsoft

A single Entra ID consent connects Laya to Azure DevOps. Using a personal Microsoft account? Connect with a personal access token instead — a PAT with Work Items (Read & write) scope is all the basics need.

2 · Choose an organisation

Laya lists every Azure DevOps organisation your account can reach. Unlike Jira, a workspace can hold connections to several Azure DevOps organisations at once.

3 · Mirror project × team boards

Pick the boards to mirror — each is a project and team pairing, exactly as Azure DevOps organises them — with two-way sync per board. You are live immediately.

Private or shared

Start alone, grow into a team workspace

Just for me

Mirror your organisation’s boards into a private workspace. No team setup, no admin involvement, nobody else affected — the quickest way to evaluate Laya against real work items.

A shared workspace for the team

Set up a shared workspace and teammates who sign in with Azure DevOps join automatically — one workspace, one set of mirrored boards, everyone on the same surface.

Verified admin claim. A shared workspace stays unclaimed until an Azure DevOps organisation admin claims it. Laya verifies admin status against the organisation’s own entitlements API — not self-declared — and on claim the previous owner becomes a maintainer.
Field coverage

What syncs, in each direction

Laya mirrors every work item type in the project — user stories, bugs, tasks, features, product backlog items and any custom types your process defines. States are mapped through each process’s own state categories, never hard-coded names, so Agile, Scrum, CMMI and fully custom processes all land correctly.

Azure DevOps → Laya

Title, state, work item type, description, assignee, tags, priority, story points, parent links, iteration path and backlog order all project onto the mirrored board — with assignee avatars fetched securely through the connection.

Laya → Azure DevOps

Title, state, priority (1–4), assignee, tags, iteration path, area path, story points, target date, descriptions and custom fields write back as you edit. New work items of any type can be created from Laya, parented correctly — and deleted, too.

Writes that never clobber. Every outbound edit carries a revision check, so if a work item changed in Azure DevOps since Laya last read it, the write is rejected rather than silently overwriting a colleague’s change — then the next sync reconciles.

Iterations are first-class: browse team iterations with their dates, assign items, and even create a new iteration from Laya. Area paths are supported in the same dropdowns. Full tables in what syncs, per provider.

Freshness

How fresh is the mirror? Here are the real numbers

Edits made in Laya reach Azure DevOps immediately. In the other direction, Laya polls every mirrored board on a 60-second cycle (on by default), so changes made in Azure DevOps appear within about a minute. Opening a work item’s detail panel reconciles that item instantly, and Sync now refreshes a whole board on demand. There is no push-based webhook for Azure DevOps today — we would rather tell you that than let you assume it.

Instant
Laya → Azure DevOps: edits push as you make them
60 s
background poll for changes made in Azure DevOps
On open
a work item reconciles the moment you view it

Every connection shows live health (Healthy, Degraded, Needs attention or Idle), the last sync time and a read-only sync log of inbound and outbound events. The wider mechanics: how two-way sync works and sync health, logs and recovery.

The fine print

Honest limitations

Work or school accounts for OAuth. Microsoft sign-in only works for Entra ID (work or school) accounts. Organisations on a personal Microsoft account connect with a personal access token instead — fully supported, just a different door.
400 work items per board. Each mirrored board caps at 400 work items (items in the Removed state are excluded). Large projects are best mirrored per team board rather than in one giant view.
Comments: read and add, not edit. You can read the full discussion on a work item and post new comments from Laya, but editing or deleting existing Azure DevOps comments is not supported. Attachments are not synced.
Governance

Held safely, admin-controlled, easy to leave

Held safely

Connection credentials — OAuth tokens and personal access tokens alike — are stored encrypted at rest and never returned by any API response or shown in the interface again.

Admin-controlled

Connecting, mirroring and disconnecting need a workspace Owner or Admin. Other members can open mirrored boards and run Sync now — if you lack the rights, the screen says so and points you to an Admin.

Clean disconnect

Disconnecting stops the sync and removes Laya’s mirror of your boards. Your native Laya boards are kept — and your Azure DevOps data is never touched.

Put your Azure DevOps boards on a faster surface

Free during early access. Sign in with Microsoft, mirror your boards, and work items sync both ways — with Azure DevOps untouched.

Mixing tools? See all five Laya integrations — or layer Azure DevOps and Jira boards together on one master board.