Meet·Advanced·30 min·Updated Sep 30, 2026

Ask a Teams channel agent about live project blockers

Query an MCP-connected channel agent that pulls live risk and blocker status straight from Jira into your Teams channel.

Download PDF

Microsoft 365

Works With

Prerequisites

An MCP connection between the Teams channel agent and your issue tracker (Jira/Asana/GitHub)

Business Outcome

Teams can check project blockers without leaving chat or waiting for someone to compile a status update from the tracker.

Workflow Overview

Teams
Copilot

Step 1: Confirm the channel agent is connected to your trackerTeams

Check the agent's connection status in its configuration panel (or ask it directly "what's your current data source") before you trust anything it reports.

An MCP connection can silently drop after a token expires or a tracker permission changes, and a disconnected agent will still answer fluently from whatever it last cached instead of failing visibly.

Step 2: Ask about current blockers directly in the channelCopilot

Ask in plain language, right in the channel where the team already works, and be specific about which epic or project you mean — a vague "what's blocked" across a tracker with dozens of open issues returns a noisy list instead of the one thing you actually need to act on.

Prompt idea:

What's blocking the checkout redesign epic right now, and how long has each blocker been open? Pull this from Jira, not from what's been said in this channel.

Step 3: Verify against the tracker for anything you'll act on (Jira)

Before escalating or raising a blocker with a stakeholder, open the actual Jira issue and check its status, age, and assignee directly — an agent summarizing a dozen issues at once can occasionally merge or mis-date one, and that's a worse look in an escalation email than a short delay to double-check.

Step 4: Schedule a meeting from the chat if neededCopilot

If a blocker clearly needs a live conversation, ask the agent to set it up right there in the channel, naming the specific owners who need to be in it — this skips the context-switch of opening your calendar app and manually hunting down everyone's availability.

Check the work

  • Confirm the blocker list matches what's actually open in Jira right now, not a cached view.
  • Check that "blocked" status reflects the tracker's current state, not an old comment thread.
  • Verify any meeting the agent scheduled included the right owners before treating it as set.

Inspired by: Microsoft, Ignite 2025 keynote recap, November 2025.

Expected Outcome

A live blocker status pulled directly from the tracker, posted in the Teams channel, with a meeting scheduled if one's needed.

!

Is AI actually needed here?

The underlying data pull is a deterministic tracker query — blocker status and age are fields, not something requiring interpretation. The agent's real contribution is letting people ask in plain language from inside Teams instead of opening Jira.

Non-AI alternative: A saved Jira filter or dashboard already surfaces the same blocker list and ages at a glance, just outside the Teams chat window.

Related Workflows

Related Playgrounds

WORK WITH LIMINALS

Make AI useful for your team.

Get practical help with AI consulting or ask about training courses for your team.