Copilot

Tenant permissions

The sharing and access settings across your organisation's Microsoft 365 environment that decide which mail, files and sites each person can open, and so what Copilot can surface.

Copilot shows what your permissions already allow Your permissions feed Copilot, which reaches your own files and an old shared folder, but not files that were never shared with you. Your permissions set by sharing Copilot Your files Old shared folder Not shared out of reach Copilot surfaces what you can open, old shares included

Copilot sees what you can see, no more and no less. It grounds answers in Microsoft Graph, and Microsoft states that it only surfaces organisational data you have at least view permission for. It relies on the same access controls as SharePoint, OneDrive, Outlook and Teams, so it never overrides them.

The catch is in the word "can". Old, loosely shared folders that nobody remembers granting access to are within reach too, and a broad question can bring them back up. Copilot did not create that exposure; it removed the friction that kept it harmless. That is why the track treats a periodic look at what is shared across your tenant as part of using Copilot responsibly, the practical side of the EU AI Act's Article 4 AI-literacy duty.

Often confused with: Sharing an agent. Sharing an Agent Builder agent passes on only the knowledge sources you added. It never widens anyone's tenant permissions, and the agent still respects the permissions of whoever chats with it.

See it in a lesson: Giving Copilot context

Further reading

← All terms

Rollo AI AcademyWant your whole team speaking this language?Knowing the words is a start. Rollo Academy gets teams genuinely working with AI, through hands-on, in-company training built around your own work.Discover Rollo Academy →