Resources / Integrations / Microsoft Teams

Microsoft Teams

Weekly prompts and new-intro cards in a Teams channel through a webhook URL your admin creates, and, once enabled for your organization, private Teams messages from the Mucho Gusto bot.

Last verified against our product: October 4, 2026

Availability

Channel notifications available; bot direct messages ship dark and are being verified with a first partner organization

The Teams bot has been tested against simulated Microsoft services only. It is switched off for every organization until we have verified it live. There is no Teams calendar or directory integration.

How an admin connects it

Channel posts need a Teams Workflows webhook URL for one channel and no Microsoft permission. Direct messages need a one-time Microsoft admin approval, then the app uploaded to your Teams admin center.

Who can set it up: Organization admin (channel webhook); a Microsoft 365 Global Administrator (bot).

Channel posts: in Teams, create a Workflows webhook for the channel that should receive posts and copy its URL.
In the Mucho Gusto admin console, open the Teams card, paste the URL and use the test button to send a sample card.
Direct messages: in the admin console, open Teams direct messages and select Connect with Microsoft. A Global Administrator approves the permissions on Microsoft's screen.
In the Teams admin center, go to Teams apps, Manage apps, Upload new app, and upload the Mucho Gusto app package we send you.
Optional: in Teams apps, Setup policies, add Mucho Gusto under Installed apps (and Pinned apps) so everyone gets it without searching.
People who have the app receive a welcome message. Each person can turn Teams messages off in Mucho Gusto notification settings.

Permissions requested

Permission or scope	What it allows
`(webhook)`	Channel posts request no Microsoft permission.
`Microsoft Graph application permission: User.Read.All`	Lets the bot match your people to their Teams accounts by work email address. Read-only directory lookup.
`Microsoft Graph application permission: TeamsAppInstallation.ReadWriteSelfForUser.All`	Lets the bot add the Mucho Gusto app to a person's own Teams so it can message them. It cannot install any other app.

The bot only ever sends messages containing links. It does not read chats, channels, files or calendars. We only accept channel webhook URLs on Microsoft's own Workflows and Office hosts. A webhook URL acts as a credential, is stored per organization and is never shown back after you save it.

Data we read

Read

Bot: each person's work email address and Microsoft account id (to find their Teams account), and the id of the private conversation created when they install the app (so we can message them).
Channel posts: nothing is read from Teams.

Not read

Messages, channels, members' chats, files or calendars

How the data is used

A new-intro card when a coworker posts an intro (channel).
A weekly prompt card (Mondays, 15:00 UTC) inviting people to record (channel).
Private messages before a meeting with someone you have not met and periodic people-to-meet suggestions, each with Watch intro link buttons (bot, when enabled).

Sync frequency

Channel posts are event-driven plus the Monday 15:00 UTC prompt. The bot matches people to Teams accounts on the daily directory pass and stores a conversation reference when someone installs the app.

Disconnecting and purging data

How: Admin console, Teams card, Disconnect for the channel webhook; Teams direct messages, Disconnect for the bot. Also remove the app in the Teams admin center and revoke consent under Entra ID, Enterprise applications.

Our stored webhook URL is deleted and channel posts stop.
Bot disconnect deletes the stored Microsoft tenant link and stops all direct messages.

What remains: Teams account matches and conversation references are removed when the organization is deleted.

Back to all integrations

Questions or a correction? [email protected]. See also: Security, Subprocessors, Privacy, Terms.