Microsoft Copilot Memory

https://learn.microsoft.com/en-us/copilot/microsoft-365/copilot-personalization-memory

Microsoft 365 Copilot memory (saved memories, chat-history details, custom instructions) stored in a hidden folder of the user's Exchange mailbox under mailbox compliance; on by default, admin-controllable; available to Copilot Chat users with or without an M365 Copilot licence. Docs still label it preview.

Active · Verified 2026-10-22 · fresh as of 2026-10-22 · 69 cited facts, 1 with a third-party source · Suggest a correction

At a glance

Tier
T1
Latest release
not applicable — not OSS fix
License
not applicable — not OSS fix
GitHub
not applicable — no GitHub repo fix
Pricing
Free + paid vendor fix
Freshness
2026-10-22 fix
Layer
agent-infra repo fix
Licensing
commercial vendor fix
Deployment locus
cloud vendor fix
Platform vs product
product vendor fix

Memory taxonomy

storage
relational
retrieval
injection
persistence
long-term
update
extraction
unit
fact
governance
auditable
conflict
overwrite

When to use

Optimised for: compliance + tenant-scoped governance via Exchange

Anti-fit: not for non-M365 / non-Microsoft tenants

Pros & cons

Pros

Enterprise-ready by default — M365 tenant boundaries, audit trails, compliance certifications; Pages abstraction makes memory inspectable like a document.

Cons

Tied to M365 — non-MS users have no path; feature cadence slowed by enterprise compliance review.

Claims & capabilities

Microsoft 365 Copilot memory stored in user's Exchange mailbox with compliance alignment; GA July 2025 (announced June 2025 Microsoft Build); 75% of Fortune 500 on M365

Technical surface

API surface
not applicable — consumer feature
Backend storage
custom (Microsoft-managed)
Deployment
Managed-only
Embedding model
not applicable — consumer feature
Multi-tenancy
hard-isolation
MCP
via official adapter — Copilot Studio supports MCP
A2A
supported (Copilot Studio A2A integration)
OpenTelemetry
first-class (Copilot Studio + App Insights)

Similar systems

Other platform-provider memory in the catalog, ranked by inbound references.

  • AWS Bedrock AgentCore Memory T2

    AWS managed memory service for agents running on Bedrock AgentCore. Native integrations with LangChain/LangGraph and Strands. Drives long-running MCP servers + agent workloads.

  • Vertex AI Memory Bank (now Agent Platform Memory Bank) T2

    Google Cloud managed memory service, now 'Agent Platform Memory Bank' in Gemini Enterprise Agent Platform. LLM-based memory extraction/consolidation from sessions (background, multimodal, custom topics), per-identity isolation, similarity search, TTL, revisions; used from ADK via VertexAiMemoryBankService.

  • Anthropic Claude Memory T1

    Memory tool API + consumer "Memory" feature + Auto Dream consolidation. Document-as-memory rather than extracted-fact-as-memory.

  • Anthropic Managed Agents — Memory T3

    Public-beta memory stores for Claude Managed Agents: workspace-scoped collections of text documents mounted into the session sandbox as a directory the agent reads and writes with its file tools; every change is versioned for audit and point-in-time restore, and memories can also be managed via API/Console.

  • Cloudflare Agent Memory T2

    Managed persistent memory service for AI agents on Cloudflare's edge. Private beta announced 2026-04-17. Sits alongside Workers AI / Vectorize as the memory tier of the Cloudflare agent stack.

  • Google Gemini Memory T1

    Gemini app learns from past chats via the Personal context setting (on by default, can be disabled; temporary chats excluded). Users can import memories and full chat history from ChatGPT, Claude and other assistants (18+, personal accounts, not EEA/CH/UK).

Sources (68 cited facts, 1 third-party)

Each fact links to the page it came from; the badge says who published it (how to read sources).