A woman reviews a secure AI-powered messaging and notification dashboard on a large screen.
Microsoft's AI at Work roadmap has an entry called "Work IQ: Listen" (ID 570867). It's the part of Work IQ that lets an agent react to events instead of checking for them. Microsoft's Ignite 2026 post says agents can respond when something relevant happens, like a new message or a business event. They don't have to wait to be asked or keep checking for updates. The roadmap lists the feature as in development. It gives an estimated preview in November 2026 and general availability in January 2027. Those dates are estimates, and Microsoft says roadmap items can change.

A woman reviews a secure AI-powered messaging and notification dashboard on a large screen. Where it stands today​

The roadmap and the documentation don't line up exactly. Microsoft Learn's developer guide, last updated November 13, says Listen is in public preview and has to be enabled for your tenant. The guide also warns that tool names, schemas and payload fields may change before general availability. A WindowsForum roundup of Ignite 2026 Work IQ announcements lists Listen event subscriptions as public preview, alongside Memory and human-approval governance. Treat it as a preview you can request, not a finished product.

The roadmap entry covers:

  • Products: Work IQ and Microsoft Copilot (Microsoft 365).
  • Platform: Web.
  • Cloud: Worldwide (Standard Multi-Tenant).
  • Rings: Preview, then General Availability.

How Listen works: the doorbell model​

Microsoft's documentation compares Listen to a doorbell. A notification tells your agent to wake up. It carries no work content and grants no access.

  1. A developer subscribes an agent to a supported event for one user.
  2. When the event fires, Listen calls the developer's registered HTTPS endpoint. The call carries identifiers, an opaque event reference and a fetch path.
  3. The agent connects to Work IQ with the user's delegated token and fetches the event and any related context.
  4. Access is checked when that fetch happens, even if the notification arrives days after the subscription was created.
  5. The agent prepares a private outcome, such as a draft reply, meeting brief or task list. It asks for explicit approval before sending, sharing, posting or scheduling anything.

Each subscription belongs to the user whose work generated the event. One person's agent never receives another person's events. For multi-person scenarios, each participant needs their own agent and subscriptions.

The seven preview events​

The preview catalog has seven scenarios, and availability can vary by tenant. Most use a base event plus a variant.

ScenarioBase eventVariant
Flagged email still unansweredResponseOwedFlaggedEmailAgingWithoutReply
Mention awaiting a response (email or chat)ResponseOwedEmailMentionWithoutEngagement or ChatMentionWithoutEngagement
Directly shared file not reviewedResponseOwedFileSharedNotReviewed
Upcoming one-on-one meetingMeetingUpcomingOneOnOneMeeting
Missed meetingMeetingMissedNone
Recap assigns action items to the userMeetingRecapReadyActionItemsAssignedToUser
Small meeting with external guests coming upMeetingUpcomingMeetingWithExternalInvitees

Some details affect design:

  • Events aren't instant. Each one fires only after its condition has held for a while, such as a wait for a reply or a lead time before a meeting.
  • Each event fires once per condition. Listen has no built-in later reminder, so an app has to schedule its own and recheck the source first.
  • You can't filter on content such as an email subject or body.
  • A meeting with an external guest can set two flags at once. A one-on-one with an outside guest sets both oneOnOneMeeting and meetingWithExternalInvitees, so route on every flag that is true.

What you need to run a pilot​

  • Work IQ enabled in the Microsoft 365 tenant.
  • Listen turned on for that tenant. Microsoft says to contact the Listen team about this during the preview.
  • The Work IQ MCP server and an MCP client.
  • A Microsoft Entra app registration with delegated permissions and both admin and user consent. App-only authentication isn't supported.
  • A publicly reachable HTTPS callback endpoint that you control. Listen validates it before delivering anything.
  • Test users and synthetic data. Events come from real activity, and there's no test-event or force-fire API.

Listen is reached through existing Work IQ MCP tools, not a separate one. It supports only the Work IQ MCP server with delegated authentication. REST, agent-to-agent and app-only access aren't available for Listen. That's narrower than Work IQ's broader API surface, which Microsoft introduced in April with agent-to-agent communication.

Setup sequence​

Microsoft's documented flow uses three MCP tools:

  1. Use fetch on /events/discovery and follow child paths until you reach a leaf.
  2. Use get_schema on that leaf path with the create operation to get the subscription schema.
  3. Use create_entity with the leaf as the parent URL. The body comes from the schema and includes a webhook delivery mode and your callback URL.

The create call returns a registrationId, a resourcePath and a status. If the status is pendingWebhookValidation, Listen sends a challenge to your callback. Delivery begins only after your endpoint answers and the subscription becomes active. Read the subscription back to confirm it.

Don't hard-code event paths from display names. The schema is authoritative. Microsoft also says its guide doesn't define the challenge response format or the callback authentication contract. Confirm both with the Listen team before building a production receiver. The Microsoft Graph change-notification handshake shouldn't be assumed to apply.

Building a receiver that holds up​

Microsoft recommends a thin callback that does four things in order:

  1. Validate the envelope, which carries the registration ID, a delivery ID, the event reference and the fetch path.
  2. Record the delivery ID.
  3. Hand the work to a worker or durable queue.
  4. Acknowledge quickly, without waiting for a model call or a user decision.

Delivery is at least once, so duplicates will happen. The documented deduplication keys are:

  • Flagged email: the event ID, flagged message ID and last-inbound time.
  • Mentions: the event ID and source item ID for each mention.
  • Shared file: the event ID, file ID and sharer email.
  • Meeting events: the event ID.

Never deduplicate on the event reference. Also plan for these gaps:

  • There's no guaranteed ordering, replay or latency commitment.
  • A mentions list holds at most 10 people.
  • An action-item list can be incomplete, so read the full recap when completeness matters.
  • Fetching an event doesn't consume it, but this isn't a replay API.
  • Underlying items can change between notification and action, so reread before acting.

Governance, privacy and cost​

For admins and security teams, the approval model matters most. Microsoft says a notification is a wake-up signal, not content and not consent. Several rules follow:

  • Treat messages, files and event content as data, never as instructions to the agent.
  • Don't log message bodies, summaries or file contents.
  • Before any visible write, show the user the acting account, channel, recipients or target, and the complete content. Get approval for that exact action.
  • If anything material changes, ask for approval again.
  • Meeting recaps and action items can contain AI-generated content, so verify facts, owners and dates.

On pricing, Listen uses existing Work IQ credit rates. Subscription calls are charged at the Work IQ Tool API rate. Wake-up notifications aren't charged during the preview. Fetching events and related content is billed as standard Work IQ tool calls. Microsoft says preview pricing can change before general availability.

Cleanup is a gap. Disabling your receiver doesn't cancel a subscription on the service side. The guide says to cancel subscriptions when a pilot ends or a user opts out. It doesn't specify the cancellation operation or schema, so confirm the procedure before starting a pilot.

Analysis​

This is a meaningful shift for agent design, with limits. Polling is wasteful, and webhooks are the standard fix. Microsoft has added a permission model that stays strict even when the agent is woken by an event.

Three limits temper the excitement. The catalog is small, with seven scenarios. The events are lagged by design. And the missing details on challenge format and cancellation mean this isn't production-ready yet. Microsoft's own mention of a "test tenant and synthetic data" says as much.

For IT admins, the practical steps are:

  • Confirm whether your tenant has Work IQ enabled.
  • Decide who gets to request Listen enablement.
  • Review which delegated permissions and consents a pilot app would need.
  • Insist on approval flows before any agent can send, share or schedule on a user's behalf.

If your pilot depends on a January 2027 general availability date, build in slack. The roadmap date is an estimate, and the preview documentation says schemas may still change.

 

References

  1. Work IQ: Listen Microsoft 365 Roadmap 2026-11-20T23:20:27.871175Z
  2. Work IQ Listen developer guide (preview) | Microsoft Learn learn.microsoft.com
  3. Microsoft Copilot Roadmap | Microsoft 365 microsoft.com