Microsoft Teams Integration Setup

Purpose

Connect SuperSend to Microsoft Teams so your team receives reply notifications in a Teams channel when contacts respond to outbound email or LinkedIn campaigns. Notifications include contact details, a reply preview, and buttons to categorize leads or open Super Inbox.

This article is self-serve. Your IT team completes Part 1 once per Microsoft 365 tenant. Your SuperSend admin completes Part 2 in the SuperSend UI — the same pattern as Slack.

You do not create an Entra app, upload files, or configure Azure on your side. SuperSend hosts the Teams app and bot.

Who does what

Important: Microsoft Entra SSO for SuperSend login is separate

If your organization uses Microsoft Entra ID SSO to sign in to SuperSend (Admin → Security), that is a different Microsoft application from Microsoft Teams notifications.

Organizations on Entra SSO usually have stricter Microsoft 365 policies. Part 1 is required for those tenants. Clicking Connect in SuperSend without Part 1 often fails, or notifications arrive without working action buttons.

Reference — identifiers for IT search

Delegated permissions (tenant admin grants consent in Part 1, Step 1):

• User.Read
• Team.ReadBasic.All
• Channel.ReadBasic.All
• Standard OpenID scopes (openid, profile, offline_access)

Part 1 — IT administrator setup (one-time per tenant)

Complete every step before anyone connects Microsoft Teams inside SuperSend.

Step 1 — Grant admin consent for SuperSend

A Global administrator or Privileged role administrator grants consent once for the whole tenant.

Option A — Admin consent URL (recommended)

1. In Microsoft Entra admin center → Identity → Overview, copy your Tenant ID.
2. Open this URL in a browser (replace YOUR_TENANT_ID):

https://login.microsoftonline.com/YOUR_TENANT_ID/v2.0/adminconsent?client_id=8d28329f-ee5d-4184-acd4-97a50dd8ba04&redirect_uri=https%3A%2F%2Fapi.supersend.io%2Fv1%2Fteams%2Foauth%2Fcallback

3. Sign in as a tenant administrator.
4. Review permissions (Read user profile, Read team names, Read channel names).
5. Click Accept / Grant admin consent.
6. Confirm success (redirect or confirmation message).

Option B — Microsoft Entra admin center

1. Go to https://entra.microsoft.com.
2. Identity → Applications → Enterprise applications.
3. Search Super Send, or filter by application ID 8d28329f-ee5d-4184-acd4-97a50dd8ba04.

If missing, run Option A first.

4. Open the app → Permissions → Grant admin consent for [Your Organization] → Yes.

Step 2 — Allow SuperSend in your Teams app catalog

SuperSend is published as a Microsoft Teams app. Your admin allows it for the organization — you do not upload a package or build anything in Azure.

1. Sign in to Microsoft Teams admin center as Teams administrator or Global administrator.
2. Go to Teams apps → Manage apps.
3. Search SuperSend.
4. Open SuperSend (full name SuperSend Notifications).
5. Confirm the app is Allowed / available for your organization (not blocked).

If SuperSend does not appear:

1. Go to Teams apps → Manage apps → Actions → Org-wide app settings (or Permission policies / Setup policies, depending on your tenant).
2. Ensure apps from the Microsoft Teams app catalog (or Microsoft Store) are permitted.
3. Search Manage apps again for SuperSend or application ID 8d28329f-ee5d-4184-acd4-97a50dd8ba04.

If the app still does not appear, email support@supersend.io with your tenant domain and a note that SuperSend is missing from Manage apps. SuperSend will verify catalog availability for your tenant. You still do not upload files or register an Entra app.

Step 3 — Allow SuperSend in Teams permission policies (if needed)

Required when your tenant blocks third-party Teams apps.

1. Teams admin center → Teams apps → Permission policies.
2. Open the policy for users who will connect SuperSend (often Global (Org-wide default)).
3. Under Microsoft apps / Third-party apps (labels vary by tenant):
4. • Allow SuperSend, or
   • Allow apps from the catalog per your security baseline.
4. Save. Policy can take up to 24 hours (usually faster).

Also check Teams apps → Setup policies — add SuperSend to allowed apps if your org restricts installation.

Step 4 — Install SuperSend on the target Microsoft Team

Install on the Microsoft Team that should receive reply notifications (for example Sales or RevOps). Repeat per team if you need multiple channels.

Option A — Teams admin center

1. Teams → Manage teams → select the team.
2. Apps tab → Add apps (or +).
3. Search SuperSend → Add / Save.

Option B — Microsoft Teams client

1. Open the target team in Teams.
2. ⋯ next to team name → Manage team → Apps → Add apps.
3. Search SuperSend → Add.

Confirm SuperSend is listed under that team’s apps.

Step 5 — IT verification checklist

• Admin consent granted (Entra → enterprise app → Permissions shows granted for your org)
• SuperSend found in Teams admin center → Manage apps
• Permission policy allows SuperSend for relevant users (if your org uses restrictive policies)
• SuperSend installed on the target Microsoft Team (team → Apps tab)

When complete, send your SuperSend administrator this article starting at Part 2.

Part 2 — SuperSend administrator setup

Terminology: SuperSend Team = workspace in SuperSend (dropdown on Integrations). Microsoft Team = team in Microsoft Teams (chosen in the channel picker).

Step 1 — Connect Microsoft Teams

1. Sign in to https://app.supersend.io.
2. Admin → Integrations.
3. Select your SuperSend team from the Team dropdown.

Campaign integrations are hidden until a team is selected.

4. Integration Library tab → Campaign Integrations → Microsoft Teams.
5. Add (or Add Microsoft Teams Account).
6. Connect to Microsoft Teams.
7. Sign in with your Microsoft 365 work account (same tenant as Part 1).
8. Approve permissions if prompted.
9. SuperSend opens Select Microsoft Teams Channel.

OAuth or consent errors → Part 1 incomplete; return to your IT admin.

Step 2 — Choose Microsoft Team and channel

1. Under Microsoft Team, select the team where IT installed SuperSend (Part 1, Step 4).
2. Wait for channels to load.
3. Select the notification channel (for example General or supersend-replies).
4. Connect Channel.
5. Confirm: Microsoft Teams connected successfully.

Step 3 — SuperSend administrator verification

• Admin → Integrations shows Microsoft Teams connected
• Microsoft Team and channel match IT setup
• Continue to Part 3

Part 3 — Enable Microsoft Teams on campaigns

Part 2 does not enable every campaign automatically.

Campaign Integration Matrix

1. Admin → Integrations → Campaign Integration Matrix.
2. Microsoft Teams row → enable for each campaign.

Inside a campaign

1. Open campaign → Settings → Integrations.
2. Microsoft Teams → Enabled on.

What appears in Teams

Reply on an enabled campaign → adaptive card in your channel:

• Contact name, email, campaign, subject, interest status, reply preview
• View in Inbox, Mark Interested, Mark Not Interested, Categorize: Objection, Categorize: Meeting Scheduled

Covers email and LinkedIn replies.

End-to-end test

1. Part 1 and Part 2 checklists done.
2. Enable Teams on a test campaign (Part 3).
3. Trigger a reply on that campaign.
4. Card appears in the Teams channel within a few minutes.
5. Click View in Inbox and one categorize button.

Disconnecting

All Teams notifications for a SuperSend team: Admin → Integrations → Integration Library → Microsoft Teams → Delete.

One campaign only: disable in campaign Settings → Integrations or the Campaign Integration Matrix.

Troubleshooting

SuperSend UI

Microsoft 365 / IT

Still stuck?

Email support@supersend.io with tenant domain, Admin → Integrations screenshot, Part 1 checklist status, and exact error text.

Related articles

• Single Sign-On (SSO) for Your Organization — SuperSend login only; separate from Teams
• Integrations Overview
• Slack Integration Setup
• Work Conversations in Super Inbox

Updated on: 14/07/2026