Microsoft’s Roadmap entry 503955, last updated September 1, lists the feature as “Rolling out” and says general availability was due in December 2025. But Microsoft’s Message Center notice, MC1158329, was also updated on September 1 and says general availability begins in mid-September 2026 and should finish by late October 2026. The Message Center announcement is the more useful planning record because it supplies the revised deployment window; administrators should treat September through October as a staged rollout rather than assume every user has had the capability since last year.
The change applies across Copilot Chat on web, desktop, Mac, Android, and iOS. Microsoft says existing Memory controls will be honored: tenants and users who have Memory disabled should not see it silently re-enabled. But organizations that previously enabled the underlying controls need to understand that the capability now includes a separate, more dynamic source of personalization: inferences from chat history.
Chat history becomes a source of Copilot context
Microsoft describes Copilot personalization as drawing on three sources: saved memories, details inferred from chat history, and custom instructions entered by the user. Saved memories are explicit, durable details such as a user’s preferred reporting tool or communication style. Chat-history personalization is broader: Copilot can infer what matters from prior conversations and use those details when answering later, even if the user did not expressly ask it to remember a fact.
That is a meaningful behavioral change for organizations that have treated Copilot Chat sessions as isolated exchanges. A user discussing a recurring project, role, work preference, or subject-matter goal may receive more contextual answers in a future chat. Microsoft’s support documentation says Copilot can use not only chat conversations but also Microsoft 365 work data, usage signals, and profile information when Memory is enabled.
The feature does not give Copilot a new entitlement to files or mailboxes. Access to organizational data remains governed by the user’s existing permissions. But it does create a longer-lived personalization layer from data a user has already supplied in chats. For security, privacy, and records teams, that means the review should focus on how Copilot retains and reuses contextual details, rather than on whether the assistant can suddenly read content that was previously inaccessible.
Microsoft’s Message Center says all Microsoft 365 Copilot users in tenants where Memory is enabled are in scope. The announcement also says there are no changes to existing admin controls or policy enforcement. That should not be read as “no administrative consequences.” Microsoft Learn documents an existing tenant-level Enhanced personalization control, and says it is on by default. When an administrator turns that control off, end users see the controls for custom instructions, saved memories, and chat history switched off and cannot turn them on themselves.
Microsoft’s dates conflict, but the current rollout window is clear
The supplied Roadmap listing has a general-availability date of December 2025, which is already in the past. The separate Message Center notice linked to the same Roadmap ID says Microsoft moved general availability several times: from an earlier January 2026 target, then from a late-July completion expectation, to a rollout beginning in mid-September and completing by late October 2026.
Modern Workspace Pro, which republishes and analyzes the Message Center notice, also identifies the September-to-October period as the revised rollout window. Its reporting does not independently establish the dates—the underlying evidence remains Microsoft’s Message Center—but it confirms that administrators tracking the notice saw the latest update as a timeline change rather than a newly announced feature.
The discrepancy is worth documenting internally. Roadmap dates are planning indicators, and they often remain less detailed than the tenant-facing Message Center record. Here, relying on the Roadmap’s December 2025 “general availability” field could lead an IT department to conclude that the feature should already be universally deployed. It should not. The practical expectation is a phased release during the current September and October window, with variation by tenant, platform, and ring.
Organizations using the Frontier preview may already have seen the feature. Microsoft says public preview began in mid-November 2025. General Availability and Preview are both listed on the Roadmap entry, so help desks should expect users in the same company to encounter different settings or behavior while deployment completes.
Turning Memory off does not erase what was already saved
The redesigned settings are useful, but Microsoft’s own support documents contain a critical distinction that should be reflected in user guidance: disabling Memory is not the same as deleting Memory.
In Copilot Chat, a user can open Chat settings, choose Personalization, and manage Saved memories. Switching the Saved memories control off stops Copilot from applying or creating saved-memory context. It does not automatically delete details already stored. Users must remove individual entries or use the “Delete all memories” option.
Deleting a chat is also insufficient if that conversation produced a saved memory. Microsoft states that deleting a chat does not delete saved memories generated from it. This is the sort of expectation gap that produces privacy tickets: a user may reasonably assume that removing the conversation removes the assistant’s recollection, when the two stores are handled separately.
Chat-history inferences have their own lifecycle. Microsoft Learn says these details are dynamic: Copilot may revise or discard older inferred context as it decides what is useful. If a user deletes every chat in which information was originally shared or referenced, Microsoft says associated chat-history details are removed within seven days. Turning off chat-history personalization triggers deletion of those inferred details after 30 days.
There is another wrinkle: Microsoft’s support documentation says that if a user turns chat-history personalization back on within 30 days after deletion, Copilot adds back the deleted memories from chat history. Administrators should avoid telling users that toggling a setting off and immediately back on is a reliable purge workflow. For a complete removal request, Microsoft directs users to remove saved memories separately and turn off chat-history personalization; the organization may also need to assist.
The compliance boundary is narrower than the settings imply
Microsoft Learn says saved memories, inferred chat-history details, and custom instructions are stored in the user’s Exchange mailbox in a hidden folder. They therefore inherit mailbox protections such as encryption at rest and Customer Lockbox. They are also discoverable through Microsoft Purview eDiscovery and Microsoft Graph Explorer, with Microsoft directing administrators to search the IPM.Contact item class and the CopilotMemory folder for the relevant content.
That storage design gives administrators a response path for discovery and deletion requests. It also comes with limitations that Microsoft’s rollout announcement does not emphasize. Purview retention policies and retention labels do not apply to Copilot Memory, according to Microsoft Learn. A policy that deletes Copilot Chat interactions after three months, for example, does not automatically remove user memories after three months. Microsoft says there are no dedicated admin controls for enforcing retention rules specifically on Copilot Memory.
Microsoft also says Memory and personalization actions do not produce Purview audit-log events. Administrators can discover and delete memory data, but they cannot depend on the normal audit trail to show each instance in which a memory was saved, changed, deleted, or used. Custom instructions are a further exception: they are not currently discoverable through those administrator tools, though users can export them through Personalization settings.
Temporary chats provide a limited way to avoid personalization. Microsoft says they neither access nor update personalized information, do not appear in the user’s chat history, and cannot be revisited by Copilot or the user. They are not, however, automatically outside organizational records controls: Microsoft notes that an organization’s retention policy may preserve temporary-chat data and make it available to administrators during the retention period.
What administrators should do before the rollout completes
There is no emergency configuration change in MC1158329, and Microsoft says current tenant and user settings will be respected. The appropriate response is a short control review and clear user communication, particularly in organizations with strict handling rules for employee, customer, financial, legal, or health-related information.
- Confirm whether Enhanced personalization is enabled at the tenant level and whether that setting matches the organization’s approved Copilot use case.
- Update internal Copilot guidance to distinguish saved memories, chat-history inferences, custom instructions, normal chat deletion, and temporary chats.
- Tell users that disabling Saved memories stops future use but does not delete existing entries; deletion requires the memory-management screen.
- Validate eDiscovery and data-subject-request procedures against Microsoft’s Exchange mailbox storage model, including the documented item class and CopilotMemory folder.
- Review any retention assumptions built around Copilot Chat, because those assumptions do not automatically extend to saved or inferred memory data.
The revised settings may make Copilot Chat feel more useful for recurring work, but they also make users’ prior conversations a more active part of subsequent responses. With rollout expected to continue through late October 2026, the immediate task is to ensure that tenant policy, records procedures, and user expectations all match that reality before the new behavior becomes routine.