A consultant configuring Copilot for Sales in Outlook for an insurance brokerage wants the email assistant to draft renewal reminder emails that reference each policyholder's coverage tier, which is stored in a custom Dataverse table linked to the account record rather than the standard account fields Copilot reads by default. Reps report that draft emails omit the coverage tier entirely. What is the most likely cause?
Select an answer to reveal the explanation.
Short Explanation
Picture Copilot as an assistant that can only mention things it has been told exist. By default it knows the standard account fields, but this brokerage stashed coverage tier off in a separate custom table, and nobody pointed the assistant there yet, so it drafts emails as if that detail simply isn't part of the account. Saying the tool can never touch custom data overstates a limitation that is really just a missing setup step. Asking reps to type the value in themselves defeats the whole point of having an assistant draft things automatically. And a licensing problem would usually break drafting altogether, not just quietly skip one field while everything else still works fine. The real gap is that the custom table was never wired in as a source the assistant is allowed to pull from.
Full Explanation
The correct answer is B. Copilot for Sales pulls context from account and opportunity data, but a custom Dataverse table holding coverage tier only becomes visible to the assistant if it is explicitly added to the configured data sources it draws from; otherwise the model has no path to that field and omits it. Option A is incorrect because Copilot for Sales can be configured to read custom tables and fields, so a blanket claim of impossibility misdiagnoses a configuration gap as a hard limitation. Option C is incorrect because the entire value of the assistant is drafting from data automatically; requiring reps to manually type the value first defeats the purpose and is not how the tool is intended to work, nor does it explain a systemic omission across reps. Option D is incorrect because a licensing gap would typically prevent the assistant from functioning or generating drafts at all, not selectively omit one specific field while still producing usable renewal reminder text.