Claude Projects in Microsoft Copilot: What Replaces Them
What a Claude Project becomes in Microsoft Copilot, how to capture its instructions and files, and how to keep using Claude's models inside Copilot.
Claude Projects are where many teams keep their best AI work: a set of instructions, a pile of reference files, and the conversations built on top of them. When a company standardizes on Microsoft Copilot, the question is what happens to those Projects. The short answer: each one becomes a Copilot agent, its files move into SharePoint, and in most tenants your people can keep using Claude's models inside Copilot.
What a Project becomes
| Claude Project | In Microsoft Copilot |
|---|---|
| Project instructions | Agent instructions (up to 8,000 characters in Agent Builder) |
| Project knowledge files | A SharePoint or OneDrive library the agent uses as knowledge |
| Project conversations | Archived from the organization export, searchable in SharePoint |
| Connectors | Copilot Studio connectors or MCP servers |
| Who the Project is shared with | Who the agent is shared with |
For a research-style Project, where people collect sources and notes and ask questions across them, Copilot Notebooks can be the closer fit. Notebooks are available to Microsoft Copilot and Copilot Chat users; creating one needs a SharePoint or OneDrive license.
Step 1: List the Projects
There's no admin list of private Projects in Claude, so the inventory starts with people. Ask each team for the Projects they use, who owns each one, and how often it's used. Claude organization owners can see which connectors are enabled under Organization settings, Connectors. That tells you which Projects reach into other systems.
Step 2: Capture each Project
- Instructions. Copy them from the Project settings.
- Knowledge files. Collect the originals from the Project owner. Anthropic doesn't document whether the organization export includes the files inside Projects, so don't count on it.
- Conversations. On Claude Team and Enterprise, the Primary Owner can export the organization's data from Organization settings, Data and privacy. The export includes conversations and user data, and its download link expires after 24 hours, so plan who downloads it and where it goes.
Step 3: Rebuild it as an agent
- In Microsoft Copilot, open Agent Builder and create an agent with the Project's name and a one-line description of when to use it.
- Paste the instructions, and remove anything specific to Claude's interface.
- Put the knowledge files in a SharePoint library with the right permissions, and point the agent to it.
- Test it with real questions from the people who used the Project, and compare the answers.
- Share it with the same people the Project was shared with.
If the Project relied on a connector, or should be available to the whole organization, build it in Copilot Studio instead. Copilot Studio supports connectors and MCP servers, and organization-wide publishing goes through it with admin approval.
Step 4: Bring over what Claude learned about each person
Copilot can't import memory from another AI tool. A person can ask Claude to write out what it remembers about them, word for word, and reuse the useful parts as Copilot custom instructions. Doing it in a short guided session makes Copilot feel familiar on day one.
You don't have to give up Claude's models
Anthropic's Claude models are available inside Microsoft Copilot: in Copilot, Researcher, Copilot Studio, Agent Mode in Excel and the Word, Excel and PowerPoint agents. Microsoft turns them on by default for most commercial tenants. In the EU, EFTA and the UK they are off by default and an admin opts in, and they aren't available in government clouds. The setting is "AI providers operating as Microsoft subprocessors" in the Microsoft 365 admin center, under Copilot settings.
For teams that chose Claude for its writing or reasoning, that changes the conversation. The move is about where the work lives (Microsoft 365, with its permissions, retention and admin controls), not about giving up the model people like.
Planning the move
A handful of Projects is manageable in-house. Dozens across departments, with connectors and an organization export to archive, is a project of its own. Our Claude to Copilot page covers what moves where, and the AI Migration Assessment starts with the inventory: every Project, its owner, its files and its connectors, mapped to its new home in Microsoft 365.