The Microsoft Copilot gap
Microsoft Copilot on SharePoint, and where it stops for building documentation
Property and facility teams increasingly ask Microsoft 365 Copilot about their buildings, and get answers that read well but cannot be relied on when someone outside the team checks them. This page sets out what Copilot on SharePoint does answer, what it does not, and what has to sit underneath before building documentation becomes evidence.
Why can Microsoft Copilot not answer questions about my buildings?
Microsoft 365 Copilot answers from the documents it can reach in SharePoint, and it reads them as text rather than as building records. It has no model of which building a file belongs to, which documents that building is required to hold, or whether a certificate has expired, so questions about the compliance status of a building fall outside what it can answer.
Microsoft 365 Copilot on SharePoint compared with Findable
Both tools search documents. They are built for different jobs, so they diverge as soon as the question is about a building rather than about a file.
| Documentation task | Microsoft 365 Copilot on SharePoint | Findable |
|---|---|---|
| Find a document by filename or title | Yes. Copilot searches the SharePoint sites and libraries the user already has permission to open. | Yes, and the same document is also retrievable by building, system and document type. |
| Answer a question about one specific building | Partly. Accuracy depends on site structure and file naming, because files are not linked to a building record. | Yes. Every document is bound to a building, so an answer can be scoped to that building and cited back to the source file. |
| Know which documents a building is required to have | No. Copilot answers from the documents that exist. It has no model of the documents that should exist. | Yes. The document set is compared against requirement lists such as TEK17 and NS 3451. |
| Flag expired or missing certificates | Only if validity dates are already maintained as SharePoint metadata and someone builds the reporting on top. | Yes. Validity dates are read out of the documents themselves and tracked as a status per building. |
| Read scanned and handwritten documents | Partly. Scanned PDFs are indexed through OCR. Older scans, drawings and handwritten notes stay unreliable. | Yes. OCR and handwriting recognition tuned for construction archives, including scanned binders. |
| Work across sources outside SharePoint | Possible through Microsoft Graph connectors, each of which needs separate setup, licensing and maintenance. | Yes. SharePoint, file servers, contractor folders and legacy systems become one evidence layer. |
What Microsoft 365 Copilot can reach depends on your licensing, which Microsoft Graph connectors are enabled, and how your SharePoint sites, metadata and permissions are configured. The rows above describe default behaviour on a standard SharePoint document library.
This is a fit comparison for building documentation, not a verdict on Microsoft Copilot. Copilot is built for general knowledge work across Microsoft 365 and is good at it. Building documentation is a different job, because the unit that matters is the building, not the file.
Common questions
Does Findable replace Microsoft Copilot?
No. Most customers run both. Copilot stays the assistant for email, documents and meetings across Microsoft 365. Findable is the layer that turns building documentation into records that can be checked, so questions about compliance, handover and portfolio risk have an answer that holds up.
What makes a building document different from any other document?
A building document only means something in context: which building it belongs to, which system it covers, whether it is the current version, and whether it is still valid. Generic search treats it as text. Building documentation has to be treated as evidence with a status.
What needs to be in place before Microsoft 365 Copilot can search SharePoint?
A Microsoft 365 Copilot licence, content stored in SharePoint or OneDrive, and permissions set so the right people reach the right sites. Sources outside Microsoft 365 need Microsoft Graph connectors, which are configured and licensed separately.
See it against your own documents
Bring one building, one audit question, or one handover folder. We will show what your current document set can and cannot prove.
Book a demo