Organization-Level Memory Layer for Microsoft Copilot

As a Solutions Architect working with Microsoft 365 Copilot and Purview, I see a growing need for a centralized memory layer at the organization level.

Today, Copilot Memory is user-specific, which is great for personalization. But many use cases would benefit from a shared memory layer that:

• Stores reusable organizational context (e.g. naming conventions, governance rules, preferred terminology)
• Applies default memory settings across users (e.g. how to respond to meeting requests, how to reference internal policies)
• Reduces the need for repetitive memory entries across departments
• Enables faster onboarding and consistent Copilot behavior across teams

This could work as a hierarchical memory model:

1. Org-level memory (defined by IT or business owners)
2. Team-level memory (optional)
3. User-level memory (personalized)

Would love to hear if this is on the roadmap – or if others see the same need.

Thanks!
Niklas Précenth
Solutions Architect, Atea