AI at Work

Why can't Copilot find the right company information?

A file existing in Microsoft 365 does not guarantee Copilot will use it in an answer. Check the Copilot experience and account, whether the person can access the source, whether that source is searchable, and whether the question identifies the relevant material. Then check that the material actually supports the answer.

The life of a company document
  1. Write itOne current version, with an owner
  2. Save itWhere the team expects to look
  3. Name itA title a colleague would search for
  4. Find itCheck that the source is accessible and searchable
  5. Review itUpdate or retire it when it changes

Access permits retrieval; it does not guarantee that the right source is found or interpreted correctly.

First establish which problem you have

"Copilot cannot find anything" can describe several different experiences. It may return no source, locate the wrong document, cite the right document but miss its exception, or produce an answer that nobody can verify. These failures need different remedies.

Keep one concrete failed question and the source a knowledgeable colleague expected it to use. That pair gives the discussion a focus. Without it, an investigation can drift into licence changes, prompt training or a large information-management project before anyone has established what failed.

Also identify the exact application, signed-in account and available work-data features. The Copilot name appears across different experiences. An answer using general web information is not evidence that a search of your organisation's material has taken place. Your administrator can confirm the capabilities enabled for the people doing this work.

Access comes before retrieval

Microsoft states that Copilot access is scoped to the signed-in user's permissions. Being inside the Microsoft 365 environment does not grant it visibility of everything the organisation holds. If the employee cannot access the source, a better prompt is not a substitute for a legitimate access decision.

The reverse also matters. If a person has overly broad access, permission-respecting search may make material easier for them to discover. An unexpectedly revealing answer should trigger a review of the source permissions. Avoid solving a failed search by sharing a whole library more widely than the job requires.

Check access as the affected employee, not only as an administrator or the document owner. The person who wrote a policy may have a very different view of the organisation's files from the person trying to apply it.

Searchability and availability are separate questions

Microsoft's semantic-index documentation explains that supported content, site search settings and indexing affect what can be retrieved. It also documents different handling for new material and updates. Do not assume a file uploaded moments ago will behave exactly like an established, searchable document.

File type and location matter. The current support matrix has exclusions, including some mailbox and archive scenarios. Check that documentation for the actual source rather than applying a generic claim that Copilot can search everything in Microsoft 365. Additional connected systems require their own configuration and access arrangements.

A missing result can therefore be an administrative or coverage issue. Record the location, file type and observed behaviour for the administrator. Avoid repeatedly rewriting the same question when the required source is outside the available search path.

Help the search distinguish the right material

An organisation may have proposals, meeting notes and approved policies discussing the same subject. A broad question gives the assistant little help distinguishing them. Naming the relevant service, period and governing source can make the intended scope clearer.

A direct reference to a known document is useful for diagnosis. If the assistant can answer from that file but struggles to find it through a general question, discovery is a more plausible problem than the model's ability to understand the passage. This observation is a starting point for investigation, not proof of a particular technical cause.

Use titles and descriptive information that help colleagues understand the source too. A document called "Final new latest" gives little context about its authority. A clear title, effective date and responsible owner can support both human review and a more precise search request. They do not guarantee a ranking position or correct answer.

Finding the document is only part of the job

Consider a fictional travel policy with an older general rule and a newer amendment for a particular staff group. An answer based on the general rule could look entirely reasonable. The important issue is the applicable amendment, not how confidently the assistant writes.

A citation lets the reviewer inspect a source. It does not establish that the interpretation is correct or that all relevant sources were found. This is especially important where a missing exception changes an entitlement, a contractual commitment or an operational decision.

Observed resultQuestion to resolve
No relevant source appearsCan this user access it, and can this experience search it?
A similar but wrong source appearsIs the scope specific enough, and is the governing source identifiable?
The right source is cited but the answer is wrongDoes the cited passage actually support the conclusion, including exceptions?
Sources disagreeWho can decide which version applies to this question?

Fix the cause and repeat the actual question

After a correction, return to the failed question with the employee who needs the answer. Confirm what changed: the source became accessible, a current version became identifiable, or the question acquired necessary scope. Record any continuing limitation in ordinary language.

A few known questions are useful for checking whether a change helps, provided they include difficult and ambiguous cases. Ask a knowledgeable person to assess the answers. An assistant confirming its own answer is not an independent check.

Buy additional capability only when the missing requirement is clear. Some teams need help with search configuration; others need an agreed current source or better task definition. Acuity's starting point is the work and the tools already available. Microsoft documentation below was checked on 3 October 2026; source coverage and product behaviour can change.

Sources and product references

Checked 3 October 2026. Features and access can change, so check what your own licence includes.

  1. Microsoft: Copilot architecture and user access boundaries
  2. Microsoft: semantic indexing, supported sources and index updates
  3. Microsoft: preparing SharePoint information and access for Copilot

Editorial guidance informed by Acuity's work with teams. Examples are fictional and client materials stay private. To record who owns an AI use and when it is reviewed, see AI Register.