A consultant configures Copilot for Sales for a client that wants sellers to ask natural-language questions and get answers pulled from both Dynamics 365 Sales records and the client's SharePoint document library linked to opportunities. After enabling Copilot, sellers get correct answers about opportunity data, but questions about content inside linked SharePoint proposal documents return nothing. What should the consultant check first?
Select an answer to reveal the explanation.
Short Explanation
Think of Copilot's answer engine as running on two separate rails. One rail is Dataverse search, which is what lets Copilot answer questions about opportunity records, contacts, and other CRM data, and that rail is clearly working here since sellers get correct answers about opportunities. The other rail is Microsoft Search over SharePoint content, and that's what has to be indexing the linked proposal documents before Copilot can ever surface an answer from inside them. If nobody turned on document management for the opportunity table and confirmed the SharePoint site is actually indexed, Copilot has no way to know those files exist, no matter how well the CRM side is configured. Bumping up a seller's permissions won't help, because SharePoint files aren't Dataverse records that security roles govern. Refreshing a scoring model is a completely different Sales Insights feature with nothing to do with search. And dropping the document library into the form as an embedded frame just changes what a person can see on screen; it doesn't tell the search index those documents exist.
Full Explanation
The correct answer is A. Copilot for Sales answers questions from linked SharePoint documents through Microsoft Search indexing of the connected SharePoint site, which is separate from the Dataverse relevance search that powers answers about CRM records. Since sellers already get correct answers about opportunity data, the CRM-side connection is working; the gap is that SharePoint content has not been made searchable to Copilot, so the consultant should verify document management integration is enabled on the opportunity table and that the linked SharePoint site is indexed by Microsoft Search. Option B is incorrect because security roles govern access to Dataverse tables and records; SharePoint documents live outside Dataverse, so raising a seller's role does nothing to expose that content to Copilot. Option C is incorrect because predictive opportunity scoring is a separate Sales Insights feature that estimates win likelihood from historical deal data and has no bearing on Copilot's document search and summarization capability. Option D is incorrect because embedding the SharePoint library as an IFrame only changes what sellers see inside the opportunity form; it does not register the library's content with the search index Copilot queries, so questions about the documents would still return nothing.