Microsoft Teams
Post messages, trigger workflows, and bridge cross-tool automation through Microsoft Teams — bot-based integration via Azure Bot Framework.
Productivity & OfficeAvailable now
Microsoft Teams is the chat and meeting surface for most Microsoft-365-anchored organizations. The integration lets myai post messages, deliver notifications, and trigger workflows from Teams — through a bot app registration in your tenant — so the automations your other tools already participate in extend cleanly into the channel where your team is actually paying attention.
What you can do
- Post messages from automations — a function drops a structured update (CRM change, deploy status, customer signal) into the right channel at the right moment.
- Direct-message specific people — for the times when a channel post is too noisy, send a 1:1 to whoever needs to act.
- Adaptive Card messages — rich, structured messages with buttons and tables, not just plain text.
- Bridge cross-tool workflows — a HubSpot deal change, a Linear issue closure, or a customer email triggers a Teams post for visibility.
- Trigger workflows from mentions —
@myai summarize this threadbecomes an action your team invokes without leaving Teams. - Multi-tenant support — one app registration can serve multiple Workspace tenants if needed.
How to connect
Azure Bot Framework App Registration in your tenant. This is different from a user-OAuth integration like Outlook — the Teams integration is a bot, which means it needs its own app secret and admin consent.
Setup (admin, one-time):
- Create an Azure Bot resource in the Azure Portal. The resource generates the App (Client) ID.
- Generate an app secret (App Registrations → your bot → Certificates & secrets → New client secret). Copy immediately — Azure only shows it once.
- Add the Microsoft Teams channel to your Bot resource.
- Set the bot's messaging endpoint to the myai inbound webhook (varies by deployment — your contact at myai will provide).
- Grant the application permissions the bot needs (
ChannelMessage.Send,Team.ReadBasic.All) and have an admin consent to them. - Provide the Client ID and App Secret in the integration form. Tenant ID is optional (blank for multi-tenant).
Common use cases
- Customer-success channel feed — every new high-priority signal from CRM, support, or product analytics posts to a dedicated channel with full context inline.
- Engineering alerts — Linear status changes, deploy events, andon escalations flow to the right Teams channel without copy-paste.
- In-line summarization —
@myai summarize this threaddigests a long Teams conversation and posts the recap back inline.
Reference
- Connection model: Azure Bot Framework app registration (admin setup, one-time)
- Required Graph permissions:
ChannelMessage.Send,Team.ReadBasic.All(application permissions, admin consent required) - Bot must be added to channels before it can post — Teams permission model enforced