Microsoft pitched a copilot grounded in your own mail and files

A single assistant claimed across five apps

Microsoft's 16 March 2023 announcement presents one assistant appearing inside Word, Excel, PowerPoint, Outlook and Teams: drafting a first version of a document, turning a data table into a chart, building a slide deck from existing files, summarising an email thread and suggesting a reply, and producing real-time meeting notes with action items. The pitch is continuity rather than five separate tools: the same assistant is meant to follow a person from a planning document into the meeting where it gets discussed.

What grounding in the Graph is supposed to add

The claimed advantage over a general chat assistant is what Microsoft calls grounding: Copilot is described as having live access to a person's own content and context inside the Microsoft Graph, meaning stored emails, calendars, chats and documents, combined with whatever is open at the moment, so a generated draft can reference a real meeting rather than a generic template. Microsoft is explicit that this is meant to make answers “accurate, relevant, contextual,” while also warning in the same announcement that “sometimes Copilot will be right, other times usefully wrong,” and that outputs need review before use. That caveat, printed inside the launch material itself, is worth taking as seriously as the claim it follows.

What an administrator actually configures

Microsoft's current Copilot documentation, a living reference rather than a fixed announcement, sets out that grounding in organisational data is not automatic for every licence tier: some Copilot experiences use only public web data unless a person manually uploads a file or works inside an app with content already open, while full automatic grounding in the Graph is reserved for a higher licence tier, access to which is scoped by the user's own existing permissions. Responses are also shaped by an administrator's data-boundary and access settings. In other words, the grounding described in the launch pitch is a configuration a workspace has to be provisioned for, not a property of the product on its own.

Questions to ask before you adopt it

• Which licence tier does your organisation hold, and does it include automatic grounding in your own files and mail?
• Who has reviewed which files, sites and permissions Copilot's search can reach before it is switched on?
• What is the process for flagging a “usefully wrong” answer before it reaches a customer or a decision?

The announcement sells continuity across apps; the documentation reveals that the continuity depends on licensing and access decisions made well before anyone opens Word. Reading the two together, rather than the pitch alone, is what turns a marketing claim into an implementation checklist.