Skip to content

docs: add Outlook and Microsoft Teams connector guide - #74

Open
fluso-agent[bot] wants to merge 2 commits into
mainfrom
fluso-agent/docs/outlook-teams-connectors
Open

fluso-agent[bot] wants to merge 2 commits into
mainfrom
fluso-agent/docs/outlook-teams-connectors

Conversation

@fluso-agent

@fluso-agent fluso-agent Bot commented Nov 17, 2026

Copy link
Copy Markdown
Contributor

What

Adds the Outlook and Microsoft Teams connectors to the docs. They are native
connectors and the Apps and MCP page did not mention Microsoft at all.

  • New page /integrations/microsoft ("Outlook and Microsoft Teams"): what you
    can ask Fluso to do, how to connect, the Microsoft permissions requested and
    why, approval behaviour, limits, data and tokens, notes for IT admins,
    reconnect and disconnect, differences from the earlier third-party
    connections, and troubleshooting.
  • features/mcp.mdx: Microsoft 365 row in the native connectors table,
    "Microsoft services connect separately" subsection, Outlook added to the
    Agents-keep-access note, a troubleshooting entry, and a link in Next.
  • integrations/meta.json registers the page. AGENTS.md lists it.

Source of truth

Checked against premapp-backend dev and master (identical for these files):
microsoft_365.py (services, scopes, tenant), microsoft_catalog.py (published
tools), classification.py (read/write classes, default policy),
routes/microsoft.py (connect flow), legacy_microsoft.py (retirement of the
earlier connections). PRs #1099, #1104, #1105, #1123, #1189.

Left out on purpose

SharePoint and Excel (availability not confirmed), Power BI, Teams channel
history, meetings and transcripts (not built), attachment reading (needs a live
test).

Please confirm before merge

  • Personal Microsoft accounts: the page says they do not work (code default is
    work and school only; the prod tenant setting is not visible in code).
  • The app name and publisher status shown on Microsoft's consent screen.
  • Teams has had a production check (only Outlook was recorded).
  • Whether to keep the one-line Outlook Calendar and OneDrive mentions on the page (strictly Outlook and Teams is possible).
  • Whether to keep the paragraph saying the toolset is smaller than the earlier connections (a positioning call).

Checks

npm run build passes (66 pages). Internal links and anchors on the two
changed pages resolve in the built output. The repo has no link-check script.

Replace two sample names that the cspell check does not know with names already used elsewhere in the docs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants