A consultant configured Copilot for Sales in Outlook for a manufacturing client. Reps want the email assistant to reference each account's partner certification tier, which is stored in a custom Dataverse table that is not part of the standard Account or Opportunity forms, when drafting renewal emails. Which action extends Copilot for Sales to use this data?
Select an answer to reveal the explanation.
Short Explanation
Think of Copilot for Sales as an assistant that can only talk about what it has actually been shown. If the partner certification tier lives in a table nobody ever introduced to the assistant, it will keep drafting renewal emails as if that tier does not exist, no matter how obvious it seems to a human rep. The fix is to formally connect that table as a knowledge source so the assistant can pull from it the same way it pulls from account and opportunity data. Putting a lookup field on the form just gives a human something new to read — it does not teach the AI anything. Emailing the data around every morning just adds one more inbox item competing for attention, and still leaves a person responsible for connecting the dots. Asking reps to memorize certification tiers is the same problem in a different outfit: it depends on a person doing what the system should be doing automatically. The scenario is really about closing the gap between where data lives and where the AI looks, and knowledge-source connections are the tool built for exactly that gap.
Full Explanation
The correct answer is D. Copilot for Sales in Outlook only surfaces information that has been connected as a data source; a custom Dataverse table holding partner certification tiers is invisible to the assistant until it is added as a knowledge source in Copilot Studio and wired into the Copilot for Sales chat experience. Once connected, the assistant can draw on that table when drafting renewal emails, which is exactly what the scenario requires. Option A is incorrect because adding a lookup field to the Opportunity form only makes the data visible when a rep opens the record manually; it does nothing to feed the AI drafting engine. Option B is incorrect because a daily email digest is a workaround that still requires the rep to read and manually incorporate the data themselves, rather than extending Copilot's own knowledge. Option C is incorrect because relying on reps to memorize account-level details does not scale, introduces error, and is not an extension of the platform at all — it simply avoids the problem the client asked to solve.