Get API key

Microsoft 365

View as Markdown

Give your members their Microsoft 365 mail, files and calendar in chat. Set up once for the organisation.

The Microsoft 365 connector lets each member bring their own Outlook mail, OneDrive and SharePoint files, calendar and Teams chats into a conversation. Each member signs in with their own Microsoft account and sees only what they could already see in Microsoft 365. There is no shared mailbox and no service account.

Setup takes two people: an org admin, who sets it up in PrivateMind, and a Microsoft Entra administrator, who approves it in your Microsoft tenant (your organisation's Microsoft 365 directory). They are often different people, so the setup card lets you do your part and then send the approval links on.

Before you start

You need:

  1. Org admin access in PrivateMind. Setup is on the Org Connectors page, which regular members can't see.
  2. Your Microsoft tenant ID. A Microsoft Entra administrator can read it from the Entra admin centre under Overview, where it is shown as the Tenant ID or Directory ID. It is a GUID, in the shape 00000000-0000-0000-0000-000000000000.
  3. A Microsoft Entra administrator who can approve applications for your tenant, usually a Global Administrator or Privileged Role Administrator.
  4. Connectors switched on for your organisation. In Organisation Settings, both MCP Servers and Custom MCP Servers need to be on. Custom MCP Servers is off by default, and while it is off, Org Connectors doesn't appear in the sidebar.

Open Org Connectors in the settings sidebar (/settings/org/org-connectors). The Microsoft 365 card at the top has three steps.

Step 1: your tenant ID

Paste the tenant ID into the box and save. Members can then connect only with accounts from that tenant. An account from any other tenant is turned away, even if it is valid.

Enter the GUID, not a domain such as contoso.onmicrosoft.com. PrivateMind won't save a domain, because Microsoft doesn't send it at sign-in and it would match no one.

After you save, the box empties and the tenant ID in use appears under it. Use the box only to enter a new one.

Step 2: approval from your Entra administrator

Two buttons appear after you save the tenant ID:

  • Approve data access
  • Approve sign-in

Both are needed. They approve two different applications. If only one is approved, the connector seems to work for administrators and fails for everyone else, which is hard to diagnose. Administrators can approve applications for themselves as they sign in, so they get past a gap that stops an ordinary member.

If you are the Entra administrator, open both links and approve. If you are not, send both to whoever is, along with the section below.

For the Entra administrator

You are being asked to approve a PrivateMind connector that lets your colleagues use their own Microsoft 365 data inside PrivateMind conversations.

There are two applications to approve, and both are needed. One is the PrivateMind web application your colleagues sign into. The other is the service that talks to Microsoft Graph on their behalf. Each of the two links you have been sent opens the right application, with your tenant already filled in.

Every permission is delegated, which means the connector acts as the signed-in person and can never see more than they can. There is no application permission, so it cannot read anything tenant-wide, and there is no service account.

What it asks for:

Permission What it allows
User.Read Read the signed-in person's basic profile
Mail.Read Read their mail
Mail.Read.Shared Read shared mailboxes they already have access to
Calendars.Read Read their calendar
Files.Read.All Read files they already have access to
Sites.Read.All Read SharePoint sites they already have access to
Chat.Read Read their Teams chats
ChatMessage.Read Read their Teams chats
Team.ReadBasic.All Read the names of teams they belong to
Channel.ReadBasic.All Read the names of channels in those teams
ChannelMessage.Read.All Read the messages in those channels
Files.ReadWrite.AppFolder Write into a single folder in their own OneDrive

The last one is the only write permission. Files.ReadWrite.AppFolder limits every write to one folder in the person's own OneDrive. Microsoft enforces that limit, so nothing can be written outside it, whatever the application does. There is no permission to send mail or to change a calendar.

After you approve, both applications appear under Enterprise applications in your tenant, named PrivateMind-M365 and PrivateMind-M365-Web. Their Permissions view lists what was granted. Check it against the table above.

Removing a read permission there breaks more than one feature. Microsoft fails the whole token exchange if any requested permission is missing. Removing Sites.Read.All also stops OneDrive working, and removing any single read permission stops search working entirely. Files.ReadWrite.AppFolder is the only one you can remove cleanly, and removing it makes the connector read-only.

To limit who in your tenant can use it, set Assignment required to Yes on the enterprise application and assign a group. This restricts use and leaves the consent in place, and it is the setup we recommend.

To remove access later, delete the enterprise application in your tenant. That cuts it off immediately and needs nothing from PrivateMind.

Step 3: turn it on

The switch in the top right of the Microsoft 365 card stays disabled until a tenant ID is saved. When you turn it on, Microsoft 365 appears in the connector Library for everyone in your organisation.

You can turn it on before your Entra administrator has approved both links, and PrivateMind can't check whether they have. Until both are approved, members see the connector in the Library but can't use it. Microsoft turns them away at sign-in with an approval error (see When something goes wrong) or, if only sign-in was approved, their first request fails. Turn it on once your Entra administrator confirms both approvals are done.

Turning it off removes it for everyone, including members who have already connected. It disappears from the Library and from every conversation it was attached to. Members who had connected keep their stored Microsoft sign-in, so they don't have to sign in again if you turn it back on.

What your members do

Members don't use the setup card. Once the connector is on and approved, each member opens Connectors from the sidebar, finds Microsoft 365 in the Library and clicks Connect. They sign in with their own Microsoft account once, and can then attach it to any conversation.

From then on they can ask things like "summarise my unread mail from this week", "find the deck I shared with the client last month", or "what does my Thursday look like".

The assistant can also save a file to their OneDrive. Everything it writes goes to one folder, Apps/PrivateMind-M365, and Microsoft stops it writing anywhere else. Because the connector can create and change files in that folder, PrivateMind asks for confirmation the first time someone connects it.

Attaching it changes the conversation

Microsoft 365 carries a person's mail, files and calendar, so PrivateMind treats a conversation holding it as a private one. Attaching it turns web search off for that conversation and disconnects any connector that reaches the public internet.

This lasts for the life of the conversation. Detaching Microsoft 365 later doesn't bring web search back: what it read is already in the history, and an outside channel could carry it out. To use web search again, start a new chat.

Connectors that stay inside your organisation are unaffected, so Microsoft 365 and an internal connector such as an issue tracker can be used in the same conversation.

If your organisation has turned on a third-party model provider, Microsoft 365 won't attach to a conversation that uses that provider's models. Its contents would be sent to the provider.

When something goes wrong

These errors come from Microsoft. They read as if the member did something wrong, though usually the setup is incomplete.

What the member sees What it means Who fixes it
Approval required, or AADSTS65001 The applications have not been approved for your tenant yet Entra administrator, step 2
A message that their account belongs to a different tenant They signed in with an account outside your organisation The member, by using their work account
A message that the organisation is not bound to a Microsoft tenant The tenant ID has not been saved Org admin, step 1
AADSTS50011 A redirect address is missing from the application registration PrivateMind support
Everything works for you but not for anyone else Only one of the two approvals was granted Entra administrator, step 2

The last row is the most common, so check it first. Approving as an administrator doesn't prove that ordinary members can sign in. Test with an account that has no admin role before you tell everyone it's ready.

Where next

  • Connectors: how members browse, connect and use connectors in chat
  • Org connectors: register your organisation's own MCP servers and REST APIs
  • Org settings: the switches that control which connectors your organisation can use