Integrate Apache Superset with Microsoft Teams 2026

Integrating Apache Superset with Microsoft Teams allows sending alerts and reports directly into Teams channels. For Microsoft organizations, it's the equivalent of Slack integration. This guide details the setup in 2026.

1. Prerequisites

• A Microsoft Teams workspace;
• Right to create connectors / Power Automate flows;
• An accessible Superset instance.

If you want preconfigured Teams integration, TVL Managed Superset offers a Teams setup on Pro+ instances.

2. Method 1 — Teams webhook

The simplest approach:

1. In Teams → target channel → ... → Connectors → Incoming Webhook;
2. Create a webhook, give it a name and a logo;
3. Copy the URL;
4. In Superset alert/report, choose URL/Webhook as method and paste the URL.

3. Adaptive Card format

Teams uses Adaptive Cards. Superset must send a JSON with the right format:

{
  "@type": "MessageCard",
  "summary": "Superset Alert",
  "title": "Churn spike detected",
  "text": "More than 5% churn in the last 24h",
  "potentialAction": [{
    "@type": "OpenUri",
    "name": "View dashboard",
    "targets": [{
      "os": "default",
      "uri": "https://superset.example.com/dashboard/42"
    }]
  }]
}

4. Method 2 — Power Automate (Flow)

For richer integrations:

1. Power Automate → Create flow → Triggered by webhook;
2. Add a "Post message in Teams" step;
3. Map Superset fields → Teams message;
4. Paste the flow URL in Superset.

5. Method 3 — Custom bot

For interactive /superset commands in Teams:

• Microsoft Bot Framework;
• Custom backend calling the Superset API;
• Natural skills (NL2SQL via OpenAI/Anthropic).

This configuration is applied by default on TVL Managed Superset, which follows community best practices.

6. Typical use cases

• Business alert: churn spike → ping #cs-team;
• Weekly reporting: Monday MRR in #leadership;
• Incidents: high 5xx rate → #ops-alerts;
• Wins: deal closed → #sales;
• Daily summary: business KPIs at 9am.

7. Throttling and best practices

• Maximum 5 alerts/hour to avoid spam;
• Criticality level: route warning vs critical;
• Direct link to dashboard in each card;
• Superset / your logo in the webhook.

8. Teams vs Slack comparison

Criterion	Slack	Teams
Native Superset integration	Bot token	Webhook
Message format	Block Kit	Adaptive Card
Interactive bot	Standard	Bot Framework
Audience	Tech, startups	Enterprise, Microsoft

9. Common pitfalls

• Webhook URL expired after 6 months of non-use;
• Malformed Adaptive Card: message rejected;
• Teams rate limit: 4 messages/second per webhook;
• Image attachment not supported in webhook (use dashboard link).

10. Conclusion

Microsoft Teams integration for Apache Superset is straightforward via webhook for simple needs. For interactive bots, custom development is heavier than with Slack but remains feasible. For most Microsoft organizations, simple webhook is enough.

Want the benefits of Apache Superset without the friction of installation and maintenance? Deploy your instance in 3 clicks with TVL Managed Superset, hosted in Europe (OVHcloud, Roubaix, France).

For more: Slack integration, Superset alerts, scheduled reports.