MENU
You need to enable Copilot memory to support the planned changes.
What should you configure?
Copilot memory is an organization-level capability. Configuring it through the organization's Copilot settings establishes the governance boundary, availability, and policy controls consistently for the developers and repositories covered by that organization.
Personal settings are unsuitable because they create inconsistent behavior between developers and do not provide centralized administration. A repository-level configuration can supply repository instructions and scoped context, but it does not replace the organization-level control that enables and governs the memory capability. An individual agent profile defines role behavior, tool access, prompts, and delegation settings; it is not the tenant-level location for enabling Copilot memory.
Organization configuration is particularly important when agents must retain approved context, recurring pReference, and workflow guidance across sessions without each developer configuring behavior independently. Central governance also allows administrators to maintain predictable controls over which organizational information is available to Copilot.
Study-guide topics: organizational governance, persistent context, and centralized agent configuration.