Teams · notifications
Microsoft Teams integration
Teams integration means your system posts a message, a card or a case link in a channel or to a user when something needs action. The good use case: “new case in your queue”, “approval waiting”, “ops is down”. The bad one: mirroring your whole admin into Teams and calling it an app. Incoming webhook is fastest and least flexible. Bot plus Adaptive Cards when people must tap Approve in the chat. Graph when you also touch calendar, files and members. Start with the smallest thing that removes a mail nobody reads. The user often has to install a Teams app in their tenant. That is onboarding, not a checkbox. The hub is [Microsoft 365](/articles/integrations/microsoft-365-integration).
Calendar and mail are Outlook. Files are SharePoint. Do not mix three Graph surfaces into the same “Teams project”. Automation that posts the right card.
Bot vs incoming webhook vs Graph
- Incoming webhook: fastest, least flexible
- Bot + Adaptive Cards: when people must tap Approve in the chat
- Graph: when you also touch calendar, files, members
Event
New case, pending approval, ops down.
Post
Channel or 1:1. Link back to the case in your system.
Action
Only when you need Approve in the chat do you build bot + card.
What to do now
Point to the mail nobody opens. That should be the first card in Teams. Also read the 365 hub, and write which mail you want to kill.
FAQ about Teams integration
Must the user install something?
Often yes — a Teams app in their tenant. That is onboarding, not a checkbox.
Is an incoming webhook enough?
Yes if you only need to post. No if someone must tap Approve in the chat.
May we mirror the whole admin in Teams?
You can. You should not. You get a worse admin and a larger scope.
Does the meeting link belong to Teams or Outlook?
The meeting is often created via Graph/Outlook and gets a Teams link. Spec it as one flow, not two projects.