Integrations/Microsoft Teams
Microsoft Teams logo

Microsoft Teams + Courier

Turn Microsoft Teams into a notification channel for your users

Microsoft Teams is where your users already work. Courier lets you deliver your product's notifications there too, from the same API and templates.

Overview

What Microsoft Teams is

Microsoft Teams is the collaboration hub where enterprise teams spend their workday, so it is a place your users already want updates from the products they use.

Courier adds Microsoft Teams as another channel in your existing notification system, with the same templates, routing, and preferences as email, SMS, push, and inbox. There is no separate Teams integration to build.

You need a Courier account and a Teams bot registered in Azure, so your users can receive messages in Teams.

Why Courier

What you get with Microsoft Teams + Courier

Use cases

What teams build with it

Let users opt in to receive your product's notifications, mentions, assignments, approvals, and digests, right in Microsoft Teams
Give each user a channel preference, so some get email and others get Teams from the same send
Add Teams to an existing notification journey without wiring a new integration
Let a user act on a notification from Teams, then continue the flow in your product
Deliver into a customer's own Teams tenant, not just your team's

Setup

Connect it in minutes

An admin adds Microsoft Teams once on the Integrations page in Courier. Once connected, anyone on your team can deliver notifications to Teams from any notification, alongside every other channel.

1
Register a Teams bot
Create a Teams app in the Developer Portal and an Azure App Registration for the bot, then grant it the Microsoft Graph permissions to send messages.
2
Add the bot credentials in Courier
Open Integrations, select Microsoft Teams, and enter the bot's Application (client) ID and Client Secret from its Azure App Registration.
3
Send from your app
Call the Send API with a recipient whose profile includes their Teams details. Courier delivers through Teams, plus any other channels you add.

FAQ

Frequently asked questions

Can I use Microsoft Teams with Courier?

Yes. Courier supports Microsoft Teams as a notification channel, so you can reach your users in Teams. It sits alongside your other channels in Courier's multichannel stack, all driven through one Send API.

Can I send notifications to my users on Microsoft Teams?

Yes. Your users receive notifications as direct messages from your Teams bot. Courier sends through the bot you register in Azure, so recipients get product updates right in their Teams chat.

What do I need to connect Microsoft Teams to Courier?

You need an Azure App Registration, a Teams app, and a Teams bot, plus admin rights to approve the API permissions. The bot's credentials are what you add to your Courier Teams provider.

How does Courier authenticate with Microsoft Teams?

Courier authenticates using your bot's Azure App Registration. You supply the Application (client) ID and Client Secret generated in Azure, taken from the bot's registration rather than the Teams Developer Portal app.

How does Courier know which Teams user to notify?

Each recipient's Courier profile carries an ms_teams object holding tenant_id and service_url, plus one target such as user_id, email, or conversation_id. Courier uses those fields to route the message.

What message formats can I send to Microsoft Teams?

Courier supports plain text and Microsoft Teams Adaptive Cards with interactive elements, designed in the template editor. You can add @mentions inside cards using <at>username</at> with a matching entities object.

Is Microsoft Teams just for internal alerts with Courier?

No. Teams is a user-facing notification channel in Courier, not only internal ops or alerting. You can send end-user product notifications there alongside email, SMS, push, and the in-app Courier Inbox.

More

Related integrations