A consultancy is designing a Microsoft 365 Copilot agent for a law-firm matter. The agent may use files on that matter's SharePoint site and must not search the rest of the tenant. Which scope should the architect set?
Select an answer to reveal the explanation.
Short Explanation
A matter file belongs in that matter's cabinet. You scope this Microsoft 365 Copilot agent to the matter's SharePoint site so the rest of the tenant stays out of the search. Telling the model to prefer the right site still lets the search wander.
Full Explanation
The law-firm pattern forbids a tenant-wide search. The Microsoft 365 Copilot agent is scoped to the matter's SharePoint site, and files outside that site are not in its knowledge. Searching the whole tenant and instructing the model to prefer the matter site when it can tell still indexes every site, and a preference sentence does not remove them. Grounding the agent on every mailbox in the firm so a matter question can read other clients' mail widens the search to other clients, which is the opposite of a matter boundary. Publishing the agent on a public website that indexes the firm's entire document corpus moves the agent off Microsoft 365 and opens the corpus to people who are not on the matter. A prompt that names the matter is not a scope. Exam caveat: the lawyer's own permissions can be broader than this agent should use. The agent scope is the matter site, not everything that lawyer can open. Operational check: ask a question whose answer exists only on a different client's site and confirm the agent does not return that file.