> ## Documentation Index
> Fetch the complete documentation index at: https://docs.synheart.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Microsoft 365

> What the Outlook Calendar, Outlook Mail, Teams and OneDrive connectors read, what they never keep, and how an admin connects them

Synapse connects to Microsoft 365 as four separate tools: **Outlook Calendar**, **Outlook Mail**, **Teams** and **OneDrive**. Each is granted, enabled and disconnected on its own, so an organization can connect one without the others.

## What each tool reads

The organization tools read **metadata about work, never its content**: when something happened and which verified member did it.

| Tool | Synapse keeps | Synapse never keeps |
| - | - | - |
| Outlook Calendar | When each meeting on a member's default calendar starts and ends | Subjects, descriptions, attendees, locations, recordings or transcripts |
| Outlook Mail | That a member sent a message, and when (Sent Items only) | Subjects, addresses, message bodies or previews, attachments |
| Teams | That a member posted or replied in a channel, and when | Message text, attachments, reactions, private chats, calls, meeting recordings or transcripts |
| OneDrive | An inventory of files: names, links, sizes and dates | File contents. Organization collection never downloads or indexes a file |

A few rules hold across all four:

* **Only verified members count.** Activity is attributed only to people Synapse can match to a current member of your organization. Anyone it can't match is counted as unmatched and skipped, never guessed from an email address and never attributed to the admin who connected the tool.
* **Teams content is discarded.** Microsoft's channel-message permission returns message text to Synapse; the collector throws it away and keeps only the metadata above.
* **None of it is used for recall.** Calendar, mail and Teams metadata never become organization knowledge an agent can quote.
* **No Microsoft 365 Copilot data.** These tools don't request access to Microsoft 365 Copilot prompts, conversations or usage. GitHub Copilot is a separate connector.

## OneDrive as a knowledge source

The organization OneDrive tool keeps an inventory only. Making OneDrive files available to agents is a separate step: a member chooses a folder as a [knowledge source](/synapse/admin-setup#connect-github), and Synapse indexes that folder's files, answering each person only with files they can open themselves in OneDrive.

## Connecting your organization

You need a Synapse admin, and a Microsoft account with the **Global Administrator** or **Privileged Role Administrator** role in your tenant.

<Steps>
  <Step title="Open Microsoft 365 under Connectors">
    In synapse.synheart.ai, open **Setup → Connectors** and find **Microsoft 365 · Organization**.
  </Step>

  <Step title="Sign in as a tenant administrator">
    Synapse verifies your Microsoft sign-in, your tenant and your administrator role before asking for consent.
  </Step>

  <Step title="Grant consent tool by tool">
    Each tool asks Microsoft for its own admin consent. Grant only the tools you want.
  </Step>
</Steps>

Synapse requests these Microsoft Graph application permissions:

| Tool | Permissions |
| - | - |
| Outlook Calendar | `Calendars.ReadBasic.All`, `User.Read.All` |
| Outlook Mail | `Mail.ReadBasic.All`, `User.Read.All` |
| Teams | `Team.ReadBasic.All`, `Channel.ReadBasic.All`, `ChannelMessage.Read.All` |
| OneDrive | `Files.Read.All`, `User.Read.All` |

`User.Read.All` lets Synapse match Microsoft accounts to your organization's members. Two of these permissions allow more than Synapse uses: `ChannelMessage.Read.All` returns message text, which is discarded, and `Files.Read.All` would allow reading files, which organization collection never does.

## Personal connections

Members can also connect their own Outlook calendar, mail, Teams or OneDrive from **Your connections**. Those are separate from the organization tools, use the member's own permission, and cover only that member.

## Disconnecting

* **Disconnect** on a tool stops that tool; **Disconnect organization suite** stops all four and clears the tenant binding. Members' personal connections stay as they are.
* Collected metadata is kept by default. Ticking **Also delete imported Microsoft metadata** deletes it, including the same kind of metadata collected through members' personal connections. This can't be undone. OneDrive files that members chose as knowledge stay.
* Disconnecting removes Synapse's access but not the consent you granted in Microsoft Entra. Remove the Synapse applications there too if you no longer want them to have access.
* To bind your organization to a different Microsoft tenant, disconnect the whole suite first.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.