Channels, chats, and meetings
Raise agent work anywhere in Teams; results and progress come back where the request was made.
Same platform, native to Microsoft 365.
Context installs into Microsoft Teams: agents work inside channels, chats, and meetings, authenticate through Entra ID, and post approvals as native cards. Built for organizations that live in Microsoft 365.
Vendor review
Operations
Jordan Patel
Context, prepare the renewal review for Acme Cloud.
Acme Cloud · $240k annual
Usage is within plan. Two duplicate licenses and a 7% price increase need review before renewal.
Identity
Jordan · Operations
Sources
Contract + usage
How it works
Each run keeps the request, actions, evidence, and final decision together.
01 · Request
Ask Context to run a configured workflow. The request retains the Teams conversation and Microsoft 365 identity.
Output · Entra principal resolved
02 · Review
Context returns a native card with the artifact, sources, and the action waiting for a decision.
Output · Approval card posted
03 · Complete
The selected action runs under the configured policy and the final record is linked back to the conversation.
Output · Run filed to Context
What you can inspect
Raise agent work anywhere in Teams; results and progress come back where the request was made.
Review and sign off on agent output with adaptive cards, without leaving Teams.
Each configured action uses an Entra ID principal and scope approved for the workflow.
Runs retain an action trail and can be configured around your Microsoft 365 retention and governance requirements.
Deployment boundaries
Context in Teams can run as a standalone surface, while its traces, evals, and policy decisions remain part of the same Context system.
A Microsoft 365 administrator approves the Context app and the scopes required by each enabled workflow.
An adaptive card does not bypass Context policy; restricted actions still require the configured reviewers.