Approvals where you already are.
hosted MCPeventsCorin asks in Teams; you answer in one tap — nothing decided in a chat window skips a rule.
Microsoft Teams AI agent approvals — the card is the gate
on the wire: M365 Agents SDK · Adaptive Cards
01@corin in any channel
Ask for a status, a dry run, or a draft from the channel the work is already in. Built on the M365 Agents SDK — not a bot bolted on.
02Approvals as Adaptive Cards
A decision arrives as an Adaptive Card with the reasoning attached: the context, the recommendation, the margin. Approve or request changes without leaving the thread.
03Same gates, same record
An approval in Teams is the same gate as an approval anywhere else — identity from Entra ID, the outcome written to the ledger — a record of every decision: what changed, who approved it, when.
04No new surface to adopt
Teams is where your operations team already coordinates quotes, orders, and exceptions. Corin meets the work there instead of adding another tab to check.
The decision waits in the thread.
Sample thread — representative data, not a customer record.
Not a chatbot.
Not a document Q&A. It doesn't answer from a wiki — it acts on live decisions with ERP state attached.
Not another inbox. No console, no queue UI — approvals live in the thread.
Not a shadow approval path. Nothing approved in Teams bypasses the policy gates or the ledger.