Your agents don’t need to persist. Your purpose does.

How do I connect Microsoft 365 to ChatGPT?

The Microsoft estate over MCP, in ChatGPT's connector settings — with the ecosystem's own documented note that Outlook Calendar arrives read-only there.

Direct answer: connect the Microsoft 365 MCP surface to ChatGPT. In ChatGPT, add it from the connector settings (developer mode); the tool's own docs carry the current path. The documented coverage: SharePoint and OneDrive files, Outlook — with Outlook Calendar read-only in OpenAI's ecosystem — and Teams chat search with sync indexing. Grant the slice you need; the read-shaped slice answers most questions.

The estate from the other assistant

Same estate, same protocol, different client: the SharePoint proposal, the Teams thread, the Outlook schedule, readable from ChatGPT under your authorisation. Estate data stops caring which assistant asks.

Decks go stale in the dark

Worked case: you set a current-deck rule — external meetings use this quarter's master deck only, after a prospect meeting once ran on a deck with last year's pricing and a product screenshot two redesigns old. OneDrive versions everything; that only one version is presentable is your rule about the versions.

Through Unl the file read arrives versioned by law: the deck attached to Thursday's meeting is last quarter's master — against your rule, the two-redesigns story attached. The stale deck gets caught at prep time, not in the room.

Microsoft 365 to ChatGPT reads the estate under your grant; through Unl the estate answers to the currency rules you set — last quarter's deck never makes it to Thursday.

Reads through Unl arrive with measured context — in the presence of the decisions you’ve already settled. It works today: one box, paste anything. If it speaks MCP, Unl can reach it. Readings arrive unprompted, the data beside the criterion; Unl is a courier, not a warehouse, and keeps only your keys and the frame.

Read further

Questions people ask

What is documented as readable in OpenAI's ecosystem?

SharePoint and OneDrive, Outlook with calendar read-only, and Teams chat search plus sync indexing — per current ecosystem documentation; verify the listing at setup.

Why does calendar arrive read-only there?

That is the ecosystem's own documented boundary. For the questions this page covers — reading state, checking against rules — read-only loses you nothing.

Do rules span Google and Microsoft estates?

Yes — rules live in Unl, above any estate. A current-template rule governs SharePoint and Drive reads alike; the estate is a detail.

What if last quarter's deck is still the right one?

Then say so, and the currency rule stops objecting to it. A freshness standard is about whether anyone has checked, not about whether the file is old. Confirming that a document still stands is the cheapest work on this list and the piece most often skipped.

What this is

Your agents don’t need to persist. Your purpose does.

Save the thoughts, decisions and targets worth keeping, each with its reasoning, carried into every AI session the moment they matter. Unprompted.

Your whole AI world. What you decided at the epicentre. It works inside Claude, Claude Code, ChatGPT and Cursor, and connects in a couple of steps.

MCP native·You decide·Model agnostic·Your data

The right information

Connect Unl to bring the right information into the moment.

Your sources, read against the criteria you set.

Add Unl to your AI

The full product, open. Free to start. Paid plans from $10 a month.