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?

The correct answer is the custom table has not been added to the set of data sources Copilot for Sales is configured to reference for account context. 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. The claim that Copilot for Sales cannot access any custom Dataverse tables under any configuration 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. The suggestion that the reps have not manually typed the coverage tier into the email body before requesting a draft 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. The suggestion that the renewal reminder emails were sent from a mailbox that is not licensed for Copilot for Sales 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.