Skip to main content

Microsoft Teams

The AISafe Microsoft Teams integration sends assessment and finding notifications to Teams channels via Power Automate Workflow webhooks. It is a notification-only integration. Alongside Slack, Teams is one of two first-party notification providers.

How it works​

AISafe posts to Power Automate Workflow webhooks. Power Automate now issues these URLs on *.environment.api.powerplatform.com. It retired the older *.logic.azure.com workflow URLs on 30 November 2025. If your saved Teams target still uses a logic.azure.com URL, create a new URL in Power Automate and save it in AISafe. Microsoft is also decommissioning the legacy Office 365 Connector surface (*.webhook.office.com), so new Teams targets must use the Workflow surface. AISafe rejects configurations pointing at the legacy endpoint.

Unlike Slack, Teams does not use OAuth when AISafe posts a message. The Workflow webhook URL itself acts as the credential. AISafe encrypts the URL at rest and does not display it in full after saving.

Setting up a Workflow webhook​

  1. In the Teams channel that should receive AISafe alerts, click the channel menu (...) and pick Workflows.
  2. Search for the template Post to a channel when a webhook request is received and select it.
  3. Complete the workflow setup: sign in if prompted, confirm the team and channel, and let Power Automate provision the workflow.
  4. Copy the generated HTTPS URL. Its host ends in .environment.api.powerplatform.com.

Paste the URL plus a friendly channel name into AISafe at Integrations → Chat notifications → Microsoft Teams (org-wide, admin+) or the per-assessment Settings → Notifications tab.

Supported events​

Teams targets receive the same events as Slack:

  • Assessment completed: AISafe posts when an assessment finishes.
  • Finding confirmed: AISafe posts when a triager confirms a finding.
  • Report ready: AISafe posts when a report is ready to download.

Delivery is at-least-once. AISafe retains delivery and attempt logs for 30 days.

Rate limiting​

Microsoft documents the Workflow webhook rate limit at about 4 posts per second per webhook. AISafe enforces a per-webhook token bucket at this rate. When a send would exceed the budget, AISafe requeues the delivery rather than dropping it.

If Teams returns HTTP 429 with a Retry-After header, AISafe honors the header value (capped at one hour). For other 4xx responses, AISafe marks the delivery as failed and stops retries.

Limitations​

  • One active Teams target per organization. Revoke the active target before configuring a new channel.
  • Notification only. AISafe posts one-way notifications; AISafe does not consume replies.
  • Power Automate Workflow webhooks only. AISafe does not support the Teams Bot Framework.