Surfaces

Context in Teams

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.

Context in Teams
Example workflow

Vendor review

Operations

JP

Jordan Patel

Context, prepare the renewal review for Acme Cloud.

CContext · Renewal review

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

Approve recommendationOpen run

How it works

From request to a reviewable result.

Each run keeps the request, actions, evidence, and final decision together.

  1. 01 · Request

    Start from a chat or channel.

    Ask Context to run a configured workflow. The request retains the Teams conversation and Microsoft 365 identity.

    Output · Entra principal resolved

  2. 02 · Review

    Inspect the proposed result.

    Context returns a native card with the artifact, sources, and the action waiting for a decision.

    Output · Approval card posted

  3. 03 · Complete

    Approve without leaving Teams.

    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

Capability is only useful when it leaves evidence.

Channels, chats, and meetings

Raise agent work anywhere in Teams; results and progress come back where the request was made.

Recorded with the runConversation-linked run

Approvals as native cards

Review and sign off on agent output with adaptive cards, without leaving Teams.

Recorded with the runAdaptive Card decision

Entra ID throughout

Each configured action uses an Entra ID principal and scope approved for the workflow.

Recorded with the runApproved principal and scope

Auditable by design

Runs retain an action trail and can be configured around your Microsoft 365 retention and governance requirements.

Recorded with the runExportable action trail

Deployment boundaries

Control is part of the product.

Context in Teams can run as a standalone surface, while its traces, evals, and policy decisions remain part of the same Context system.

Tenant setup

A Microsoft 365 administrator approves the Context app and the scopes required by each enabled workflow.

Policy remains explicit

An adaptive card does not bypass Context policy; restricted actions still require the configured reviewers.

See how it works with Workspace

Talk to us.
Bring a workflow your team runs today and see it run in your environment.