Microsoft 365

Microsoft 365 appears in the Workplace category under Settings →
Integrations → Microsoft 365
. One Microsoft 365 account is connected per
workspace, and that single connection does three jobs:

  • an Outlook calendar can be the source of truth behind a planning calendar
    — trading, promotion or custom;
  • an Excel worksheet in OneDrive or SharePoint can be that source too, mapped
    column by column exactly like a Google Sheets tab;
  • a OneDrive or SharePoint file can be AI context — the assistant reads
    it when a question bears on it.

Everything is read-only. Twelfth never writes to Outlook, OneDrive or
SharePoint.

New to the Microsoft 365 connector? What Twelfth does with Microsoft 365 data gives the overview.

Connect the account, one permission at a time

The page has three tabs: Calendars, Files and Settings (which holds
the permissions, what Twelfth stores, and disconnecting). A tab whose work needs
a permission the connection does not have says so, and offers it there.

Choose Manage (or Connect) on the Microsoft 365 row. Twelfth asks
Microsoft for one permission at a time, each on its own consent screen, so the
account only ever grants what the workspace actually uses:

Permission What it lets Twelfth do
Outlook calendars (Calendars.Read) Read events from the calendars this account can see, for planning calendars
OneDrive & SharePoint files (Files.Read.All) Read the files this account can open — its OneDrive, files shared with it, and the SharePoint libraries it belongs to — for AI context and for Excel worksheets as calendar sources

Both land on the same connection. Grant one now and the other later from the
Grant button beside it; reconnecting keeps what was already granted.

Only workspace owners and admins can connect, grant or disconnect.

Whose account this is, and what that means

The connection is one account for the whole workspace, not one per person.
Everything Twelfth reads — calendars, files, worksheets — it reads as that
account, on the permissions above.

There is no “share this file with Twelfth” step, because Microsoft has no such
thing: whatever the connected account can open, Twelfth can read on its behalf.
That includes that person’s own OneDrive. So:

  • A file in the connected account’s own OneDrive is badged Personal OneDrive
    in the picker, in the check before you link it, and in the list of linked
    files. Files in a SharePoint library, or shared with the account, are not.
  • Linking is limited to workspace admins and remit owners; a linked file is then
    readable by whoever can read the remit it was linked to.
  • To keep personal documents out of reach entirely, connect an account that
    belongs to the SharePoint sites your team uses and nothing else — a service
    or shared mailbox account, rather than a person’s day-to-day one.

Settings → Who this reads as on the integration page states all of this for
the workspace you are in.

If your tenant needs an admin to approve

Some Microsoft 365 tenants do not let people consent to apps themselves. If
Microsoft turns the consent screen away, Twelfth shows an admin consent
link
. Send it to your Microsoft 365 administrator; once they approve Twelfth
for the tenant, connect again and the consent goes through.

Disconnect, in the danger zone on the Settings tab, revokes the stored token for the whole
workspace. Calendars linked to an Outlook calendar or an Excel worksheet stop
loading and files linked as context stop being readable until the account is
reconnected.

Files as AI context

On the Files tab, choose Add a file. Pick from what the
connected account opened recently or was shared, or paste a OneDrive or
SharePoint link. Twelfth checks the file as you choose it — what it is, and
whether it can read the contents — then reads it into a snapshot the assistant
consults through read_document, the same as a document shared from Google
Drive.

What is read: Excel workbooks (every visible worksheet, up to 12 worksheets
× 2,000 rows), Word documents and PowerPoint decks (their text —
paragraphs, table rows, one section per slide; images and speaker notes are
not read), and plain files (CSV, text, JSON). PDFs can be linked but are
held as unsupported until an extractor exists.

A file can be workspace-wide or belong to one remit. Workspace admins link
anywhere; a remit owner links within their own remit. Every linked file also
appears on Artefacts.

Outlook calendars and Excel worksheets as calendars

Under Settings → Calendars, a calendar’s Source picker offers Outlook
Calendar
once the calendar permission is granted, and Excel workbook once
the files permission is. An Outlook calendar reads events in the calendar’s
window; an Excel worksheet is read as a grid and mapped the way a Google Sheets
tab is — choose the workbook (or paste its link), choose the worksheet, and
confirm what each column means. See Calendars.

Start with a new tab asks Twelfth to add the worksheet for you: it writes
the template headers and whatever the calendar already holds, then links it.
That is the one thing Twelfth ever writes to Microsoft 365, so it needs a
permission the read-only connection does not carry — the picker asks for it on
that click, in one Microsoft screen, and never bundles it with connecting. From
the link the worksheet is the source of truth: rows typed or pasted there are
read back, and Twelfth does not edit them.

What Twelfth stores

The encrypted grant, the account’s name, and for each linked file its
OneDrive/SharePoint identifiers, its web address and the text snapshot. Losing
the connection clears every snapshot read through it.