{"id":600,"date":"2026-03-31T14:47:33","date_gmt":"2026-03-31T14:47:33","guid":{"rendered":"https:\/\/codingwithramin.com\/?p=600"},"modified":"2026-08-18T20:27:39","modified_gmt":"2026-08-18T20:27:39","slug":"building-a-sharepoint-agent-that-remembers-combining-memory-sharepoint-grounding","status":"publish","type":"post","link":"https:\/\/codingwithramin.com\/?p=600","title":{"rendered":"Building a SharePoint agent that remembers: combining memory and SharePoint grounding"},"content":{"rendered":"\n

In Part 1<\/a>, we built a Foundry agent with long-term memory that could remember user preferences, roles, and context across sessions without any custom embedding pipelines. If you haven’t read that post, start there. This one builds directly on top of that code.<\/p>\n\n\n\n

Memory alone is useful. It just doesn’t go very far on its own. Knowing a user prefers bullet-point summaries or works in finance is helpful context, but it doesn’t change what the agent can actually do. It still can’t answer questions about your company’s policies, find the document someone shared last week, or pull up the latest project brief.<\/p>\n\n\n\n

That’s where SharePoint grounding comes in. In my earlier series on Building Intelligent SharePoint Agents<\/a>, I walked through how the SharePoint tool in Foundry Agent Service grounds agent responses in your actual enterprise content, with automatic indexing and permission-aware retrieval built in.<\/p>\n\n\n\n

This post combines both capabilities into a single agent: one that searches your SharePoint content intelligently and remembers what each user has asked about before, their role, and their preferences. That’s the difference between a search tool and an assistant that actually knows you.<\/p>\n\n\n\n

Why combine memory and SharePoint grounding?<\/h2>\n\n\n\n

Consider what each capability does on its own.<\/p>\n\n\n\n

SharePoint grounding alone lets the agent search your enterprise documents and give accurate, permission-aware answers, but every conversation starts from zero. A user in legal who asks about compliance policies every morning has to re-establish context each time: the agent doesn’t know they’re a lawyer, and it can’t adapt its response style to how they like information delivered.<\/p>\n\n\n\n

Memory alone remembers who the user is and what they care about, but it can’t touch any enterprise content. It’s a knowledgeable assistant locked out of your company’s own documents.<\/p>\n\n\n\n

Combine the two and you get something actually useful. The agent knows this user works in legal, prefers detailed responses with clause references, and asked about the data privacy policy last week. When they come back and ask “any updates on what we discussed?”, it searches SharePoint for changes to that specific policy and answers in the format this user prefers. No context re-establishment needed.<\/p>\n\n\n\n

Prerequisites<\/h2>\n\n\n\n

This post builds on the code from Part 1. Make sure you have:<\/p>\n\n\n\n

From Part 1:<\/strong><\/p>\n\n\n\n