Photo credit: Gemini
Between personal productivity and the nonstop demands of a modern Microsoft 365 environment, no one has time to dig through emails, task boards, and documentation just to understand what’s going on. That’s why Copilot Notebooks have become more than a tool for me. I coined the term our team Notebook has become a second brain for my department.
This post took a long time to write because I had to unlearn what I thought a Copilot Notebook was. What follows isn’t theory. It’s the system I built, the problems it solved, and the clarity it unlocked. If you work in IT, operations, or digital workforce management, I think you’ll see the value immediately.
The key takeaway – Beyond Storage: A System for Thinking
The Copilot Notebook is not:
- A document repository
- A task list
- A static knowledge base
It is a dynamic system that mirrors how my Digital Workforce team thinks and operates.
It acts as:
- Memory – capturing decisions, workflows, and context
- Search layer – surfacing the right information instantly
- Alignment tool – keeping everyone on the same page
- Execution accelerator – turning insight into action
What Is a Copilot Notebook?
A Copilot Notebook is a context-rich workspace inside Microsoft 365 where you can gather files, notes, lists, and data sources, and have Copilot reason over them together.
It’s not just a chat window. It’s a persistent, curated knowledge environment.
- Copilot Chat is single-threaded and ephemeral.
- A Copilot Notebook keeps a stable set of sources that Copilot continuously grounds against.
That means more accurate answers, less repetition, and a reusable intelligence layer that grows over time.
Technical Disclaimer
In order to get the most out of this post, there is a level of technical understanding on the M365 platform I assume the reader will have. Specifically, when I say something like, “SharePoint List” or “Power Automate flow” my assumption is, this jargon will not be greek.
For my technical setup, I have the Copilot Notebook as a hive storing data across my M365 ecosystem (Tickets from our case management system, Team OneNote notebooks, excel exports from or Task board that get fed nightly) all shown on Figure 1.
Note: Keep in mind, trash-in equates to trash-out if your data is dirty. Mentioned earlier, I am using OneNote as a data source for my second brain. By nature, OneNote is usually messy and unstructured. That being said, be intentional with the data you connect and ensure the quality or answers of these data sources are of sufficient quality. Lastly, I have an excel file fed via Power Automate nightly job from my case management system and task board. As of writing, there is no other way to get that data into the Copilot Notebook. If you would like to know how I created this Second Brain, I’d be happy to make a YouTube video on my channel.
Please use the comments to share my blind spots or how I have helped, let’s dig in!
Figure. 1 Diagram for Second Brain
Photo credit: Gemini
From Information Overload to Operational Clarity (from the perspective of an IT Pro)
Every day, a typical Digital Workforce generates signals:
- Task updates across dozens of initiatives
- Automation requests from business partners
- Governance decisions tied to Copilot and M365
- Incident responses and service health alerts
I will use my typical Team task board for example (A simple SharePoint list). It reflects a living system of work that includes:
- Active initiatives like End point device system updates, SharePoint improvements, Power App solutions built, etc.
- Cross-team collaboration where folks have added insights to past work that you know at some point you will need to reference in the future.
- A mix of backlog, in-progress, blocked, and completed items, all constantly shifting
That’s a lot of context to hold in your head and God forbid, you take some PTO.
The Copilot Notebook changes that. Instead of remembering everything, the team can externalize memory—capturing not just tasks, but meaning.
Real Example: Turning Work Into Knowledge
Using Copilot Scheduled Prompts (something I will talk about in a future post) I can create a daily summary of what took place between the task board and the ticket system. This helps me identify trends overtime and what current fire I need to attend. Okay a daily status report is neat, but the title of this post is ‘second brain’ so let’s go deeper…
Mentioned earlier, I said that I had Power App builds, Python scripts, Admin configuration settings on my task board. That means this simple SharePoint list I use houses crucial technical decisions, the departments that benefitted from the solution, if I have contractual details on my tasks (which I do) budget items, license renewals, due dates, are available. Even Team resources are listed on my task board. Meaning, who did the last SharePoint admin task, or Purview thing, who can write JSON, etc.
This is exactly the kind of thinking the notebook preserves.
Instead of losing that context in an email thread, the notebook becomes a place to:
- Capture decision rationale
- Track repeatable intake patterns
- Build institutional knowledge for future requests
- This is the big one, discuss architectural ideas based on the context of past decisions.
Over time, this transforms one-off conversations into reusable intelligence.
Copilot + Notebook = Action, Not Just Insight
The integration of Copilot into this ecosystem amplifies the effect.
Copilot already helps the organization:
- Summarize content
- Generate drafts
- Analyze data
- Retrieve organizational knowledge
Now combine that with a notebook that contains:
- Task board history
- Governance decisions
- Operational patterns
- Team responsibilities
The result is powerful:
You’re no longer just asking, “What do I know?”
You’re asking, “What has this team already learned, and what should I do next?”
Think about this for onboarding. Once the newbie starts handling tickets or broken automations, they can query the second brain as a sort of coach. Or let’s say, years go by, and that one really awesome power automate flow grew in scope and is a liability if you don’t know who benefits from it. Why not ask Copilot “what was the initial purpose of this flow?”
Side tangent: I had to lead a project for a large Windows update. I do not usually manage end point devices and I was tasked with creating a project plan for the new initiative. I asked my Copilot Notebook, “create a project plan based on the last Windows update.” Project Charter and all, it was all there. This probably saved me a day of work!
Example: Leadership Context at Your Fingertips
Because I also play a manager role, take a look at the documented flow in the day in the life of a Digital Workforce Manager using departmental Notebook titled Second Brain
- Morning: Reviewing operational signals and cross-team issues
- Midday: Facilitating planning and technical decisions
- Afternoon: Coordinating intake and workforce strategy
- End of day: Synthesizing insights into actionable direction
That entire rhythm depends on context.
The notebook serves as the memory layer behind that leadership function, allowing:
- Faster decision-making (since I can query past projects and in most cases, Copilot will remind me of a particular direction based on the context of past choices).
- Better alignment across teams (we all view the same KANBAN task board, and query the same Copilot Notebook).
- Reduced dependency on tribal knowledge (fire fighters who save the day or not a scaleable approach. Having that one goto guy who knows everything is actually highlighting a failure in the proper distribution information/mentorship).
Real-Time Awareness: From Incidents to Innovation
Figure 2 below is an active project I am developing to have the second brain be more than a lump of intelligence, but something that can take action in the proper context. Once this is done, you know I will write about it. Feel free to follow below, so that you don’t miss out. But Even in reactive scenarios, like service health incidents or M365 App access issues, context matters.
Let me set the scene, there was a scenario where a SharePoint service was down. I wasn’t quite sure if we relied on that particular service, so I queried my second brain. It informed me of a meeting from three years ago where we made the decision to not enable the service and instead we built something in-house. This was awesome, but I would like to go deeper. So I designed a workflow:
- Microsoft sends an incident email
- Power Automate queries the brain
- The second brain checks whether we use the affected service
- If yes, it drafts a SharePoint news post using vendor language
- It creates an approval for me
- Upon approval, it publishes automatically
This is no longer reaction — it’s informed judgment at machine speed.
A second brain enables:
- Historical incident pattern recognition
- Consistent communication
- Automated decision support
- Removal of bottlenecks
- Event-driven action
Once a process is vetted, you can even remove the approval step. That’s not just reaction but informed judgment.
A second brain reinforces this by:
- Providing historical patterns of incidents
- Capturing prior responses and outcomes
- Enabling consistent, data-informed decisions
- Removing me as the bottleneck
- Once you have a trusted or vetted repeatable process, consider removing the approval step
Figure 2. Using the Second brain to act rather than just be a lowly chat bot
Photo credit: Gemini
Final Thought
My Teams is already doing the hard work:
- Managing complex task ecosystems
- Driving automation across the business
- Governing emerging AI capabilities
- Coordinating across multiple teams
The Copilot Notebook simply ensures that none of that effort is lost.
It turns work into reusable intelligence. And in a world where speed, clarity, and governance all matter—
that’s exactly what a second brain should do.
Support Links
- Getting Started from Copilot Notebooks – https://support.microsoft.com/en-us/microsoft-365-copilot/get-started-with-microsoft-365-copilot-notebooks
Follow
- Apple Podcasts – https://podcasts.apple.com/us/podcast/level-up-m365/id1718776415
- Spotify – https://podcasters.spotify.com/pod/show/levelupm365/
- Newsletter/Socials – https://levelupm365.com/subscribe-social-page/
If this post was helpful support the effort by ether of the following, share, like, subscribe, leave a tip!
Level Up M365 