Smarter Meeting Notes & Summaries for Azure DevOps Teams
Turn the transcript of a bug triage or sprint planning call into Azure Boards work items, assigned and parented, with the decisions written to your team wiki.
Triage call ended at 11:40. 6 fixes and 2 decisions pulled out. First item filed:
Decided on the call
- • Agreed: Apple Pay double charge on payment retry is Priority 1, Ravi owns it, target Sprint 58.
- • Agreed: tax rounding on Canadian orders goes to the backlog until finance confirms the rule.
- • Open: nobody took the flaky Cypress test on address autocomplete. Held for the lead.
How do I create Azure DevOps work items from meeting notes automatically?
Give an agent your Azure DevOps project and the place your call transcripts are saved.
- 01
Trigger fires
After a triage or planning call, it reads the transcript, separates what was decided from what was only discussed, and creates a Bug, Task or User Story for each agreed piece of work.
- 02
Separate decisions from discussion in the transcript
It fills in the area path, iteration and assignee when the call made them clear, links each item to its parent feature, and quotes the relevant part of the conversation in the description.
- 03
Match each agreed fix against existing work items
Decisions go onto the team's wiki page.
- 04
Create Bugs or Tasks with area path and iteration
Items nobody agreed to own, or that look like an existing bug, wait for the lead to decide.
- 05
You approve
Anything under your confidence bar waits for a human.
How you tell it what to do
Built in plain English.
You write the rule the way you'd describe it to a teammate. The agent reads the rule, breaks it into the actions it'll take, and confirms the apps it'll touch — before it does anything.
- 1Separate decisions from discussion in the transcript
- 2Match each agreed fix against existing work items
- 3Create Bugs or Tasks with area path and iteration
- 4Append decisions and new item links to the wiki
How it connects
Connect Azure DevOps. The agent does the rest.
Claude and ChatGPT are already running on our side. You connect Azure DevOps with one click, and meeting notes & summaries runs inside it.
Claude and ChatGPT run on our keys. Nothing for you to configure.
- Azure DevOpsConnect
- Microsoft_teamsConnect
Runs on your data, in your apps.
Nothing to deploy. Nothing to maintain.
Actions
What Azure DevOps + DeskFerry can do
Real Azure DevOps actions your AI agent can perform automatically — no manual work required.
Provision cloud resources
Spin up servers, databases, or containers in Azure DevOps when deployment pipelines or scaling rules are triggered.
Monitor system health
Watch CPU, memory, and network metrics in Azure DevOps and trigger alerts when thresholds are breached.
Scale resources automatically
Adjust compute capacity in Azure DevOps based on traffic patterns, queue depth, or custom scaling policies.
Rotate secrets and credentials
Automatically rotate API keys, database passwords, and certificates in Azure DevOps on a defined schedule.
Deploy application updates
Trigger rolling deployments in Azure DevOps when new container images or build artifacts are available.
Manage DNS records
Create, update, or remove DNS entries in Azure DevOps as part of deployment or domain management workflows.
Collect and forward logs
Stream application and infrastructure logs from Azure DevOps to centralized logging and analysis platforms.
Enforce security policies
Audit resource configurations in Azure DevOps against compliance rules and remediate violations automatically.
Discussed for four minutes, nobody volunteered. Not filed until someone is assigned.
"Coupon field clears on back button" sounds like #18107, closed last sprint. Reopen it or file new?
Transcript says "next sprint or the one after". Someone needs to pick Sprint 58 or 59.
Human in the loop
Approve before it sends.
Every draft lands in a review queue. You approve, edit, or reject — the agent never acts on its own unless you explicitly turn that on for a workflow you trust.
Governance
Every action, with the reasoning attached.
Each step the agent takes is logged with what it did, why it did it, and which app it touched. Audit-ready, so security and compliance can sign off without backfilling.
- Priya11:52 AM
Moved #18342 into Sprint 58 and confirmed Priority 1.
- Agent11:46 AM
Added 2 decisions and 5 linked work items to wiki page Triage/2026-09-17.
- Agent11:45 AM
Held the autocomplete test item instead of filing it.
Reason: It was discussed but no one agreed to own it, and an unassigned Bug would sit orphaned on the board.
- Agent11:44 AM
Created Bug #18342 under Feature #17990 with repro steps quoted from the call.
- Agent11:41 AM
Read the 38-minute transcript and found 6 agreed fixes and 2 decisions.
How it works
Get started in three steps
Step 01
Connect Azure DevOps and your recordings
Authorize the organization and project, and point the agent at the folder where Teams or Zoom transcripts land. It reads open work items first so it can spot duplicates.
Step 02
Say which meetings produce which items
For example: triage calls file Bugs in the Checkout area path, planning calls file Tasks under the feature being discussed, and retros only update the wiki.
Step 03
Settle the unowned and ambiguous items
Anything with no owner, a vague iteration or a likely duplicate waits for the lead. The rest is filed and linked from the meeting's wiki page.
Start automating Meeting Notes & Summaries for Azure DevOps
7-day free trial. Works with the tools you already use.
FAQ
Frequently asked questions
Does the agent join our Microsoft Teams meetings?
No. It works from the transcript after the call ends. If your meeting tool saves transcripts somewhere the agent is connected to, it picks them up there; otherwise someone drops the transcript file into a folder it watches. Nothing joins the call as a bot, and nobody has to change how they run triage.
How does it avoid filing a bug we already have?
Before creating anything it searches open and recently closed work items in the same area path for a similar title and description. A close match goes to the review queue with both items side by side, so the lead chooses between reopening the old one, adding a comment to it, or filing a new Bug.
Which work item types and fields does it set?
Whatever your process template uses. On the Agile process it usually files Bugs and Tasks; on Scrum, Product Backlog Items and Tasks. It sets title, description, area path, iteration, assignee and priority when the call made them clear, and leaves a field empty rather than guessing when it didn't.
We don't want retro comments turning into tickets. Can it tell meetings apart?
Yes. Each meeting type gets its own line in the rule. A common setup writes the retro's agreed changes to a wiki page and only creates a work item when someone says out loud to make a ticket for it. Planning and triage calls keep filing items as usual.
Can we trace a work item back to what was said?
Yes. Each item it creates carries a quote from the transcript in its description, shows the connected account in the item's history, and has a matching row in the audit log. If a filed item is wrong, the lead can see exactly which part of the call produced it and fix the rule.
Explore more