Sam's Dynamics, Power Platform & AI Blog

Showing posts with label Microsoft 365. Show all posts
Showing posts with label Microsoft 365. Show all posts

Friday, 11 September 2026

Copilot and SharePoint: fix the library first

Grounding a Copilot agent on SharePoint: what actually breaks

Pointing an agent at a SharePoint site takes about ten minutes. Pick the site, save, ask a question, get an answer. Everyone's impressed.

Then you ask something you already know the answer to, and it tells you something that was true in 2021.

I've done SharePoint work since long before any of this arrived, and what strikes me is how the old problems have suddenly become expensive. Nobody much cared that the expenses policy lived in six places. Now it's why your agent gives people the wrong expenses answer.


Versions. The agent finds one copy and answers from it, with complete confidence either way. It has no idea FINAL_v3_updated_new is the real one. Pick the authoritative copy, archive the rest, ground only on the place you trust.

Scanned PDFs. If there's no text layer, the file doesn't exist as far as the agent is concerned. That usually includes your signed contracts — the documents people most want to ask about. Check a sample before promising anything.

Permissions. The agent honours SharePoint permissions, which is what you want. The catch is the reverse: anything people could already see is now genuinely findable. Search used to be bad enough that oversharing stayed invisible. That gap is gone. Run a permissions review before you switch anything on, not after someone surfaces the salary spreadsheet in a chat window.

Metadata and file names. Empty columns are context the model doesn't get. You don't need a taxonomy project — a Status column with Draft, Current and Superseded, actually maintained, does most of the work. Same with drafts sitting in the same folder as approved documents. Separate them, or ground only on the finished material.

What this means for your estimate. Roughly two days on the agent, a few weeks on the library. Say that during scoping rather than discovering it halfway through.

It usually lands better than you'd think. Most organisations know their documents are a mess — they've just never had a reason good enough to fix it. This is the first time anyone's been willing to pay for it.


Thanks for reading this article. Hope this Article will help you. Cheers!!!

#Dynamics365 #PowerPlatform #MicrosoftCopilot #DynamicsCRM #CopilotStudio #Dataverse #AIDeveloper #DynamicsAIEngineer #HireAIEngineer #AIEngineer #D365Consultant #CRMDeveloper #AIAgents #MSDyn365


Copilot and SharePoint: fix the library first

Grounding a Copilot agent on SharePoint: what actually breaks Pointing an agent at a SharePoint site takes about ten minutes. Pick the site...