SharePoint Knowledge Base: Let Copilot Build It for You

Do you remember the old SharePoint wiki? I sure do. It went away with the older versions of SharePoint, and Microsoft never really gave us a modern replacement. Until now. Here’s my post and associated video on how to create one.

The new SharePoint knowledge base is that replacement, and honestly, it’s something people have been asking for for years. Even better, you don’t have to write it all yourself. You can point Copilot at files you already have, and it builds the whole thing for you.

📚 What Is a SharePoint Knowledge Base?

A knowledge base holds guidance, decisions, and procedures. When I think of one, I picture my old job in a big IT department. We had tons of server documentation, and we all needed it to troubleshoot each other’s systems during on-call weeks.

Procedure manuals, onboarding guides, and how-to articles are all great examples. Here’s the thing: people want answers without opening a pile of Word documents. So instead of files, a SharePoint knowledge base gives them pages they can click through, like a website.

So how is this different from a document library?

  • A document library holds files and folders: working documents in many formats.
  • A SharePoint knowledge base holds connected pages, guidance, and FAQs, all built on markdown.

Note: This feature is brand new and still rolling out in November 2026. So you may not see it in your tenant yet. For the latest on availability, check Microsoft’s announcement.

🧭 Four Ways to Start a SharePoint Knowledge Base

First, where do you find it? You have two options:

  1. In any SharePoint site, click New and choose Knowledge base.
  2. On the SharePoint start page, click Build on the left. It will then ask which site to put it in.
SharePoint Mark8 Project Team menu with Knowledge base option highlighted

Next, the Let’s build a new knowledge base screen gives you four starting points:

  1. Blank: start from scratch and write or paste your own pages.
  2. Import: bring in markdown files or folders, a Confluence HTML export, or a classic SharePoint wiki.
  3. Copilot: describe what you want, point it to your sources, and let it build the pages.
  4. Autopilot: build it from the Microsoft 365 Copilot app. This one isn’t in my tenant yet, so stay tuned.
Create a new knowledge base screen with options for blank, Markdown, Confluence, or classic wiki imports

Also, just like libraries, you can have more than one SharePoint knowledge base on a site. Each one shows up in Site contents with its own icon.

Fun fact: under the hood, it really is a library. If you click Switch to library view, you’ll see plain folders full of markdown files. In other words, each folder is a level in your navigation. Then click Switch to knowledge base view to go back.

✍️ Create a Knowledge Base Manually

Let’s start with the simplest option. I created one called “Mark 8 Knowledge” on my Mark 8 project site.

  1. Click New and choose Knowledge base.
  2. Choose Blank and give it a name, just like naming a new list.
  3. Open your new Welcome and Getting started pages. These are full of tips and ideas, like how-tos, onboarding guides, and FAQs.
  4. Click New page, give it a title, and type or paste your content.
  5. Click Save and exit.

That’s it! As a result, editing your SharePoint knowledge base feels just like editing a regular SharePoint page.

SharePoint Mark8 Project Team knowledge base page explaining when to create one

🤖 Let Copilot Build Your SharePoint Knowledge Base

Now for my favorite part. Copilot can read a whole library of files and turn them into organized pages. For my demo, I used a library full of IT help desk documents.

  1. Go to the site, or even the specific library, that holds your source files.
  2. Open Copilot and describe the knowledge base you want.
  3. Click Use credits when Copilot asks for permission.
  4. Answer any follow-up questions and review the proposed goal and scope.

For example, here are two prompts I like:

Create a knowledge base for IT help desk based on all the files in the Documents library.

Create an onboarding knowledge base for new hires from the files in this library, with sections for tools, processes, and FAQs.

The more detail you give it, the better the result. Tell it the name, purpose, sources, questions it should answer, and how to organize it. Plus, you don’t even need the New button. Just ask Copilot on any site to build a knowledge base, and it kicks off its built-in skill.

Important: Building a SharePoint knowledge base with Copilot uses Copilot credits, and so do updates and health checks. Also, be patient. My IT help desk version took about half an hour.

The result was gorgeous, though. In fact, Copilot organized my whole SharePoint knowledge base into categories and subpages.

SharePoint Contoso IT Help Desk knowledge base page with troubleshooting categories and safe triage guidance

📥 Import Markdown Files

Do you already have markdown files? Then importing is fast, and it doesn’t use any Copilot credits.

  1. Click New, choose Knowledge base, and select Import markdown files.
  2. Drag your .md files in and click Next.
  3. Give your knowledge base a name.

However, there’s one catch. Mine came in as one big flat wall of pages, using the exact file names. So plan to rearrange them into topics and subtopics afterward.

Similarly, classic wiki and Confluence imports into a SharePoint knowledge base work the same way. Keep in mind that every import is a one-time copy, not a sync. So once you move your classic wiki over, you’ll probably want to retire the old one.

🛠️ Edit and Organize Your Pages

Once your SharePoint knowledge base exists, editing it is easy. Here’s what you can do:

  • Add pages anywhere. Click New blank page to create pages and subpages.
  • Switch editors. Use the visual editor, or flip to the source editor to see the raw markdown.
  • Insert images, videos, and tables. One heads-up: you can’t resize images on the page. So edit your image before you insert it.
  • Jump around with page contents. This panel lists the headings on a page, so you can skip to any section.
  • Rearrange the structure. Choose Move up or Move down, or Promote a page up a level. To push a page under another one, choose Make subpage. It works just like editing SharePoint navigation.
  • Check page properties. For Copilot-built pages, this shows the exact source files each page came from. I love that!
  • Use version history, duplicate pages, hide the left navigation, or switch to full width.

What about comments? They’re for editors only. So visitors reading your pages won’t comment. Instead, comments let your editing team talk about the content.

🔄 Keep Your SharePoint Knowledge Base Current

Your SharePoint knowledge base does not update itself when your source files change. If you add, edit, or delete a file, you have to tell Copilot.

For example, you could prompt: “Add the documents in [folder URL] to this knowledge base.” Or try: “Check this knowledge base for updates from its sources. Summarize the proposed changes before updating any KB pages.” I like that second one, because you see the plan before anything changes.

You can also ask Copilot to check the health of your knowledge base. Try: “Check the health of this knowledge base and show me what needs attention.” It looks for things like broken links, pages that aren’t included in the navigation, and incomplete source references. Just keep in mind that a health check doesn’t fact-check your content. It’s looking for structural problems, not whether the information itself is correct.

Also, keep a few rules in mind:

  • One update at a time. Only one Copilot update can run on a knowledge base at once, even across different people. If a coworker is mid-update, wait for theirs to finish.
  • 10 files max per request. Got more? Just break them into batches.
  • Updates can undo your work. During the preview, an update can reverse manual edits or bring back pages you deleted. So review the affected pages afterward.

💡 What about Autopilot? If your organization has Autopilot in the Microsoft 365 Copilot app, you can create and update a knowledge base from there too. It’s optional, so everything in this post works with Copilot in SharePoint alone.

🔐 Permissions and Sharing

Good news: a SharePoint knowledge base just uses SharePoint permissions. Nothing new to learn here.

  • View: people can read pages and ask Copilot questions about them.
  • Edit: people can write, comment, add sources, run health checks, and import content. Site members have this by default.
  • Create: people can make a new knowledge base, including with Copilot. You don’t have to be a site owner.

There’s one quirk, though. There’s no share button for the whole knowledge base. Instead, you can share a single page, which includes its subpages. Or you can share the site itself.

To change permissions of just the library, go to Site contents and open the settings for your knowledge base from there. Then go to permissions, stop inheriting, and give members read access (as shown in the video).

⚠️ Known Limitations

Since the SharePoint knowledge base is brand new, expect some rough edges:

  • Pages don’t inherit the permissions of their source files.
  • Sensitivity labels aren’t supported.
  • Links can break.
  • Some content may get left behind. Copilot told me it hadn’t finished a couple of things, so I had to prompt it to keep going.
  • Images in markdown files aren’t copied over during import.

🤔 Knowledge Base or SharePoint Agent?

Gabriel asked a great question: why build a wiki when a SharePoint agent can answer questions about your documents?

Honestly, it depends on your users. For example, some people want to click, drill down, and browse a table of contents. For that culture, a SharePoint knowledge base is perfect. On the other hand, maybe everyone will just ask Copilot questions anyway. In that case, an agent on your document library may be all you need.

Want another option? I also wrote about building a wiki with Microsoft Loop. And for more ways Copilot is changing SharePoint, check out 10 new Copilot in SharePoint features.

🎓 Keep Learning with IW Mentor

Want to master SharePoint, Copilot, Power Apps, and Power Automate? All of it is in our Ultimate plan at IW Mentor. That’s 50+ hours of no-code training built for business users, not programmers.

Even better, our biggest sale of the year is coming! From the day after Thanksgiving through December 4, you can get 40% off Ultimate. Get the details here. Plus, Ultimate members now get our new monthly solution lab webinars for free. Each one builds a real business solution, and non-members pay $150 per webinar.

And don’t forget Power Hour! It’s live every Wednesday at 11am Central. Sign up for the newsletter, and you can vote on next week’s topic. You pick it, I cover it.

❓ FAQs

What is a SharePoint knowledge base?

It’s a modern wiki in SharePoint. It turns guidance and procedures into connected pages instead of separate documents.

Do I need Copilot to create one?

No. You can build one manually or import markdown files without Copilot. However, building or updating one with Copilot uses Copilot credits.

Does it update automatically when my files change?

No. You have to ask Copilot to incorporate new or changed files.

So, are you seeing the new SharePoint knowledge base in your tenant yet? And what would you build first? Let me know in the comments!

Here is the associated video:

📚 References

Leave a Reply