SharePoint Knowledge Base can import Markdown files and folders, bringing existing documentation into SharePoint pages instead of requiring teams to recreate it manually. This is useful for documentation owners and SharePoint users moving procedures, technical guides, or team knowledge into a central collection. Laura Rogers [MVP] is the publisher associated with this import topic.
The import feature accepts individual Markdown files or a folder of Markdown content. When you import a folder, SharePoint keeps its folder hierarchy, which can help preserve the organization of an existing documentation set. The resulting pages become part of the SharePoint Knowledge Base.
Knowledge-base content can be read by people and used in Microsoft 365 AI experiences, including Copilot in SharePoint. Importing content and asking Copilot questions about it are separate capabilities: importing does not itself require a Copilot license, while Copilot use may require the appropriate license or credits.
This feature is aimed at organizations with existing Markdown documentation, such as procedures, internal guidance, or technical documentation. It is in Frontier preview, so availability can vary between organizations and the interface may change.
Microsoft's current requirements include usage-based billing. You also need permission to create or edit content in the destination knowledge base and access to the source files or folder. The input must be Markdown in format; changing another file's extension to does not convert its contents.
You can also choose Import Markdown files as the initial content source when creating a knowledge base.
Import is a one-time copy, not a live link to the original files. Later edits in either location do not automatically update the other, so teams should decide which location is authoritative.
Images referenced by Markdown files are not copied automatically. Review imported pages and check that images and other linked resources remain accessible. Source permissions and sensitivity labels also do not transfer; imported pages use the destination knowledge base's permissions.
For large libraries, handle content in smaller batches and review results before continuing. Avoid starting another import into the same destination while one is running. Check the import report before retrying an interrupted import, since a retry can create duplicates. Other migration options include Confluence spaces and eligible SharePoint Classic wiki pages.
Open the knowledge base, select New > Import, choose Markdown files or Folder, select the content, and follow the prompts.
Yes. Importing a folder preserves its hierarchy in the knowledge base.
The import itself does not require a Copilot license. Asking Copilot questions about knowledge-base content may require the appropriate license or credits.
Source permissions and sensitivity labels do not transfer; the imported pages use the destination knowledge base's permissions. Referenced images are not copied automatically.