In May 2025, Microsoft introduced a new admin control for Enhanced Personalization, configured via Microsoft Graph: enhancedPersonalizationSetting
If you haven’t changed it, you will see this result with the default configuration. Enhanced Personalization is enabled by default for the organization, affecting all Copilot Basic and Premium users.
Import-Module Microsoft.Graph.Authentication
Connect-MgGraph -Scopes "PeopleSettings.Read.All"
$Url = "https://graph.microsoft.com/beta/copilot/settings/people/enhancedpersonalization"
$Result = Invoke-MgGraphRequest -Method GET -Uri $Url
$Result
What is Enhanced Personalization?
Enhanced Personalization currently has two parts.
Copilot memory lets Copilot learn how users work and what they need and prefer, based on their chats, job profile, custom instructions, and more.
Personalized recommendations build on that: if Copilot memory is enabled, users get suggestions for capabilities that match their role, experience level, and previous interactions, instead of generic or repetitive tips.
Work Insights in Enhanced Personalization
With this update, Microsoft is adding "Work Insights" for all Copilot Premium users (a new third part), unless an admin has changed the enhancedPersonalizationSetting configuration. Work Insights extends the Copilot chat history that was already available.
To personalize Copilot, Microsoft uses a user's private communication data from Microsoft 365, as long as Enhanced Personalization is enabled. This includes Teams chats, Outlook emails, transcripts, Microsoft 365 usage data, profile information such as the user's role, and data from connectors. According to Microsoft, this data is used solely to make Copilot more efficient and more personal for that user. It remains confidential and is not shared with other users. If an admin disables the setting, Microsoft stops using the data for this purpose.
Microsoft recommends a simple check:
To learn what Copilot knows about you, simply ask "What do you know about me." This provides a summary of the important information, including work insights, that Copilot uses to personalize responses. If you see a work insight that you want removed, you can ask Copilot to forget that detail, and Copilot won't use that to personalize future responses.
Users can also disable the personalization settings manually.
To review the current status, users should open the Microsoft Copilot start page, select the gear icon in the bottom left > Settings > Personalization. The same path works for Copilot Basic users. The settings are on by default.

Here is a comparison for Copilot Basic users. They can also use Enhanced Personalization, but not with work-related content.

Disable Enhanced Personalization for specific users
First, as an admin, you can't disable just one part of Enhanced Personalization. You can only turn everything on or everything off, which means no personalization at all.
If you want to disable Enhanced Personalization for specific users, create an Entra ID group and PATCH the enhancedPersonalizationSetting endpoint.
- This update takes a few hours.
- Group membership changes also take time to apply.
- Copilot also needs time to ignore the previously stored memory.
Import-Module Microsoft.Graph.Authentication
Connect-MgGraph -Scopes "PeopleSettings.ReadWrite.All"
$Body = @"
{
"isEnabledInOrganization": true,
"disabledForGroup": "<GroupObjectID>"
}
"@
$Url = "https://graph.microsoft.com/beta/copilot/settings/people/enhancedpersonalization"
Invoke-MgGraphRequest -Method PATCH -Uri $Url -Body $Body -ContentType "application/json"Users get a note personalization is off when the change is active.

If you then ask “What do you know about me from my work content?”, Copilot will reply with work data, but not the saved memory.

Protecting Copilot Memory from deletion
Don’t forget that users can clean up their Copilot memory, which may be a problem in some legal or governance cases. Microsoft Purview now offers a new data retention policy scope for Copilot Memory to preserve the memory information for a specific time period.


No comments yet