teams-meeting-pipeline

You can automate Microsoft Teams meeting summaries by running CLI operations to process meeting transcripts and generate action items. The pipeline manages the underlying Microsoft Graph webhook flow to ensure meeting notifications keep arriving for processing.

Managing Microsoft Graph webhook subscription expiry involves using CLI operations to create, renew, and delete subscriptions. This maintains the webhook flow so meeting notifications continue arriving, preventing pipeline disruptions during operational health checks.

To replay failed Teams meeting summary jobs, use CLI operations to list and inspect stored jobs, then execute a replay run. This allows production troubleshooting by reprocessing meetings that previously failed during transcript resolution or summarization.

Yes, Hermes CLI access is required to operate the Teams meeting summary pipeline. You also need Microsoft Graph tenant and client credentials to authenticate webhook subscriptions and validate configuration snapshots during operational health checks.

Token health checks for the Teams meeting summary pipeline fail when Microsoft Graph tenant or client credentials are misconfigured or expired. Running a validation operation captures a configuration snapshot to identify authentication issues before performing dry-run transcript resolutions.

Yes, you can validate Microsoft Graph configuration by running a dry-run transcript resolution. This operational validation checks token health and configuration snapshots without processing a full Teams meeting transcript, confirming the pipeline is ready for production.