Skip to content
docs

Microsoft Teams

Microsoft Teams integration uses Power Automate Workflows (“Post to a channel when a webhook request is received”). Vygl posts Adaptive Cards with the same content the Slack integration sends — severity breakdown, finding tables, AI verdicts, and links back into Vygl.

Setup

Section titled “Setup”

  1. Create a Power Automate Workflow. In Teams, open the target channel, click ⋯ → Workflows, and search for “Post to a channel when a webhook request is received”. Run the wizard, picking the channel that should receive notifications. Power Automate creates the workflow and shows a HTTP POST URL — copy it.

  2. Add the integration in Vygl. Open Settings → Integrations, click Add Microsoft Teams, paste the URL.

  3. Subscribe to events. Pick scan_completed, critical_finding, cve_critical, and any others you want.

  4. Apply filters — restrict by project, scan type, or severity.

  5. Test. Click Test on the integration row; an Adaptive Card should arrive in your channel within a few seconds.

What the card looks like

Section titled “What the card looks like”

A typical critical-finding card includes:

  • Header — project name, finding title, severity badge.
  • Facts — file location, rule ID, branch, commit SHA, scan duration.
  • AI verdict — when AI verification has run.
  • Action button — Open in Vygl deep link.

CVE Watch alerts use the same card pattern, scoped to the affected dependency.

Async delivery

Section titled “Async delivery”

Power Automate Workflows return HTTP 202 Accepted immediately and post the card to the channel asynchronously. If a card doesn’t appear in your channel:

  1. Check the Run history of the Power Automate workflow — failures show up there with full diagnostic info.
  2. Verify the workflow’s Teams connection is still authorized.
  3. Try the Test button in Vygl to fire a synthetic event.

Retries

Section titled “Retries”

Vygl retries on transport errors (3x with backoff). 4xx responses (workflow misconfigured, channel deleted) are logged but not retried — fix the upstream issue and re-test.