docs(teams): consolidated Microsoft Teams integration refresh

[jordanc-relevanceai]

This PR consolidates 4 drafter PRs that all rewrite integrations/popular-integrations/microsoft-teams.mdx. Each section below is the original description from a source PR. Opening as draft for review before closing the source PRs.

Source PRs (kept open until confirmed)

• docs(TSP-1075): expand Microsoft Teams integration with 10 native OAuth tool steps #501 — TSP-1075: 10 native OAuth tool steps with detailed accordions
• Update Microsoft Teams docs with Permissions Reference, Troubleshooting, and expanded FAQs #530 — TSP-1024: Permissions Reference, Troubleshooting, expanded FAQs
• docs(TSP-1098): update Teams integration for marketplace-approved Bot App #538 — TSP-1098: marketplace-approved Bot App rewrite of setup flow
• docs(TSP-1146): add Microsoft Teams attachment support documentation #577 — TSP-1146: attachment support (inline images, file uploads)

Reconciliation note

All four PRs target the same file. Cherry-picked in dependency order — #538 (foundation auth model) → #501 (tool steps) → #530 (FAQs/troubleshooting) → #577 (attachments) — and reconciled the conflicts manually:

• Intro paragraph — combined docs(TSP-1098): update Teams integration for marketplace-approved Bot App #538's two-way-conversation framing with docs(TSP-1075): expand Microsoft Teams integration with 10 native OAuth tool steps #501's OAuth/Graph API technical detail
• Tool steps section — kept docs(TSP-1075): expand Microsoft Teams integration with 10 native OAuth tool steps #501's expanded structure (Team & channel management, Messaging & communication) and dropped duplicate cards from the older list
• Use cases — kept docs(TSP-1075): expand Microsoft Teams integration with 10 native OAuth tool steps #501's 6 expanded use cases (added Shift handoff bot, Compliance monitor)
• Section ordering — Use cases → Admin consent (docs(TSP-1098): update Teams integration for marketplace-approved Bot App #538) → Best practices (docs(TSP-1075): expand Microsoft Teams integration with 10 native OAuth tool steps #501) → Troubleshooting (docs(TSP-1075): expand Microsoft Teams integration with 10 native OAuth tool steps #501) → FAQs
• FAQs — combined unique entries from all four PRs, kept the more thorough wording, deduped overlapping titles

Areas that need a careful read

• The Permissions Reference section from Update Microsoft Teams docs with Permissions Reference, Troubleshooting, and expanded FAQs #530 (added earlier in the file) is referenced from a couple of FAQs — verify the anchor link works
• docs(TSP-1098): update Teams integration for marketplace-approved Bot App #538's marketplace bot framing and docs(TSP-1075): expand Microsoft Teams integration with 10 native OAuth tool steps #501's Graph API framing are now both present — make sure the page doesn't contradict itself on which auth model is "primary"

---

#501 — docs(TSP-1075): expand Microsoft Teams integration with 10 native OAuth tool steps

Summary

• Expanded the Microsoft Teams integration page to document 10 native OAuth-based tool steps that call Microsoft Graph API directly, replacing the previous Pipedream-based approach
• Added 4 new tool steps: List Teams, Retrieve Chat Messages, Search Messages, List Team Members
• Reorganized existing 6 tool steps into logical categories with detailed descriptions

Pages updated

• integrations/popular-integrations/microsoft-teams.mdx

Changes in detail

• Introduction updated to describe the native OAuth / Microsoft Graph API approach and its benefits (faster, more reliable, better security)
• Tool steps section reorganized into 4 categories: Team & Channel Management, Messaging & Communication, Team Operations, Advanced Operations
• Detailed accordions added for every tool step, each with: what it does, 3 use cases, key parameters, and expected output
• Beta warning removed and replaced with a factual note (tool steps now use native OAuth and are not experimental)
• Example use cases expanded from 4 to 6 cards, including new scenarios that use the new tool steps
• Best Practices section added with 5 accordions covering ID resolution, approval mode, context retrieval, search vs. monitoring, and rate limits
• Troubleshooting section added with 5 common issues and their resolutions
• FAQ updated: removed the "why are tool steps in beta?" entry; refreshed permissions wording to mention new operations

Linear issue

https://linear.app/relevance/issue/TSP-1075/

---

#530 — Update Microsoft Teams docs with Permissions Reference, Troubleshooting, and expanded FAQs

Summary

• Added a Permissions Reference section detailing all Microsoft Graph API scopes requested during OAuth
• Added a Troubleshooting section covering common admin issues (unauthorized app, consent denied, missing app, triggers not responding)
• Expanded FAQs with new entries for missing channels, 401 errors, non-responding triggers, and improved existing answers

Test plan

• Preview the Microsoft Teams page at /integrations/popular-integrations/microsoft-teams
• Verify all accordion sections expand/collapse correctly
• Check internal anchor links (e.g. Permissions Reference link in FAQ) work

---

#538 — docs(TSP-1098): update Teams integration for marketplace-approved Bot App

Summary

• Added <Check> callout highlighting that the Relevance AI Bot App is officially approved on the Microsoft marketplace
• Updated the intro to emphasize two-way real-time conversations and that the bot works in channels, group chats, and direct messages
• Strengthened Step 2 with explicit Bot App framing; added a new Direct messages (DMs) tab with step-by-step setup instructions
• Updated the trigger setup section to describe bidirectional conversation flow
• Updated use cases to reflect real-time conversation capabilities
• Added three new FAQ entries: What is the Teams Bot App?, Where can I use the bot?, How do I start a DM with the bot?
• Updated the existing DM FAQ to be more specific about the setup steps

All existing OAuth, trigger, tool steps, admin consent, and agent notification content is preserved unchanged.

Linear: https://linear.app/relevance/issue/TSP-1098/

Test plan

• Verify all headings are in sentence case
• Verify the <Check> callout renders correctly
• Verify the new DM tab in Step 2 renders correctly alongside Channels and Group chats tabs
• Verify new FAQ accordions expand correctly
• Verify no broken internal links

---

#577 — docs(TSP-1146): add Microsoft Teams attachment support documentation

Summary

• Added new Attachment support section to the Microsoft Teams integration page documenting the capability added in RelevanceAI/relevance-api-node#13425
• Documents inline image support (images pasted directly into Teams chat)
• Documents file upload support (PDFs, documents, images via the Teams file picker)
• Explains the [N attachments] indicator shown when a message contains only attachments and no text
• Updated the "Can my agent access files shared in Teams?" FAQ to reflect that attachments are now received directly via triggers, not only through SharePoint

Test plan

• Verify the new Attachment support section renders correctly in the Mintlify preview
• Check that the CardGroup icons (image, file) resolve correctly
• Confirm the [N attachments] inline code renders as expected
• Verify the updated FAQ entry is accurate and clear

Linear: https://linear.app/relevance/issue/TSP-1146/

---

Linear

• TSP-1024
• TSP-1075
• TSP-1098
• TSP-1146

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
relevanceai	🟢 Ready	View Preview	May 5, 2026, 4:56 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.