Episode Details

SharePoint Lists Copilot knowledge: in this episode of M365.fm, Mirko Peters dismantles the myth that “modernization” always means migration—and shows how SharePoint Lists can now act as first‑class Copilot knowledge without moving a single row into Dataverse or Fabric. He starts with the “migration mirage”: the reflex to rebuild working lists in new platforms just because AI or Power BI are involved, burning budget on duplicated data, broken flows, and licensing surprises while delivering exactly the same business value you already had.

Mirko walks through how this reflex formed: years of hearing that “real” AI and analytics require “enterprise‑grade” stores, so SharePoint Lists were treated like embarrassing, legacy cousins. He contrasts that belief with the quiet shift Microsoft just shipped—Copilot Studio can now connect directly to SharePoint lists as live knowledge sources, under the same permissions and governance you already configured. No ETL pipelines, no schema redesign, no re‑implementing security; Copilot simply queries the list in real time, in the user’s own security context.

He then breaks down what the new SharePoint List connector actually does. In Copilot Studio, you add a list as knowledge, choose from My Lists or Recent Lists, authenticate like a normal user, and Copilot immediately treats that list as an authoritative data source. When HR updates the holiday list or Sales adjusts a pipeline row, the change is reflected instantly in Copilot answers—no cache refresh, no re‑indexing, no “sync job.” Governance stays intact: if a user cannot open a row in SharePoint, Copilot will not surface it either, eliminating the need for shadow service accounts or duplicated permissions.

The episode also exposes the cost of unnecessary migrations. Mirko shows how moving lists to Dataverse “for Copilot” stacks licensing, schema mapping, and Power Automate rework on top of existing solutions without improving outcomes. He argues that the real bottleneck was never storage, but access: Copilot needed a safe, direct path to operational data, which the new connector finally provides. With that in place, the smartest move is often to leave lists where they are, stabilize governance, and let Copilot bring conversational intelligence to them in situ instead of dragging them through yet another platform hop.

Throughout the conversation, you get concrete examples: a holiday calendar list that instantly powers “When is our next company holiday?” queries, a pipeline list that Copilot can summarize by stage and owner, and operations lists that become living knowledge cells instead of candidates for expensive “modernization projects.” Mirko gives you language to push back on reflex migrations—framing “authentication, not replication” as the new standard—and a checklist for when a list is perfectly fine and when a real move to Dataverse or Fabric is still justified

WHAT YOU WILL LEARN

• Why “modernization = migration” is a myth that burns time, money, and governance.
• How the new SharePoint List connector lets Copilot Studio use live lists as knowledge without ETL.
• How real‑time, permission‑aware access replaces fragile exports, dataflows, and duplicated schemas.

  Listen Now