Copilot Notebooks for beginners: collect project sources in one AI workspace

When a project starts living across five Copilot chats, three documents, and two meeting notes, AI help gets messy fast. Copilot can still answer, but you spend time explaining the context again and again. Copilot Notebooks is Microsoft 365 Copilot's way to give one small project its own workspace with selected sources.

This guide continues from Microsoft Copilot for beginners and Copilot Pages for beginners. This is not about your first prompt or turning one answer into a shared page. Here you gather the right project material first, then ask Copilot for a short brief or action list that a human reviews.

Source: Microsoft Support: Get started with Microsoft 365 Copilot Notebooks

Who this guide is for

This is for you if you already use Microsoft 365 or Copilot Chat and have a small project with a few documents, pages, or meeting notes. Maybe you are a consultant summarizing client material. Or you might be in a school or operations team that wants approved planning documents in one place before the next meeting.

The goal is simple: one notebook for one project, a few relevant sources, one clear question, and a reviewed output. Not a full Microsoft 365 tour.

What you will learn in 10-20 minutes

After this guide, you can:

• create one Copilot Notebook for a small project,
• add a few trusted references,
• ask Copilot to answer from those references,
• turn the answer into a project brief or action list,
• check facts and permissions before sharing.

Where to find Copilot Notebooks

Go directly to https://m365.cloud.microsoft/notebooks, or sign in at https://microsoft365.com/, select Notebooks, then All notebooks, and choose New notebook.

If you cannot see Notebooks, access may depend on your account, license, SharePoint or OneDrive service plan, admin settings, and gradual rollout. Microsoft describes Notebooks for Microsoft 365 Copilot, Copilot Chat, and some Microsoft 365 Personal/Family/Premium contexts, but not every feature appears everywhere at the same time.

Source: Microsoft Support: Get started with Microsoft 365 Copilot Notebooks

Before you start: choose a small source set

Start narrower than feels natural. Pick one project or recurring workstream, such as Q3 offer, new colleague onboarding, or course planning.

Then choose 3-8 sources you are allowed to use. That might be a PDF, Word document, PowerPoint deck, Excel file, Copilot Page, OneNote page, or a OneDrive/SharePoint file. Microsoft lists .docx, .pptx, .xlsx, .pdf, .loop, .page, and OneNote pages among supported reference types.

Keep safety practical: use proper Microsoft 365 permissions, choose material that belongs to the task, and avoid unnecessary customer, employee, or student data unless your organization has approved the workflow. That is more useful than pretending AI can never work with real sources.

Source: Microsoft Support: Add references to your Microsoft 365 Copilot Notebook

Step 1: create a notebook for the project

Open Copilot Notebooks and choose New notebook. Give it a name a person will understand three weeks from now:

• Q3 customer offer
• Onboarding checklist
• Spring course planning
• Internal FAQ for new process

Avoid names like Test, AI stuff, or Misc. A notebook should be a small project room, not another junk drawer.

Step 2: add references

Choose Add content to References and add a small set of sources. Microsoft describes several ways to add material, including suggested references, search, upload, link, OneDrive, and drag-and-drop.

A good first set might include:

• the latest project brief,
• meeting notes or a meeting recap,
• one relevant PDF or slide deck,
• a previous Copilot Page about the project,
• a short process or policy document.

Microsoft says Copilot Chat users can add up to 50 references. Microsoft 365 Copilot users can add more than 300, but only up to the first 300 are used for grounding. For a beginner workflow, the limit is not the point. If you need more than eight sources in the first attempt, the project is probably too large.

Source: Microsoft Support: Add references to your Microsoft 365 Copilot Notebook

Step 3: ask Copilot from the notebook sources

Inside the selected notebook, use Message Copilot. Ask Copilot to work from the references and to be clear about what needs human review.

Copy this first prompt if you want:

Use only the references in this notebook. Summarize the project in five bullets, list the open questions, and suggest the next three actions a human should review before we share anything with the team.

The prompt does not need to be perfect. What matters is that you point Copilot toward the sources, the output, and the review step.

Microsoft describes Copilot Notebooks as a workspace where answers are grounded in notebook content and selected references. It is not the same as open web research, and you should not treat it as if Copilot automatically sees your whole OneDrive, email, Teams, or the web.

Source: Microsoft Support: How Microsoft 365 Copilot Notebooks works

Step 4: turn the answer into a usable brief

Once you have a first summary, ask Copilot to shape it into something you can review. For example:

Turn this into a one-page project brief with: purpose, confirmed facts from the references, open decisions, risks or missing information, and a short action list for the next meeting. Mark anything uncertain as "needs human check".

For a solo consultant, that might become a client summary. An admin-heavy team might use it as an onboarding checklist. A teacher or project lead might turn it into a planning note. The point is that Copilot drafts the first structured version, not that Copilot takes over the decision.

Step 5: review before you use the answer

Check the brief before you send it anywhere:

• Are the right files in the references?
• Have old duplicates been removed?
• Are dates, names, prices, and obligations correct?
• Is sensitive information included unnecessarily?
• Did Copilot mark uncertain parts clearly?
• Does any source need to be replaced or updated?

Microsoft's FAQ reminds users that generative AI is not always accurate and that answers should be double-checked before decisions or actions. That is a good standard even for small projects.

Source: Microsoft Support: Frequently asked questions about Microsoft 365 Copilot Notebooks

Step 6: share only when permissions are clear

If the notebook should be shared, select Share, add names or email addresses, and choose Invite. This is where it is easy to move too fast. Microsoft says sharing a notebook can also give others access to linked files when possible, and invited users currently get editing access rather than read-only access.

So do a quick permission check: should these people see every linked file? Should they be able to edit the notebook? If the answer is unclear, wait and adjust file access first.

Source: Microsoft Support: Share a Microsoft 365 Copilot Notebook

Copy this: a reusable project-brief prompt

You are helping me turn this Copilot Notebook into a reviewed work brief.

Use only the notebook references unless I explicitly ask otherwise.

Task:
1. Summarize the current situation in five bullets.
2. List the three most important decisions or questions still open.
3. Draft a short brief for [team/client/class/meeting].
4. Mark uncertain claims as "needs human check".
5. End with a practical action list for the next meeting or work session.

Before writing the final brief, tell me if the references look too thin, outdated, or inconsistent.

Common mistakes

• One notebook for everything. Make one per project instead.
• Too many old or half-relevant references.
• Assuming Copilot uses the web or every Microsoft 365 file automatically.
• Sharing the notebook without checking linked files.
• Treating the brief as final without human review.
• Deleting notebooks as part of experimentation. Microsoft describes limited recovery, so experiment with small harmless workspaces instead.

Next step

If this works for one project, create a simple team rule: one notebook per project, a clear name, a named source owner, and one short review step before anything is shared.

If you want Copilot to become a clear work routine instead of another loose chat tab, Hammer can help you choose the first project workflow. We can also help set simple source and permission rules, with a review habit your team can actually follow.