Episode
Copilot Inherits Your Mess: Modernizing Microsoft 365 for AI with Richard Harbridge [MVP]
- Published
- Sep 1, 2026
- Duration seconds
- 3932
- Processing state
not_requested
Actions
POST https://stenobird.com/v1/public/podcasts/m365-fm-modern-work-security-and-productivity-with-microsoft-365-7311214/episodes/copilot-inherits-your-mess-modernizing-microsoft-365-for-ai-with-richard-harbridge-mvp/transcription-requests
Idempotently request low-priority transcript generation for this episode.GET https://stenobird.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365-7311214/copilot-inherits-your-mess-modernizing-microsoft-365-for-ai-with-richard-harbridge-mvp.md
Read the agent-friendly Markdown representation of this episode resource.
Summary
Microsoft 365 Copilot doesn’t arrive in a clean Microsoft 365 tenant. It arrives in an environment that organizations have been building for years — full of SharePoint sites, Teams, OneDrive content, duplicate documents, historic migrations, guest accounts, inconsistent permissions, forgotten workspaces, broken ownership models, and content nobody has reviewed in years.For traditional Microsoft 365 management, much of this technical debt could remain relatively hidden. AI changes that.In this episode of M365.FM, Mirko Peters talks with Richard Harbridge, Microsoft MVP and industry advisor at ShareGate, about why AI readiness is fundamentally connected to Microsoft 365 modernization and governance.The conversation moves beyond the question of how to deploy Copilot and focuses instead on a more important question: What kind of Microsoft 365 environment are we actually giving AI access to? COPILOT DOESN’T CREATE THE MESS — IT AMPLIFIES IT One of the central ideas in this conversation is that Microsoft Copilot is not necessarily creating entirely new governance problems. Instead, AI makes existing problems significantly more visible and consequential.Organizations have accumulated years of decisions around permissions, sharing, workspace creation, ownership, migrations, external access, inactive content and collaboration.Richard describes this accumulation using the concept of “sprawl.”Sprawl itself is not automatically bad. A growing number of Teams, SharePoint sites and other resources can be evidence that people are successfully adopting Microsoft 365.The problem begins when that growth happens faster than the organization’s ability to manage it.Temporary permissions become permanent. Old collaboration spaces remain accessible. Ownership changes. Business structures evo…