Connect Microsoft Teams
Connect your Microsoft account from the tenant portal so voice agents can post messages to a Teams channel for hand-offs, hot leads, and booking alerts.
Connect Microsoft Teams
Voice agents can post a message to a Microsoft Teams channel when Teams is connected per tenant — useful for hand-offs, hot leads, or booking notifications. Clients connect their own Microsoft account from the tenant portal — operators do not need Microsoft API keys or a separate automation.
Time: ~2 minutes
Prerequisites
- Tenant portal access (API key from your agency, or staff login at
/login) - A Microsoft 365 account that is a member of the Team you want the agent to post to
- An active agent with the Teams tool enabled (your operator configures this)
Steps (client self-serve)
- Open the tenant portal:
https://voice.makeautomation.ai/login - Sign in with your tenant API key (provided by your agency).
- Go to Integrations (
/portal/integrations). - Under Microsoft Teams, click Connect.
- Sign in with Microsoft and approve access when Microsoft prompts you.
- Return to the portal — status should show Connected.
If you have multiple Microsoft accounts, pick the one that belongs to the workspace whose channel the agent should post to.
After connecting (operator)
- Open the agent in the admin dashboard.
- In Integrations, add the Microsoft Teams tool (post channel message).
- Set the tool's team ID and channel ID in the agent configuration (see below). The agent never asks the caller for these — they come from configuration.
Find your team and channel IDs
The post_teams_channel_message tool needs a team ID (a GUID) and a channel ID (format 19:…@thread.tacv2). The easiest way to get both:
- In the Teams desktop or web app, open the channel you want the agent to post to.
- Click the ⋯ (More options) next to the channel name and choose Get link to channel.
- The link contains both IDs, URL-encoded — for example:
https://teams.microsoft.com/l/channel/19%3Aabc...%40thread.tacv2/General?groupId=1111-2222-3333&tenantId=...- The
channelIdis the19:…@thread.tacv2segment (decode%3A→:and%40→@). - The
groupIdquery parameter is the team ID (GUID).
- The
- Paste both into the agent's Teams tool configuration.
If you cannot find them, ask your operator — they can also look up team and channel IDs via the Composio actions MICROSOFT_TEAMS_LIST_USER_JOINED_TEAMS (returns each team id) and MICROSOFT_TEAMS_TEAMS_LIST_CHANNELS (returns each channel id for a team).
Troubleshooting
| Issue | What to check |
|---|---|
| Connect button does nothing | Pop-up blocker; allow the OAuth window |
| Status stays Pending | Complete the Microsoft consent screen; retry Connect |
| Consent blocked by admin | Your Microsoft 365 org may require admin approval for the ChannelMessage.Send permission — ask your IT admin to grant admin consent |
| Message never appears | Confirm the connected account is a member of that Team, and the team/channel IDs in the agent config are correct |
| Wrong workspace | Disconnect and reconnect with the intended Microsoft account |
Related
- Client help: connect Outlook Calendar for Microsoft 365 tenants
- Operators: full GHL + CRM setup → Admin → Runbooks → SOP 05 — GHL client onboarding
- Technical reference: Composio connected apps (internal)