Microsoft 365 Copilot uses company information that each signed-in user has permission to view. Before connecting shared files, check that those permissions match what your business intends. Additional data connections have their own access settings to review.
Imagine a staff handbook everyone can read and a management planning document shared with a smaller group. An assistant should give each person answers from the documents intended for them. I would ask to see that demonstrated with ordinary staff accounts before opening the assistant to the team.
Existing access deserves a closer look
Microsoft's privacy documentation, updated 3 November 2026, says Copilot "only surfaces organizational data to which individual users have at least view permissions."
That makes your existing sharing rules part of the AI rollout. A file shared with the whole company is already available to that audience. An assistant adds another way to find and summarize it. Review who should have access, including broad groups and old project memberships.
Microsoft's deployment guidance, updated 13 November, puts remediating oversharing among its main actions. For a small team, I would begin with the folders holding sensitive material and ask their owners to confirm the intended readers.
Check each connected source
Connecting another document system brings another decision. Microsoft's Copilot connector setup guide lists two visibility choices: "Only users with access to the content" and "Everyone in the organization."
Ask your supplier or administrator to show which setting applies to each connection. For restricted material, the intended readers should remain the intended readers through the assistant too. Check that the system recognizes each person correctly.
There is a useful distinction for SharePoint agents as well. Microsoft's agent access guidance says access to the agent and access to its source documents are separate checks. A shared agent can give different people different answers because they have different document permissions.
Include an access-change demonstration
Someone moves teams. A project closes. A document becomes restricted. Ask what happens to the assistant's search results after that change.
For indexed Copilot connectors, Microsoft's validation documentation, updated 4 November, says permission updates occur during a full crawl rather than an incremental crawl. It also warns that changes may take time to appear. That guidance concerns connector indexing; the timing for your exact source and connection needs checking.
I would ask for a small demonstration using fictional documents:
- Sign in as people with different access and ask about both documents.
- Check the answer, source preview and citation as well as the original file.
- Remove a test user's access, record the time, then repeat the questions after the documented update process.
- Agree who handles an access problem and how the affected connection is paused while it is investigated.
This is my suggested buying check, rather than a test result or a security guarantee. The broader knowledge-assistant acceptance checks cover answer quality and handover.
The same question applies on your own server
An assistant on your own server also needs rules for who can read each document collection. For example, Open WebUI documents private knowledge bases with access granted to named users or groups. Ask for the same staff-account and access-change demonstration in whichever system you choose.
If you want an assistant that answers from your company documents, bring a list of document collections and intended readers to a free 45-minute call. I can help you define what the access demonstration needs to show.
Frequently asked questions
Can Copilot access my SharePoint?
Microsoft documents SharePoint as a source for its work assistants. What a person can retrieve depends on their permissions, the Copilot experience they use and the configured source. Ask your administrator to show the scope for your setup.
Is hiding a site from Copilot the same as changing access?
Microsoft describes Restricted Content Discovery as a temporary discovery control. Existing permissions stay in place, and people with access can still open the content directly. Review access permissions separately.