The complete guide
Slack and Microsoft Teams integration: the complete guide
Updated November 18, 2026 · Published by Danny Rathod, Founder, StackLift AI. Written with AI assistance; how we make content.
Short answer
A Slack or Microsoft Teams integration puts an assistant or workflow inside the chat tools your team already uses, for HR, IT and policy questions, approvals and alerts. Slack apps use OAuth and the Events API; Teams bots use the Azure Bot Framework. Effort depends on the knowledge sources, permissions, approvals and how both platforms are supported.
What does a Slack or Teams integration do?
People ask questions and make requests in chat all day. An integration lets a bot or app answer and act there, so staff do not switch to another portal. The most common use is an internal assistant that answers from your own documents.
- Answer HR, IT and policy questions from approved documents. See AI chatbot development.
- Open and update tickets from a chat message.
- Route approvals, such as time off or purchases, with buttons.
- Post alerts from monitoring, CRM or billing tools to the right channel.
- Look up customer or order details with a command.
- Summarize long threads for people who join late.
How does a Slack or Teams integration work?
In Slack, you create an app, install it into a workspace through OAuth and get a bot token with the scopes you asked for. Slack sends events such as messages and mentions to your server through the Events API, either to a public HTTPS endpoint or over Socket Mode. Messages are laid out with Block Kit.
In Microsoft Teams, a bot is built on the Azure Bot Framework. Teams sends activities such as messages to your bot's endpoint, and your service must check the token Microsoft signed before it trusts a request. Replies use Adaptive Cards for rich layouts. The two platforms differ in identity, install rules and message format, so supporting both is more than one build with two logos.
What data moves, and in which direction?
| Data | Direction | How often |
|---|---|---|
| User messages and commands | Slack or Teams to your service | Per message or command |
| Replies, cards and buttons | Your service to Slack or Teams | Per reply |
| Button clicks and approvals | Slack or Teams to your service | Per action |
| Alerts and notices | Your systems to a channel | Per event |
| Knowledge documents | Your sources to a search index | Scheduled sync |
What drives the effort of a chat integration?
The typical effort shown above covers a single-platform assistant. These factors raise it.
- Supporting Slack and Teams together.
- The knowledge sources behind answers, and keeping them current. See RAG.
- Respecting who is allowed to see which document.
- Approval flows and the systems they write to.
- Admin install rules, workspace or tenant approvals and single sign-on.
- Logging, audit trails and a human handoff for unclear questions.
- Test and production workspaces kept separate.
For a bot's cost shape, see AI chatbot cost.
What are the common chat integration pitfalls?
- A bot that answers from documents a user should not see. Check permissions at question time.
- Not replying within the platform's response window. Acknowledge quickly, then work in the background.
- Granting broad scopes. Ask only for what the bot needs.
- Skipping request verification, which lets anyone call your endpoint.
- Answers that sound sure when the source is silent. Cite sources and say when you do not know.
- Assuming a Slack design will carry over to Teams unchanged.
Should you build it custom or use a connector?
| Question | Connector or iPaaS | Custom integration |
|---|---|---|
| Setup speed | Fast for notices | Slower to start |
| Question answering | Basic | Grounded in your documents, with permissions |
| Both platforms | Often separate flows | One service, two front ends |
| Ongoing cost | Tool fees | Hosting and maintenance |
| Good for | Alerts and simple commands | Internal assistants and approvals |
Power Automate fits Microsoft-centered notices, and Zapier suits simple alerts. See iPaaS.
How do you test and launch a chat integration?
- Choose the first three tasks the bot should do.
- Build in a test workspace or tenant with sample data.
- Test permissions with users who should and should not see a document.
- Test slow replies, repeated events and errors from downstream systems.
- Pilot with one team and review the questions the bot missed.
- Widen access once answers and approvals hold up.
How does StackLift scope a Slack or Teams integration?
StackLift AI integrates with Slack and Microsoft Teams; we are not a partner of either company. The free estimate scopes the work feature by feature, and a senior architect reviews it before it becomes a commitment.
Agents and engineers work on feature branches with CI/CD, observability and rollback from sprint one.
Questions people ask
Can one bot work in both Slack and Teams?
Yes, with a shared back end and a front end for each platform. The platforms differ in identity, install rules and message format, so plan for both.
How does a Slack bot receive messages?
Through the Events API, which pushes events to your server over HTTPS or Socket Mode. Your app needs the right scopes granted at install.
Can an AI assistant in Slack use our documents?
Yes. It searches your approved sources, answers with citations and respects who can see what. See our glossary entry on RAG.
Do we need IT approval to install a bot?
Usually. Workspace or tenant admins often approve apps and scopes, so involve them early.
How long does a Slack or Teams integration take?
See the typical effort above. Supporting both platforms and connecting document sources add time. Run the free estimate for your own scope.