Documents and knowledge: store, find, use with Copilot.
Libraries with metadata and versions carry the filing, search finds by permission, and Copilot and agents answer from the same documents, citing their sources.
One library per document type, with metadata that search understands.
At a manufacturer of measuring instruments, test reports, drawings and customer correspondence each sit in a library of their own with the rights of the team that needs them. One content type per document type brings required columns, a template and, if needed, a retention label, maintained once in the content type gallery and published to every site that needs it; values such as customer, instrument family and phase come from the term store, so that everyone picks the same term and filters, views and search work across the whole collection. A document set keeps everything on one case together, such as the approval of an instrument, with shared metadata and access of its own. Views group the same collection by customer, phase or year, and folders stay where they separate rights. Whoever creates a library and holds a Copilot licence describes its purpose, and Copilot in SharePoint suggests columns that new documents fill in themselves on upload; how hubs and sites order the libraries is in the chapter on structure and navigation.
02
Versions, content approval and document ID make a version valid.
The calibration work instruction stands as major version 3.0 for every reader, the draft 3.1 only for editors and approvers: major and minor versions with content approval separate work from validity, and every version stays in the version history with date, person and comment. You set the version limit per library, automatic or manual, matched to recovery and storage; versions above the limit disappear past the recycle bin, content under a retention policy excepted, and a report shows beforehand how much storage the versions take up. The Document ID service gives every file a fixed number with your organisation's prefix; a link to it leads to the file even after it moves, and minutes, contracts and tickets refer to the number. Where several people write at the same time, we do without check-out, and the template on the content type puts customer and number into the header.
03
Records lock what has to remain evidence.
A completed test report becomes a record through a retention label from Purview: editing and deletion are blocked, unlocking and locking create versions, and for a regulatory record nobody can remove the label, not even an administrator. The label is set by a person by hand, by the content type as its default, or by a policy automatically by library, keyword or sensitive information, with a simulation that shows beforehand which documents it will hit. At the end of the period a named person decides on deletion, in several stages, and deleted records remain provable. For a quality management system this means: the valid directive lives in the controlled library with content approval; when it is withdrawn, a workflow moves it to the site's archive and declares it a record, and the audit finds every version with name and date. Which licence records and the disposition review need is in the chapter on licences and cost.
04
Document processing and eSignature run inside the library.
A supplier's invoice lands scanned in the intake library; a prebuilt model reads receipt number, date, supplier and amount into columns, text recognition makes scanned pages searchable, and what the model reads with low confidence is flagged by a column for checking. These services, formerly under the name Syntex, run as document processing for Microsoft 365 without a licence commitment through an Azure subscription; the monthly allowance and the meters behind it are in the chapter on licences and cost. Autofill columns come with the Copilot licence of the person who creates them and fill every new file, even if the person uploading has no licence; the guide names English-language files, which is why we test every column with your documents in your languages before it goes live. After approval a contract goes from the library for signature: SharePoint eSignature creates simple electronic signatures under eIDAS, external people sign as guests through Entra ID, every step is in the Purview audit log, and where your specialists require a higher level, we connect Adobe Acrobat Sign or Docusign.
05
Search finds by columns and by rights.
A service technician searches for calibration on the home site: in the Directives vertical the valid work instruction sits at the top, a bookmark puts the calibration protocol template first, and a filter on validity hides the old versions. Behind it lies one index across SharePoint, OneDrive, Teams and connected systems that stores for every item who may open it; every query shows only those results, in Microsoft Search as in Copilot. Maintained columns become filters in the search schema, verticals narrow the search to directives, projects or forms, bookmarks and acronyms explain the organisation's terms, and Copilot connectors bring a wiki, a network drive or the ERP into the same index with the rights of the source. With a Copilot licence, Copilot Search is added, questions in natural language over the same index; without a licence, keyword search remains. Query analytics show searches without results, and every gap gets a measure. If a site is shared too widely, search finds that first; which is why we check sharing before we extend search.
06
Copilot and agents answer from the same documents, with sources.
An employee asks Copilot in SharePoint on the Quality site which calibration interval applies to the instrument family; the answer gives the interval and links the work instruction as its source. Copilot sees only what the person may open, and therefore also finds what is shared too widely. Site owners build an agent from a site, a library or selected files, with a name, purpose, behaviour and starter questions, set it as the site's main agent and share it by link, into a Teams chat too; the agent is a file in the library, with versions like every document. With the owners we pick the sources, mark outdated content or move it to the archive so that the agent finds the current version, and take sensitive sites out of search and Copilot with Restricted Content Discovery. One agent per site answers questions about that site; questions across all areas, with business systems and with rules on which version applies, are the Company Brain pattern, which has a page of its own.
07
The QMS shows what document control looks like in SharePoint.
In the manufacturer's quality management the building blocks interlock: content types for directive, work instruction, form and process description with required fields such as process, person in charge, standard clause and next review date; a document ID that survives a move; major and minor versions with content approval, so that readers see the valid version and editors the draft; a workflow for review and approval with deputies and deadlines that stops an author from approving her own version; the reminder before the review date and the escalation after it; read confirmations recorded with version and time in a list; withdrawn versions as records. An integrated management system for quality, environment and occupational safety uses the same building blocks with shared process overviews and separate roles where one discipline needs them. Certification remains a professional judgement by your auditors; the platform delivers the evidence.
What you decide.
One library per document type or one library per team with folders?
Options
1One library per document type with content type and views
2One library per team with the folder structure of the file server
3Document sets per case in one library
Our recommendation: One library per document type with a content type where many people search for the same kind of document: directives, contracts, test reports, drawings. Document sets per case where everything on a project, a customer or a person should stay together, with shared metadata and access of its own. We take the folder structure of the file server as the starting point where it has proven itself, one level deep, with the rights on the library and not on the folder.
What we advise against: One library for everything with seven folder levels and rights on individual folders: search still finds things, but nobody can tell any more who sees what.
Content approval with minor versions or simple versioning?
Options
1Major and minor versions with content approval for controlled documents
2Major versions only, the approval as a column with a flow
3No approval, the version history is enough
Our recommendation: Major and minor versions with content approval for controlled documents where readers may see only the valid version: directives, regulations, work instructions, form templates. Major versions only for working documents that change daily, with the version history as evidence. The approval as a column with a flow for documents with approval paths by amount or contract type, where the request carries the link to exactly the version under review.
What we advise against: Content approval in the project files where documents change daily: every version waits for an approval, and the team falls back on OneDrive.
Record, regulatory record or retention policy?
Options
1A retention policy on the library, without records
2A retention label that declares the document a record
3A regulatory record
Our recommendation: A retention policy for the large part of the documents: it keeps a copy even when someone deletes, and locks nobody out. The record for evidence that has to stay unchanged, such as test reports, receipts and withdrawn directives; the label comes from the content type or from a policy, and a person with the role can unlock it when needed. The regulatory record only where a regulation requires the irreversible lock, because not even your administration can lift it any more.
What we advise against: Setting regulatory records everywhere out of caution: a wrongly labelled document can then no longer be corrected until the end of the period.
Copilot in SharePoint, a site agent or a Company Brain?
Options
1Copilot in SharePoint on every site, without an agent of its own
2One site agent per area with chosen sources
3A Company Brain across all areas and business systems
Our recommendation: First Copilot in SharePoint, which is available on every site, and one site agent for the library with the most questions, usually directives or HR, with sources the owners have chosen and a test with authorised and unauthorised accounts. One agent per area follows once the first one answers questions that used to arrive by email. The Company Brain comes when questions go beyond areas and business systems and need rules on which version applies; where it takes shape in the Microsoft stack is in the Microsoft AI/SI guide.
What we advise against: Laying an agent over the whole intranet before sharing has been checked: it is the first to find every over-wide share.
Status and sources.
As of: October 2026
As of 29 May 2025
Automatic version limits are the recommended setting.
SharePoint offers an automatic version limit for libraries: all versions of the last 30 days are kept, after that hourly, daily and weekly versions up to a cap of 500. Microsoft recommends the setting but does not enforce it; manual limits by count or age remain possible.
A retention label from Microsoft Purview declares a SharePoint document a record: editing and deletion are blocked, unlocking and locking create versions. For a regulatory record nobody can remove the label, not even an administrator, and the retention period can only be extended.
Syntex is now document processing for Microsoft 365.
The pay-as-you-go services previously offered under Microsoft Syntex run as document processing services without a licence commitment: prebuilt contract model, autofill columns, content assembly, translation, text recognition and eSignature. The contract model extracts parties, duration and renewal date, currently from PDF and image files.
SharePoint eSignature is available in Switzerland too.
Microsoft offers eSignature worldwide through the Microsoft 365 public cloud, with the exception of Indonesia. The signatures are simple electronic signatures under eIDAS; external signers access the document as guests through Entra ID. Every step appears in the Microsoft Purview audit log, and signature requests can be tracked in the Approvals app in Teams.
Autofill columns fill every new file, whatever the uploader's licence.
Copilot in SharePoint suggests columns with instructions from up to 20 files in a library. Once saved, every newly uploaded file gets its metadata automatically, even if the person uploading has no Copilot licence; existing files are processed on selection. The guide currently names English-language files and recommends no more than 10 columns per library.
Copilot Search with a licence, Microsoft Search for everyone.
Anyone with a Microsoft Copilot licence sees a dedicated search tab in the Microsoft Copilot app: queries in natural language and content from all enabled connectors, with no further setup. Without that licence, Microsoft Search is available in the app and in SharePoint, keyword-based; connector content appears there through configured tabs and result types. Admins maintain bookmarks and acronyms for both.
Site agents: created with a Copilot licence, also used on a usage basis.
Creating an agent for a site requires a Microsoft Copilot licence and the right to add files to the site. People without a licence can use it as soon as your organisation has set up pay-as-you-go billing through an Azure resource. The agents need no activation; they are available on every site a person has permissions for.
This is how we put it into practice: place, required fields, template and ownership per document type, built with one division and its real documents and handed over as a filing plan. Document management in Microsoft 365
As few as possible and as many as it takes for views, filters and search to answer your divisions' questions: per document type usually a handful of required columns such as customer, document type, phase and validity, with values from the term store. Every further column has to be filled in by someone, or an autofill column fills it; Microsoft recommends no more than ten autofill columns per library. Columns nobody filters by after the pilot are removed again.
Does search also find the content of scanned PDFs?
Only if the file has a text layer. Scans from the copier often arrive as images, and search then sees only the file name and the columns. The text recognition of document processing lays a text layer over scanned pages, after which search finds terms inside the document, and a model reads details such as receipt number or date into columns. For collections from a migration we plan text recognition as a step of its own and settle beforehand which meter it runs on.
Does Copilot also answer from drafts and old versions?
From everything the person asking may open. Anyone with edit rights sees minor versions and drafts, so Copilot can take them into its answer; readers see only the approved major version. Old versions that sit as files in an archive folder are found by Copilot as well, which is why we mark them as withdrawn or take the archive area out of search. A site under Restricted Content Discovery stays invisible to search and Copilot outside the site.
What changes for search when we rename or move a library?
The index picks up the new address on its next run, and results then point to the new place. Links with a document ID keep leading to the file as long as it stays within the site; links with a path, such as in bookmarks, on pages or in emails, you have to update. That is why minutes and pages refer to the document ID, and we plan the move of whole libraries with a list of the links that depend on them.
How long is a version kept?
As long as the library's limit allows: with the automatic limit all versions of the last thirty days are kept, then hourly, daily and weekly versions up to the cap; with a manual limit the chosen count or age. Versions above the limit are deleted permanently, bypassing the recycle bin. Content under a retention policy or an eDiscovery hold is excepted, and versions of records cannot be deleted.
Where does a signed document end up?
Back in the library, next to the approved version, with the signatures in the PDF; the request and every step are in the Purview audit log, and signature requests can be tracked in the Approvals app in Teams. External people sign as guests through Entra ID. For contracts that require a higher signature level we connect a provider's service with its own licence; which level a document needs is for your specialists to decide.
When does a document store become enterprise content management?
When documents arrive from outside and carry retention periods from the moment they come in: mail, email attachments and forms in an intake library, a file plan with class, period and reviewers per document type, periods started by an event such as the financial year end, the disposition review and an archive that takes content out of active storage. The Enterprise Content Management page describes these building blocks; the store from this chapter remains their foundation.
Next chapter · Chapter 5
Who sees what in the intranet, from group to guest.
Who sees what in the intranet, from the group to the guest?