Copilot4DevOpsV10
The biggest release we have shipped. Chat becomes a live workspace. Elicit builds an entire Epic → Feature → User Story hierarchy in a single run. Documents draft, version and publish straight to your Wiki. Mockups export design tokens into your codebase. All of it inside Azure DevOps, all of it new.
Form Not Loading? Click Here
Four modules rebuilt, a refreshed interface throughout, and a release that covers the whole path from requirement to design.
A question card appears before generation, targeting the gaps that would materially change the output — audience, dependencies, compliance standards, sections to include. Questions arrive in passes with a progress indicator. Any one can be skipped, or the whole card at once.
Chat now renders live, actionable cards instead of plain text: work item hierarchies, sprint and board summaries, WIQL results, cumulative flow and velocity, pull requests, file diffs, commit history. Write actions are supported, with explicit confirmation required for anything destructive.
Generate Epic → Feature → User Story from a single source item in one run, instead of a separate pass per level with manual re-parenting afterwards. Use your project’s process template chain or build a custom hierarchy, then save and share it across the organisation.
Title generation continues until requirement coverage is addressed, rather than producing a fixed number. Every AI-generated title carries a relevancy score from 0 to 10, sortable for triage — and you can add your own titles alongside them.
Templates for SRS, SOP, Test Plan, Release Notes and User Guide. Refine drafts through chat scoped to a whole document or a named section. Every AI edit appears as a marked diff to apply or discard, incrementing the version and recording the instruction behind it. Publish to Azure DevOps Wiki, attach to a work item, or export to Word, PDF or Markdown.
Theme, fidelity and platform controls above the prompt. Generate variants to compare directions without losing the original. Select any component to edit it with scoped chat. Preview across desktop, tablet and mobile, then export as HTML, design tokens, CSS variables or a Tailwind theme.
One source item in. An entire Epic → Feature → User Story hierarchy out, published to Azure DevOps with every link type applied top-down. That used to be a separate pass per level, then manual re-parenting.
Forty-five minutes, most of it in the product.
The design decision behind clarifying questions, and where it shows up.
Clarifying question passes, Epic to User Story in one run, relevancy scoring, publish with link types applied top-down.
Live cards for work items, sprints and repositories — plus write actions and the confirmation step on destructive operations.
Template to draft to marked diffs, with version history and publishing to Azure DevOps Wiki.
Theme, fidelity and platform controls, variants, component-level editing, and export to design tokens.
Open floor. Submit questions when you register and we’ll prioritise them.
The people behind V10 — walking you through every part of it live on September 9. Bring your questions.
Every module in this release touches a different seat on the team.
Hierarchy generation, coverage-based titles, relevancy scoring.
Persistent threads, manual titles alongside AI candidates.
Test plan templates, acceptance criteria widgets, test plan documents.
Repository widgets, pull request and commit actions in chat.
SOP and SRS templates, section-scoped chat, Wiki publishing.
Stored answers, marked diffs, version history on every document.
No. Every question is optional. You can skip any individual question or dismiss the whole card and generate immediately — unanswered questions fall back to a stated default assumption, so you always know what was assumed on your behalf.
No. Chat replies state which sections they propose to change before anything is applied, and every proposed change appears as a marked diff you apply or discard section by section.
Write-operation widgets support actions like creating branches, pushing commits and completing pull requests. Higher-risk and destructive actions require explicit confirmation before they are carried out.
Elicit runs and generated documents are saved as persistent threads, retaining the original prompt, clarifying answers, chat transcript and current content. Reopening a thread restores it in full.
[Confirm licensing and pricing position before publishing.]
Yes — everyone who registers receives it, whether or not they attend live.
Forty-five minutes, live in the product, across every module that changed. Register once and we’ll send the recording either way.
Save my seat
