Connect Microsoft Teams
Connect UnitOps to Microsoft Teams so your team receives alerts in a channel and can ask the AI assistant questions from Teams.
Page: Admin -> Channels (/admin/channels) · Roles required: UnitOps admin plus Microsoft 365 tenant admin for the initial consent
What you get
- Channel alerts - rules such as "Forecast ready for approval" post automatically to the channel you choose, as Adaptive Cards.
- Per-user DMs - personal alerts arrive as direct messages from the UnitOps bot.
- AI chat - ask the assistant about sales, labor, or forecasts from Teams.
The provider is Teams Bot (Multi-workspace), built on the Bot Framework, so one connection can serve several tenants. There are no webhook URLs to paste for the standard flow.
Step 1: Connect your tenant
- In UnitOps, go to Admin -> Channels.
- Find the Microsoft Teams card and click Add to Teams.
- Consent to the UnitOps app so it can read your teams and send messages.
Once the tenant is connected, the card shows a Teams setup checklist that tracks the remaining steps and re-checks on demand.
Step 2: Choose the team and default channel
- Under Team UnitOps posts in, pick one of your teams. You no longer have to message the bot first.
- Choose a default channel. Alerts that have no channel of their own are posted there.
Step 3 (optional): Turn on chat with the assistant
Enable chat on the Teams card so people can ask the assistant questions in Teams as well as receive alerts.
Channel conversations are readable by everyone in the channel, so admins can review them under Admin -> AI Conversations. A direct message with the assistant is private: it is shown there only to an owner or an admin, and to nobody else.
Send a test message
Use the send action on the workspace row and confirm a connection-test message arrives in the default channel within a few seconds. If discovery of your teams is refused, the card explains why, which is almost always a missing consent rather than an outage.
Manual connection (advanced)
A platform admin can instead register a tenant-owned Azure AD app manually, providing the tenant ID, client ID, and client secret (vault://kv/teams-client-secret). This option is not available to regular organization admins; use it only when the standard Add to Teams consent flow is blocked.
Troubleshooting
| Symptom | Fix |
|---|---|
| No teams listed after connecting | Finish the tenant consent so UnitOps has Team.ReadBasic.All, then click Re-check |
| Alerts do not post to a channel | Confirm a default channel is set and the rule includes the teams channel in Notifications |
| Assistant does not answer in Teams | Turn on chat in Step 3; answers still respect the asking user's location permissions |