Native Microsoft Teams notifications without Power Automate

[KristiDodaj]

Is your feature request related to a problem? Please describe.

Sending Superset webhook notifications to Microsoft Teams currently requires an intermediary, such as Power Automate, to translate the payload and post the message.

Organizations that cannot use Power Automate need to maintain their own service for Teams delivery.

Describe the solution you’d like

Add Microsoft Teams as a notification destination in Alerts & Reports, following the direct-delivery pattern of Superset’s existing Slack integration.

Administrators would configure Microsoft application credentials and permitted channel destinations. Users would select Teams and a configured destination when creating an alert. Superset would format and deliver the notification through a supported Microsoft messaging mechanism, without requiring Power Automate or a separately hosted webhook relay.

The initial scope would include:

• Delivery to configured Teams channels.
• Attachment-free alerts containing the alert name, description, and chart or dashboard link.
• Clear configuration and delivery errors.
• Tests covering message formatting and failed delivery.

Screenshots, file attachments, scheduled reports, direct messages, and interactive features would remain outside the initial scope.

Before implementation, we would appreciate maintainer feedback on whether this belongs in Superset core. We propose investigating a Teams bot approach, with authentication, app installation, permissions, and destination configuration agreed upon before development.

Describe alternatives you’ve considered

• Power Automate: Receive Superset webhook payloads, format them, and post to Teams.
• Email to a Teams channel: Where enabled, a Teams channel has an email address that Superset’s existing email notifications can target. This produces an email-style post rather than a native bot notification. See Microsoft’s channel email documentation.

Power Automate requires maintaining a workflow, while channel email depends on email integration being enabled and permitted senders being configured. The proposed integration would provide native bot notifications directly from Superset.

Additional context

Microsoft retired Office 365 connectors in Teams, including the legacy Incoming Webhook connector, with the final shutdown rollout scheduled for May 18–22, 2026. The replacement Workflows webhooks rely on Power Automate.

Teams delivery interest was expressed in PR #36127. Generic webhook support is covered by Discussion #33268.

Would be happy to take this on if there is traction :)