A company has a Microsoft 365 E5 subscription and uses Microsoft Copilot Studio.

Verified Answer : =

Enable the agent to answer questions about company policies → From Copilot Studio, add SharePoint as a Knowledge source.

Identify which departments and policies are connected → From Copilot Studio, configure the SharePoint tool.

This scenario is about designing a Microsoft Copilot Studio agent that uses a SharePoint Online library containing 10,000 policy PDFs, with a populated Department column for each document.

For the first requirement, the agent must answer questions about company policies. The most direct and correct design choice is to add SharePoint as a Knowledge source in Copilot Studio . This allows the agent to ground its answers in the contents of the policy PDFs stored in the SharePoint library.

For the second requirement, the agent must identify which departments and policies are connected . Since the SharePoint library already includes a structured Department column, the correct design step is to configure the SharePoint tool in Copilot Studio so the agent can use that SharePoint content and its associated metadata more effectively. This supports linking documents to departments rather than only retrieving unstructured text.

Why the other options are not the best fit:

Build a custom model in Microsoft Foundry is unnecessary because the scenario can be solved with native Copilot Studio and SharePoint integration.

Import the PDFs into Microsoft Dataverse adds extra complexity and is not required when SharePoint is already the source.

Use AI Builder to process and feed SharePoint content is not the simplest or most direct design for policy Q & A.

Apply Microsoft Purview sensitivity labels helps with governance, not with department-policy mapping.

Create a Microsoft Dataverse table for the departments is redundant because the department information already exists in SharePoint metadata.

Upgrade to SharePoint Premium is not required for this design.