Copilot Memory Admin Controls: Find and Test the Right Setting

Copilot memory admin controls depend on which Copilot you use: work or school Copilot has Microsoft organizational controls, GitHub Copilot has its own organization and enterprise settings, and personal Microsoft Copilot uses individual settings. Identify the signed-in account before changing anything, then test the effect from an ordinary user account.

fenbs can keep the team’s approved decision and review results available to connected assistants. It does not change Microsoft or GitHub settings. Use the native administrator controls first, and preserve an accurate record of what you checked.

Which Copilot and account are you administering?

1. Open the account profile in the affected app and identify whether it is a personal Microsoft account, a work or school account, or a GitHub account.
2. Confirm the organization or enterprise that manages the account or subscription. Record the relevant product and administrative scope without copying personal account details.
3. Choose the matching control below, make a limited test change under your normal approval process, and verify the result as an affected user.

Microsoft’s organizational documentation↗ (opens in a new tab) now uses Microsoft Copilot and Microsoft Copilot Chat for products some screens still call Microsoft 365 Copilot and Microsoft 365 Copilot Chat. This guide calls that branch work or school Copilot to keep the account boundary clear.

For the underlying behavior rather than administration, see Microsoft Copilot memory or GitHub Copilot memory. A comparison such as Copilot versus ChatGPT answers a different product-selection question.

How do you control memory for work or school accounts?

Microsoft identifies Enhanced personalization as the administrative control behind organizational memory. Its control overview↗ (opens in a new tab) describes disabling the related features for the organization or a group of users. Have the authorized tenant administrator handle the configuration rather than asking employees to change personal preferences.

1. Read the current Enhanced personalization documentation and establish the intended organization or group scope before making a change.
2. Check the supported configuration route. The Microsoft Graph setting reference↗ (opens in a new tab) describes organization enablement and a group exclusion; the linked beta reference warns that production use of beta APIs is unsupported. Have the administrator verify the applicable supported route.
3. Apply the approved change and sign in as an affected user. Inspect Settings > Personalization and check that the expected memory-related controls are disabled.
4. Test an unaffected account if the change is scoped to a group. Record the actual results and any remaining configuration question before expanding the change.

Microsoft’s memory administration guidance↗ (opens in a new tab) says users cannot re-enable the affected personalization controls when the administrative control is off. It also describes the feature as preview, so check the live instructions and the actual account rather than relying on a remembered screen path.

What changes when you disable organizational memory?

Disabling use is different from deleting stored information. Microsoft says disabling saved memories or custom instructions stops their application but does not remove them. Deleting a conversation also does not delete saved memories produced from it. Follow the separate deletion guidance when removal is required.

The same Microsoft administration guide says Purview retention policies for chat interactions do not apply to Copilot memory, and it provides no memory-specific administrative retention control. It also says memory and personalization actions do not create Purview audit entries. Do not describe a chat-retention rule or audit report as proof that memory was removed.

Write the test result narrowly: the affected account could not enable the controls, for example. A successful toggle test does not establish source access, deletion, or absence from every future response. Use harmless sample information and avoid treating the assistant’s answer alone as confirmation of the underlying setting.

How do GitHub administrators manage Copilot Memory?

GitHub’s administrator instructions↗ (opens in a new tab) describe separate controls for managed Copilot subscriptions. The memory feature is preview and is off by default for enterprise- and organization-managed subscriptions. An enterprise policy can limit what organization owners may change.

1. For an enterprise, open AI controls > Copilot > Configure features & clients and locate Copilot Memory. Select the approved policy.
2. For an organization, open Settings > Copilot > Policies and locate Copilot Memory. Check the enterprise policy before changing the organization setting.
3. For stored repository facts, open the repository’s Settings > Copilot > Memory. Review the facts and delete inappropriate or incorrect entries.
4. For organization-billed user preferences, use the organization’s Settings > Copilot > Access export or deletion options. Verify the billing scope before assuming the record includes every preference.

GitHub documents audit events for administrator exports or deletions and user opt-outs. Check the actual event for the operation you performed. If several organizations assign a user’s subscription, GitHub applies the most restrictive memory setting, so investigate that boundary before treating an unexpected result as a local failure.

The GitHub Copilot app guide covers a particular working surface. Administration should start with the managed account and subscription, then verify the supported surface your developers actually use.

What can you do about personal Microsoft accounts?

Microsoft’s individual privacy controls↗ (opens in a new tab) apply to personal Microsoft accounts, not organizational accounts. For the supported app version, the user opens Settings > Personalization, turns off Saved memories, and uses Manage to delete existing memories. Turning the setting off does not automatically delete what was saved.

Do not report an organization-wide control as complete because one employee changed that personal setting. Identify the approved work account and route business work there under the organization’s existing process. Avoid collecting personal memories or screenshots containing unrelated private information as review evidence.

If your task is deciding what employees may save, who owns it, and when to review it, use the separate Copilot memory policy guide. The administrative check here verifies whether the chosen control exists and has the intended effect.

How to do this with fenbs

1. Create a free account, free for one person with no credit card. Add a project for the Copilot administration review and use a team kanban board when colleagues need access.
2. Add a task for each relevant product and account type. Put the intended scope, official documentation link, expected result, and unresolved checks in the plan.
3. Record the person’s approved choice in Decisions and rules. Distinguish the setting’s verified effect from any deletion or retention work still waiting on an administrator.
4. Connect a supported assistant through Integrations. Ask it to read the rules before helping with the review and save progress with the next check before it stops.

fenbs is not the right fit as a Copilot administration console. It does not connect to work or school Microsoft Copilot or modify native memories. GitHub Copilot is a supported assistant connection through MCP, a standard way for an AI app to use an outside tool, subject to your organization’s permission.

Review the result when the product, managed scope, or official control changes. The AI governance library covers the surrounding responsibilities, while instruction examples help with readable working guidance after the administrative boundary is settled.