A Microsoft MVP helping you grow your business by empowering everyone to achieve more with Microsoft 365 and #Copilot
Melbourne
Joined February 2014
- Tweets6.7K
- Following452
- Followers1.4K
- Likes3.1K
Pinned Tweet
I've had early access to SharePoint knowledge bases, and there's plenty to get into.
Connected pages for people and agents, built from the documents you already have.
Here's what I've learnt from two builds, and what I'd plan before starting yours.
Decide who can read your SharePoint knowledge base before adding sources.
KB pages don't inherit source permissions. Content from a restricted document can become readable by everyone with KB access.
Review the audience before asking Copilot to build.
Before Copilot builds your SharePoint knowledge base, ask it to propose the structure.
In my HR build, I reviewed the topics, navigation and routes for employees and managers first.
You can change a plan before you have pages to reorganise.
I imported an 84-page markdown knowledge base into SharePoint, with its hierarchy and page properties.
The structure you prepare becomes the structure people navigate. Review it before importing.
Here's the first-look build:
youtu.be/NVFZhF4FS5w
Your SharePoint knowledge base should follow the questions people ask.
A new starter needs to know what happens on day one. That answer might span HR, IT and onboarding documents.
Give them connected guidance they can follow through the task.
Daniel Anderson | Microsoft MVP retweeted
SharePoint + Copilot just got a lot more interesting 👀
I counted down my top 10 new things you can do, no developer required.
1. 🔎 Ask Copilot questions about SharePoint content
2. 📄 Compare different versions of SharePoint files
3. ⏪ Review SharePoint version history and restore previous versions
4. ✂️ Reorganize PDFs and extract pages into a new PDF
5. 🖼️ Edit images directly from a SharePoint document library
6. ✨ Create interactive HTML experiences from SharePoint content
7. 🌐 Create SharePoint pages and homepages from HTML
8. ⚡ Create workflows and approvals using natural language
9. 🧠 Create, test, and improve reusable Copilot skills
10. 📊 Use Copilot with SharePoint site analytics
Full video in the comments👇
Copilot in SharePoint gives you scope to delegate small, complete jobs where the documents already live.
Define the outcome, check the result and keep approval at the right step. This PDF workflow shows the approach:
youtu.be/R2uCU3Pw3Tk
There's useful Copilot and SharePoint work to do with the content you already have.
Choose information people repeatedly need help applying. Then build a better way to use it. Our policy checker illustrates that thinking:
youtu.be/2KRsVpcB3Ag
SharePoint can be where an AI-created business experience becomes part of everyday work.
The design may begin elsewhere. Publishing, navigation and ongoing ownership still need a home. This learning hub shows one approach:
youtu.be/RZcF6mcCeGg
Look for connected steps when assessing where Copilot can help in SharePoint.
Preparing a file may involve selecting content, assembling an output and sharing it. Map the whole job, including the checks and approvals, before deciding what to delegate.
Good SharePoint design reduces the decisions a person has to make just to find the right guidance.
Use their situation to narrow the questions and show the relevant next step. Copilot and interactive pages give you different ways to support that.
Start a SharePoint build with the business brief.
Who is the page for? What should they be able to do? Which content and design rules matter?
AI can help produce the page, but you still need to make those decisions to judge whether the result fits.
When Copilot works on SharePoint content, check what needs to survive the transformation.
It might be the wording, page layout or branding. Define those requirements up front. A file being created doesn't, by itself, tell you that it's ready to use.
Copilot chat and SharePoint pages can support the same task in different ways.
Some people want to ask a question. Others want guided choices or the full source. Design those routes around the information people need, with a clear way to check it.
A SharePoint solution needs to be maintainable by the people who own it.
Before launching, work through routine changes: a new link, revised guidance, a different contact. Decide who can make those updates and how they'll check the result.
Build review into the Copilot workflow you're designing in SharePoint.
Decide what a person needs to inspect before accepting the result. Source material, intermediate files and the final output can help them check the work instead of taking completion on trust.
Copilot makes content ownership in SharePoint worth paying closer attention to.
When people use a page to answer questions or make decisions, a policy change needs to reach that page too. Agree who maintains the information and how changes are checked.
Build a SharePoint Homepage in Claude Design and Upload It as an HTML Page danielanderson.io/articles/u…
Test a SharePoint solution by following a real task from start to finish.
Can someone find the guidance, use it and take the next step? Include the handoff into Copilot. A page looking right is one check; the working journey needs its own review.