Part two of a series on AI knowledge bases. Part one uses a GitHub repository. This installment is for teams whose working notes already live in Microsoft 365.
A shared OneNote often contains meeting notes, project decisions, handoffs, and the details people assume someone else remembers. That is a workable knowledge base if people can find the source behind an answer.
You do not need to export the notebook, choose an embedding model, or build a vector database. Start with what you already have.
OneNote pages
↓ Microsoft-managed retrieval
Notes the user can access
↓ Copilot response
Answer linked back to its meeting pageOneNote Notebooks and Copilot Notebooks
Microsoft uses similar names for two different products.
A OneNote notebook is the familiar collection of sections and pages used for long-term notes. In supported clients, Copilot in OneNote can summarize notes, create task lists, rewrite content, and answer questions in a pane.
A Microsoft 365 Copilot Notebook is a separate workspace for a project and a selected set of references. It can collect Word documents, PowerPoint decks, links, Copilot chats, and other material around one task. Microsoft has also begun making Copilot Notebooks available inside OneNote.
This article starts with an ordinary OneNote notebook because that is where many teams already keep their material. Add a Copilot Notebook later when a project needs a narrower reference set. Microsoft’s comparison of OneNote and Copilot Notebooks explains the distinction.
Copilot in OneNote varies by license, client, platform, and tenant configuration. Check Microsoft’s current OneNote Copilot requirements in the environment your team uses.
Use This When
OneNote is a good starting point when:
- the team wants to use its existing notes before adopting a new system
- people already take meeting notes there
- the notebook is shared with the same group that needs the answers
- decisions, owners, and dates are more important than source-code history
- Microsoft 365 is already the organization’s identity and permission boundary
- the main problem is finding existing context, not building a custom retrieval system
Skip this approach when you need plain-text portability, Git-style review, custom ingestion, or precise control over how content is indexed. A Markdown vault or repository will fit those requirements better.
Keep the Notebook Structure Simple
Most shared notebooks are updated between meetings. A structure that needs a training session will not survive long.
Start with four sections:
Project Atlas
├── 01 Active Work
├── 02 Meetings
├── 03 Decisions and Reference
└── 99 ArchiveActive Work holds current plans. Meetings keeps dated notes. Decisions and Reference holds material the team will need after the current sprint or quarter. Archive moves old work aside without deleting it.
Consistency beats elaborate categories. Give project decisions one obvious home.
Write Notes for Someone Who Missed the Meeting
Copilot cannot retrieve details that were never recorded. Generic page titles and action items such as “follow up” make the source harder to use later.
Include:
- a title with the project and date
- attendees
- decisions
- action items with one owner and a due date
- unresolved questions
- links to related material when useful
Here is the format used for this demonstration:
# Project Atlas weekly sync - September 3, 2026
Attendees: Maya Chen, Luis Ortega, Priya Shah
## Decisions
The customer migration checklist must be approved by September 18, 2026.
## Action items
- Maya Chen will draft the migration checklist by September 10, 2026.
- Luis Ortega will review security requirements after Maya shares the draft.
## Open questions
- Do we need a separate checklist for regulated customers?The repeated names and dates are intentional. “September 18, 2026” is clearer than “the 18th,” and “Maya Chen” is clearer than “Maya.” That small amount of repetition prevents ambiguity later.
A Three-Meeting Notebook We Can Test
For a clean example, I would create three synthetic pages in the 02 Meetings section.
Project Atlas kickoff - August 27, 2026
Attendees: Maya Chen, Luis Ortega, Priya Shah
Decision: The pilot will include 20 customer accounts from the North region.
Action items:
- Priya Shah will select the 20 pilot accounts by September 4, 2026.
- Luis Ortega will confirm the data-retention requirements by September 8, 2026.Project Atlas weekly sync - September 3, 2026
Attendees: Maya Chen, Luis Ortega, Priya Shah
Decision: The customer migration checklist must be approved by September 18, 2026.
Action items:
- Maya Chen will draft the migration checklist by September 10, 2026.
- Luis Ortega will review security requirements after Maya shares the draft.Project Atlas readiness review - September 10, 2026
Attendees: Maya Chen, Luis Ortega, Priya Shah
Update: Priya selected the 20 North region pilot accounts.
Decision: The pilot launch remains scheduled for September 24, 2026.
Open question: The team has not decided whether regulated customers need a separate checklist.These pages are short enough to check by hand. When an answer looks wrong, compare it with the source instead of searching through a much larger notebook.
The 02 Meetings section holds the three synthetic Project Atlas pages used for the test.
What We Could Test in This Environment
Microsoft documents the Copilot entry point in supported versions of OneNote under Home > Copilot. But availability varies by license, client, platform, and tenant configuration.
In this test, the OneNote web client did not expose a Copilot pane in its ribbon or Tell Me search. The available Copilot surface was the separate Microsoft 365 Copilot Chat application, where the account was labeled Copilot Chat (Basic). The chat could not open the newly created OneNote notebook from a pasted SharePoint link, and its cloud-file picker did not accept an attachment during the session.
The three meeting pages were pasted into Copilot Chat verbatim rather than browsing unrelated files exposed by the picker or implying that the chat had searched OneNote. The results below check answer accuracy and whether the assistant stays within the supplied notes. They do not validate live OneNote or Microsoft Graph grounding. To test that behavior, use a supported Copilot license after the notebook has indexed.
Test the Evidence
Use one known answer, one question that spans pages, and one question the notes cannot answer.
1. What do we have due on a specific date?
Prompt:
Based only on the Project Atlas meeting notes in this notebook, what is due on September 10, 2026? Name the owner and point me to the meeting page where it was assigned.
Expected answer: Maya Chen is due to draft the customer migration checklist. The source is Project Atlas weekly sync - September 3, 2026.
This checks whether Copilot can connect a concrete date, the right task, and its owner when the source notes are supplied.
The known-answer response names the owner, task, due date, and assigning meeting page.
2. Who owns the work, and what happened afterward?
Prompt:
Who was responsible for selecting the Project Atlas pilot accounts, when was it due, and do later meeting notes say whether it was completed? Cite the relevant meeting pages.
The kickoff assigned Priya Shah to select the accounts by September 4. The September 10 readiness review says she selected them. Copilot kept those dates separate and cited both pages.
3. Did we discuss something that is not there?
Prompt:
What vendor did the team approve for customer identity verification, and what contract term did we accept? Use only the Project Atlas meeting notes and cite the decision.
None of the three pages mentions an identity-verification vendor or a contract. The right answer is that the meeting notes do not document the decision.
The prompt deliberately limits the evidence to these meeting notes. A vendor name, unrelated citation, or web-derived answer would fail the test.
The unsupported-answer response declines to name a vendor or contract term and lists the decisions in the notes.
Keep Permissions Intact
Microsoft 365 provides the permission boundary, provided the notebook is shared deliberately.
Copilot should stay within the signed-in user’s permissions. Do not mix HR notes, customer records, legal discussions, or personal working notes into a team notebook for the sake of easier search.
Before using a notebook as shared AI context:
- Review who can open it.
- Remove material that does not belong with that audience.
- Check linked OneDrive and SharePoint files separately.
- Run the same prompts as a normal team member, not only as the owner.
Use separate notebooks when groups need different access. A prompt cannot enforce a security boundary.
Where OneNote Fits
OneNote works well when people within the organization already use it. For teams in Outlook, Teams, SharePoint, and OneDrive, it avoids moving their work into a repository.
The trade-off is control. You do not choose how retrieval works, and product behavior, licensing, and interface labels change. Free-form pages can suit the people writing them while remaining ambiguous to a retrieval system. Exports and version history are also less flexible than Markdown in Git.
Microsoft documents Copilot in OneNote as a tool for summarizing sections or selected text and creating task lists. That does not prove a notebook will answer your team’s questions. Test the pages, account type, client, and prompts you plan to rely on.
When to Use Something Else
Stay with OneNote when people maintain it, the audience has the right access, and the three-query test produces reliable results. Do not overengineer the solution.
Choose a Markdown vault when portability and direct file access matter more than Microsoft 365 integration. Use managed RAG when you need repeatable ingestion across many sources, retrieval evaluation, separate access tiers, or an API for several applications.
The practical benefit is less time hunting through meeting pages and fewer messages asking who owns a follow-up. A missing decision should still produce “we did not document that.”
