Microsoft Copilot Projects Group Work by Initiative

Key insights

• Ami Diamond describes Projects as a way to organize Copilot work around a specific initiative.
• The listed project elements include conversations, tasks, files and outputs, instructions, and context.
• Diamond says each Project can have its own instructions to keep future interactions aligned to the initiative.
• The description gives example uses including a SharePoint migration, training series and customer engagement.
• The material does not specify licensing, rollout status, availability, or detailed creation steps.

Ami Diamond [MVP] recently published a 9-minute, 41-second video titled “Microsoft Cowork - Create a Project.” Its accompanying description introduces Projects in Copilot as a way to group work around an initiative, rather than leaving related activity scattered across individual conversations. The central takeaway is that a Project can bring conversations, tasks, files and outputs, instructions, and context together.

What's new

Diamond describes a new capability called Projects in Copilot. In the description, a Project is an organizing space for work tied to a particular initiative, such as a SharePoint migration, a Copilot adoption program, a training series, customer engagement, or content creation.

The description lists five kinds of material associated with a Project: conversations, tasks, files and outputs, project instructions, and context. It also highlights that each Project can have its own instructions. Diamond says this lets Copilot understand the initiative’s context and stay aligned across future interactions.

That is the feature-level explanation available in the published material. It presents Projects as an organizational approach to AI work, but does not detail interface controls, creation fields, or how the listed elements are added or managed.

Why it matters

For people who use Copilot across ongoing work, organizing by initiative could make related interactions easier to keep together. A migration, adoption program, or customer engagement often involves more than one prompt or conversation; the Project concept described here provides a shared place for that work and its associated context.

The project-specific instructions are the most concrete stated benefit beyond grouping items. Rather than restating an initiative’s context in every interaction, users could set instructions for that Project and carry them into future interactions. The video description does not explain exactly how instructions affect responses, so the practical degree of continuity remains unclear.

For administrators, the topic may be relevant as a change in how users organize AI-assisted work, but the supplied material gives no information about controls, governance, licensing, or tenant rollout. Makers and end users can assess the basic idea and examples, but should not treat the description as a full product specification.

How it works

Diamond’s description gives a high-level model rather than a step-by-step walkthrough. A user creates a Project for a specific initiative, keeps related work in that Project, and gives it its own instructions so future Copilot interactions can use the project context.

1. Choose an initiative, such as a training series or SharePoint migration.
2. Organize its conversations, tasks, files and outputs, and context in a Project.
3. Add project-specific instructions, which Diamond says can help Copilot stay aligned in future interactions.

These are the elements described in the source, not verified interface steps. The provided material does not show where to find the creation command, what information is required, or whether the items are linked automatically or added manually.

Limitations and open questions

The video description is brief and does not establish how Projects are created or what happens behind the scenes. It does not specify whether tasks are connected to a separate task-management service, where files are stored, or how project context is selected. It also does not explain whether Projects can be shared with colleagues or how permissions work.

Availability and licensing are not stated, nor does the description identify a rollout stage or supported regions. Readers should check their own Copilot environment rather than assume the capability is enabled for their account. The published material supports the basic organizational concept, but not a conclusion about deployment or administration.

Sources

• Ami Diamond’s video, “Microsoft Cowork - Create a Project”
• Ami Diamond’s LinkedIn profile

Frequently asked questions

What can a Copilot Project contain?

Diamond’s description lists conversations, tasks, files and outputs, project instructions, and context.

Can a Project have its own instructions?

Yes. The description says each Project can have its own instructions to help Copilot understand the initiative and stay aligned across future interactions.

Is Projects available to every Copilot user?

The material does not state availability, licensing, or rollout status, so this cannot be confirmed from the video description.

Does the video explain the exact creation steps?

The provided material describes the concept and example uses, but does not give verifiable interface steps or setup details.