Teams Meetings

Use the Teams meeting pipeline when you want Mibyan to ingest Microsoft Graph meeting events, fetch transcripts first, fall back to recordings plus STT when needed, and deliver a structured summary to downstream sinks. Prerequisites: see Microsoft Teams for the underlying bot/credential setup.

Run mibyan gateway setup and pick Teams Meetings for a guided walk-through.

This page focuses on setup and enablement:

Graph credentials
webhook listener configuration
Teams delivery modes
pipeline config shape

For day-2 operations, go-live checks, and the operator worksheet, use the dedicated guide: Operate the Teams Meeting Pipeline.

What This Feature Does

The pipeline:

receives Microsoft Graph webhook events
resolves the meeting and prefers transcript artifacts first
falls back to recording download plus STT when no usable transcript is available
stores durable job state and sink records locally
can write summaries to Notion, Linear, and Microsoft Teams

Operator actions stay in the CLI (the teams-pipeline subcommand is registered by the teams_pipeline plugin — enable it via mibyan plugins enable teams_pipeline or set plugins.enabled: [teams_pipeline] in config.yaml):

mibyan teams-pipeline validate
mibyan teams-pipeline list
mibyan teams-pipeline maintain-subscriptions

Prerequisites

Before enabling the meetings pipeline, make sure you have:

a working Mibyan install
the existing Microsoft Teams bot setup if you want Teams outbound delivery
Microsoft Graph application credentials with the permissions required for the meeting resources you plan to subscribe to
a public HTTPS URL that Microsoft Graph can call for webhook delivery
ffmpeg installed if you want recording-plus-STT fallback

Step 1: Add Microsoft Graph Credentials

Add Graph app-only credentials to ~/.mibyan/.env:

MSGRAPH_TENANT_ID=<tenant-id>
MSGRAPH_CLIENT_ID=<client-id>
MSGRAPH_CLIENT_SECRET=<client-secret>

These credentials are used by:

the Graph client foundation
subscription maintenance commands
meeting resolution and artifact fetches
Graph-based Teams outbound delivery when you do not provide a dedicated Teams access token

Step 2: Enable the Graph Webhook Listener

The webhook listener is a gateway platform named msgraph_webhook. At minimum, enable it and set a client state value:

MSGRAPH_WEBHOOK_ENABLED=true
MSGRAPH_WEBHOOK_PORT=8646
MSGRAPH_WEBHOOK_CLIENT_STATE=<random-shared-secret>
MSGRAPH_WEBHOOK_ACCEPTED_RESOURCES=communications/onlineMeetings

The bind host is read from the platform’s extra.host in config.yaml (there is no MSGRAPH_WEBHOOK_HOST env var — see the webhook listener reference). The listener exposes:

/msgraph/webhook for Graph notifications
/health for a simple health check

You need to route your public HTTPS endpoint to that listener. For example, if your public domain is https://ops.example.com, your Graph notification URL would typically be:

https://ops.example.com/msgraph/webhook

Step 3: Configure Teams Delivery and Pipeline Behavior

The meeting pipeline reads its runtime config from the existing teams platform entry. Pipeline-specific knobs live under teams.extra.meeting_pipeline. Teams outbound delivery stays on the normal Teams platform config surface. Example ~/.mibyan/config.yaml:

platforms:
  msgraph_webhook:
    enabled: true
    extra:
      host: 127.0.0.1
      port: 8646
      client_state: "replace-me"
      accepted_resources:
        - "communications/onlineMeetings"

  teams:
    enabled: true
    extra:
      client_id: "your-teams-client-id"
      client_secret: "your-teams-client-secret"
      tenant_id: "your-teams-tenant-id"

      # outbound summary delivery
      delivery_mode: "graph" # or incoming_webhook
      team_id: "team-id"
      channel_id: "channel-id"
      # incoming_webhook_url: "https://..."

      meeting_pipeline:
        transcript_min_chars: 80
        transcript_required: false
        transcription_fallback: true
        ffmpeg_extract_audio: true
        notion:
          enabled: false
        linear:
          enabled: false

If you bind the listener to a non-loopback host such as 0.0.0.0, you must also set allowed_source_cidrs to Microsoft’s webhook egress ranges. Loopback binds (127.0.0.1 / ::1) are the intended dev-tunnel and local reverse-proxy setup.

Teams Delivery Modes

The pipeline supports two Teams summary-delivery modes inside the existing Teams plugin.

`incoming_webhook`

Use this when you want a simple webhook post into Teams without channel-message creation through Graph. Required config:

platforms:
  teams:
    enabled: true
    extra:
      delivery_mode: "incoming_webhook"
      incoming_webhook_url: "https://..."

`graph`

Use this when you want Mibyan to post the summary through Microsoft Graph into a Teams chat or channel. Supported targets:

chat_id
team_id + channel_id
team_id + home_channel fallback for the existing Teams platform

Example:

platforms:
  teams:
    enabled: true
    extra:
      delivery_mode: "graph"
      team_id: "team-id"
      channel_id: "channel-id"

Step 4: Start the Gateway

Start Mibyan normally after updating config:

mibyan gateway run

Or, if you run Mibyan in Docker, start the gateway the same way you already do for your deployment. Check the listener:

curl http://localhost:8646/health

Step 5: Create Graph Subscriptions

Use the plugin CLI to create and inspect subscriptions. Examples:

mibyan teams-pipeline subscribe \
  --resource communications/onlineMeetings/getAllTranscripts \
  --notification-url https://ops.example.com/msgraph/webhook \
  --client-state "$MSGRAPH_WEBHOOK_CLIENT_STATE"

mibyan teams-pipeline subscribe \
  --resource communications/onlineMeetings/getAllRecordings \
  --notification-url https://ops.example.com/msgraph/webhook \
  --client-state "$MSGRAPH_WEBHOOK_CLIENT_STATE"

Graph subscriptions expire in 72 hoursMicrosoft Graph caps webhook subscriptions at 72 hours and will not auto-renew them. You MUST schedule mibyan teams-pipeline maintain-subscriptions before going live, or notifications will silently stop three days after any manual subscription creation. See Automating subscription renewal in the operator runbook — three options (Mibyan cron, systemd timer, plain crontab).

For subscription maintenance and day-2 operator flows, continue with the guide: Operate the Teams Meeting Pipeline.

Validation

Run the built-in validation snapshot:

mibyan teams-pipeline validate

Useful companion checks:

mibyan teams-pipeline token-health
mibyan teams-pipeline subscriptions

Troubleshooting

Problem	What to check
Graph webhook validation fails	Confirm the public URL is correct and reachable, and that Graph is calling the exact `/msgraph/webhook` path
Jobs do not appear in `mibyan teams-pipeline list`	Confirm `msgraph_webhook` is enabled and that subscriptions point at the right notification URL
Transcript-first never succeeds	Check Graph permissions for transcript resources and whether the transcript artifact exists for that meeting
Recording fallback fails	Confirm `ffmpeg` is installed and the Graph app can access recording artifacts
Teams summary delivery fails	Re-check `delivery_mode`, target IDs, and Teams auth config

تطبيق ديسكتوب

البداية

استخدام مبيان

الميزات

منصات المراسلة

التكاملات

الأدلة والدروس

دليل المطوّر

المرجع

What This Feature Does

Prerequisites

Step 1: Add Microsoft Graph Credentials

Step 2: Enable the Graph Webhook Listener

Step 3: Configure Teams Delivery and Pipeline Behavior

Teams Delivery Modes

`incoming_webhook`

`graph`

Step 4: Start the Gateway

Step 5: Create Graph Subscriptions

Validation

Troubleshooting

​What This Feature Does

​Prerequisites

​Step 1: Add Microsoft Graph Credentials

​Step 2: Enable the Graph Webhook Listener

​Step 3: Configure Teams Delivery and Pipeline Behavior

​Teams Delivery Modes

​incoming_webhook

​graph

​Step 4: Start the Gateway

​Step 5: Create Graph Subscriptions

​Validation

​Troubleshooting

​Related Docs

What This Feature Does

Prerequisites

Step 1: Add Microsoft Graph Credentials

Step 2: Enable the Graph Webhook Listener

Step 3: Configure Teams Delivery and Pipeline Behavior

Teams Delivery Modes

`incoming_webhook`

`graph`

Step 4: Start the Gateway

Step 5: Create Graph Subscriptions

Validation

Troubleshooting

Related Docs