
A Microsoft MVP 𝗁𝖾𝗅𝗉𝗂𝗇𝗀 develop careers, scale and 𝗀𝗋𝗈𝗐 businesses 𝖻𝗒 𝖾𝗆𝗉𝗈𝗐𝖾𝗋𝗂𝗇𝗀 everyone 𝗍𝗈 𝖺𝖼𝗁𝗂𝖾𝗏𝖾 𝗆𝗈𝗋𝖾 𝗐𝗂𝗍𝗁 𝖬𝗂𝖼𝗋𝗈𝗌𝗈𝖿𝗍 𝟥𝟨𝟧
In a recent YouTube interview hosted by Daniel Anderson [MVP], Microsoft veteran Zach Rosenfield explains why Copilot in SharePoint is evolving into an agentic platform rather than a simple chat tool. The conversation emphasises practical business uses and shows how SharePoint can move from a passive file store to an active workspace. As a result, the episode reframes Copilot as a tool that performs tasks, not only answers questions.
Furthermore, the interview outlines core features such as reusable skills, persistent site memory, and live dashboards that link to data sources like Excel and Microsoft Lists. Zach draws on nearly two decades of SharePoint experience to make the distinction clear. Consequently, the video is aimed at IT leaders, site managers, and knowledge workers who want to apply AI to real work.
Zach explains that Copilot in SharePoint operates across documents, libraries, and lists by using organizational context from Microsoft Graph. In practice, Copilot reads structured content, applies rules, and then acts on that content to create pages, generate files, or update lists. Therefore, the emphasis is on delivering work outputs rather than holding extended chats.
Moreover, the system supports direct creation of Word, Excel, and PowerPoint outputs from SharePoint content, which solves the common blank-page problem. This capability speeds routine tasks and reduces manual copying and formatting. However, it depends on well-managed content to produce reliable results.
The interview highlights a shift toward agentic processes where teams assign goals and success criteria to AI agents instead of scripting every step of a workflow. Zach calls these reusable tools SharePoint skills, and he contrasts them with simple saved prompts by showing how skills encapsulate permissions, workflows, and content rules. As a result, skills can scale knowledge across teams while enforcing governance.
At the same time, Zach argues that not everything belongs inside a skill; some information should live in a persistent site memory layer called SharePoint.md. This separation allows skills to focus on actions and logic, while SharePoint.md stores rules, context, and shared knowledge. Consequently, teams can reuse skills across multiple sites without duplicating core organizational memory.
One of the clearest points in the video is that metadata is not obsolete; in fact, it becomes more valuable in an AI-driven environment. Zach notes that well-structured metadata helps agents find answers faster, improves accuracy, and lowers the cost of AI usage by reducing repeated full-document analysis. Therefore, investing in metadata pays off by improving speed and lowering operational costs.
On the other hand, organizing metadata and building robust information architecture require time and governance discipline. Teams will face tradeoffs between immediate convenience and long-term scale: poorly structured content may work for ad-hoc tasks but will limit agent accuracy and inflate credit consumption. Thus, organisations must balance short-term gains with longer-term effort to curate content and maintain consistent taxonomies.
The interview also covers practical features like live HTML dashboards that connect to Excel, CSV files, and Microsoft Lists to surface real-time insights. Zach shows how those dashboards can drive approvals, reporting, and process monitoring without switching tools, which improves productivity. However, he warns that security and permission boundaries remain essential because agents act on behalf of users and must honor access controls.
Real-world examples include automating finance, legal, sales, and RFP processes where Copilot agents can gather materials, draft responses, and manage review stages. Yet, the approach raises challenges: teams must define clear success criteria, provide feedback during runs, and audit agent decisions to prevent drift. Therefore, while agents reduce manual work, they add new responsibilities for oversight and continuous tuning.
Looking ahead, Zach and Daniel discuss broader trends such as the rise of Copilot agents and action-oriented Copilot Apps that guide approvals and validation within the flow. Consequently, Microsoft appears to be moving away from pure conversation toward interactive, goal-based systems that integrate deeply with SharePoint. This change promises more automation but also increases the need for governance, testing, and clear design.
In summary, the video presents Copilot in SharePoint as a practical platform for doing work, not just chatting about it. Organizations that invest in metadata, information architecture, and reusable skills stand to gain speed and accuracy, while those that skip governance risk higher costs and unreliable outputs. Thus, the interview offers a grounded roadmap for teams that want to adopt AI agents responsibly and at scale.
Copilot SharePoint purpose, SharePoint Copilot features, Copilot for SharePoint use cases, Microsoft Copilot SharePoint integration, SharePoint AI assistant vs chat, Copilot enterprise document management, SharePoint productivity with Copilot, Implement Copilot in SharePoint