Copilot knowledge bases can now be converted to Copilot Spaces

Ahead of the sunset of Copilot knowledge bases on November 1, 2025, we’ve introduced a new way for you to migrate your legacy knowledge bases into a Copilot Space. Simply press the Convert to Space button under each knowledge base you want to convert into its own space.

🔐 Security by design

For security and peace of mind, each knowledge base is converted to an individual space for organization admins to manage and test. When they’re ready, they can promote them for organizational access on their terms.

📂 Examples of how
teams are already using Copilot Spaces

• Generating code that follows security patterns, API standards, and team preferences.
• Sharing knowledge like SQL/KQL queries, telemetry schemas, or best-practice auth docs.
• Onboarding new developers by giving them instant access to curated project knowledge.
• Planning projects and create issues by centralizing PRDs and decisions in one space.

💬 Get started

• Try Copilot Spaces today at github.com/copilot/spaces. Spaces are currently available in github.com for all Copilot users.
• Provide feedback in the Copilot Spaces community discussion or using the inline Give feedback button in the UI.
• Learn more about spaces in our documentation on Copilot Spaces.
• Copilot Spaces follow the same billing model as Copilot Chat.