Microsoft Copilot Projects organize an individual’s related chats, context files and generated outputs, while Workspaces let invited members share reference content and generated materials. The choice matters to Copilot users deciding whether work should stay personal or be available to a team. M365 Copilot Connection demonstrates both experiences and describes how their sharing and content-creation options differ.
Projects and Workspaces can look similar because each brings related material together around a topic. The practical difference in the demonstrated experiences is ownership and sharing: a Project is for personal work, while a Workspace is set up for collaboration around shared content.
In a Project, the demonstrated interface groups recent chats, project context and document outputs. The user can add files as context for future prompts and return to the project to review its chat history and created files. The presenter describes Projects as a focused chat experience rather than a space with extensive collaboration features.
Workspaces are presented as the next iteration of Copilot Notebooks. In the demonstrated interface, a Workspace has reference content, member controls and creation options that go beyond standard document outputs. These include reports, infographics, study guides, audio overviews and Copilot pages. The presenter also shows a Workspace scope control in the prompt area and options to rearrange reference items.
Choose Projects when you want a personal place to keep a workstream’s chats, files and results together. Choose Workspaces when colleagues need access to shared reference materials or generated content. The key decision is whether other people should be able to access the workspace content, not whether they should see your individual conversations.
According to the demonstration, adding people to a Workspace makes its content available to those members, but chats created within it remain private to their authors unless explicitly shared. The presenter says Workspaces are a Copilot Chat experience available to licensed and non-licensed users. The presenter also cautions that people without a license may not have access to the same rich work data in Work IQ.
The presenter describes the Workspaces update as rolling out, but the material does not specify a complete rollout schedule, regions, qualifying license names or tenant requirements. It also does not establish that the demonstrated interface or every creation option is available to every user. Check what appears in your own Copilot experience before planning a team process around it.
Projects are reached through Cowork in the demonstrated interface. The presenter notes that navigation had changed: Projects appeared in the left navigation earlier, but in this recording they are accessed through Cowork. That interface movement is described as subject to further changes, so the exact location may not remain consistent.
The demonstration also shows an infographic customization step: before generating, the user selects an art style and image dimensions such as square, landscape or portrait. Reports and other outputs can be retained in the Workspace so members can access them there. The presenter describes a report as a snapshot of the source material, not as a scheduled recurring output.
Names and navigation are not fully consistent in the demonstrated experience. The presenter sees Workspaces in the Copilot navigation while OneNote still uses the Copilot Notebooks name. The presenter says the two labels refer to the same underlying notebook/workspace experience, but the interface differences mean users may encounter both terms.
Projects accessed through Cowork required Copilot credits in the recorded demonstration, according to the presenter. The presenter contrasts this with using normal Copilot Chat, which they expected not to incur that consumption cost, but describes that as dependent on anticipated future integration. Treat this as a report of the demonstrated setup, not a general pricing or licensing guarantee.
The presenter could not find a way to schedule reports to run automatically. They also note that availability and licensing can vary. The material does not verify tenant-wide access, specific license entitlements, administrative controls or whether all users can generate every listed content type. Validate the options in your environment before promising a shared workflow.
Projects keep an individual’s related chats, context files and outputs together. Workspaces are designed to share workspace content and generated materials with invited members, while chats remain private unless shared.
The presenter describes Workspaces as available to licensed and non-licensed users, but says users without a license may not have access to the same rich work data in Work IQ. Exact entitlements and availability are not specified.
The demonstration says Workspace content is shared with members, but chats remain private to each user unless explicitly shared.
The presenter had not found a scheduling mechanism for reports. The material does not confirm whether scheduled generation is available elsewhere.