A consulting firm's Dynamics 365 Sales environment uses a custom Copilot Studio agent that answers reps' questions about internal policies (expense limits, discount approval thresholds) during live deal reviews, pulling answers from a SharePoint site. The firm wants the agent's answers to stay current as policies change without a developer redeploying anything. Which extension approach fits best?
Select an answer to reveal the explanation.
Short Explanation
Think about where the truth actually lives. The policy numbers live on a SharePoint site that gets edited whenever finance changes a threshold, so the smartest move is to have the agent read straight from that source every time someone asks a question. That way the agent's answer is only ever as stale as the SharePoint page itself. Typing the numbers into the agent's own instructions feels quick, but it freezes those numbers in time until somebody remembers to go edit the agent again, which is exactly the maintenance burden the team is trying to avoid. Copying everything into a separate table on a nightly schedule sounds more official, but if that job skips daytime hours, reps could be quoting numbers that were already changed that morning. And tucking policy answers into outreach sequence steps solves a completely different problem than answering questions during a deal review. The pattern to recognize is: whenever you want an agent to reflect a source of truth that changes on its own schedule, connect it to that source directly instead of copying or freezing a snapshot of it.
Full Explanation
The correct answer is D. Connecting the agent's knowledge source directly to the live SharePoint site means the agent always retrieves the current policy text at query time, so updates to expense limits or discount thresholds are reflected the moment the source changes, with no redeployment needed. Option A is incorrect because hardcoded values in system instructions go stale the instant a policy changes and require a developer to edit and republish the agent, defeating the goal of low-maintenance currency. Option B is incorrect because a nightly batch job that pauses during working hours can leave the Dataverse copy out of sync for most of the business day, and it introduces an unnecessary duplicate data store to maintain. Option C is incorrect because sequence steps are for guiding rep outreach actions, not for hosting reference answers to ad hoc policy questions; embedding policy text there does not give the agent a queryable knowledge source and would need manual updates in yet another place. Grounding the agent directly in the authoritative live source is the only option that satisfies both accuracy and low ongoing maintenance.