『M365 Show - Modern work, security, and productivity with Microsoft 365』のカバーアート

M365 Show - Modern work, security, and productivity with Microsoft 365

M365 Show - Modern work, security, and productivity with Microsoft 365

著者： Mirko Peters (Microsoft 365 consultant and trainer)
無料で聴く

このコンテンツについて

 Welcome to the M365 Show — your essential podcast for everything Microsoft 365, Azure, and beyond. Join us as we explore the latest developments across Power BI, Power Platform, Microsoft Teams, Viva, Fabric, Purview, Security, and the entire Microsoft ecosystem. Each episode delivers expert insights, real-world use cases, best practices, and interviews with industry leaders to help you stay ahead in the fast-moving world of cloud, collaboration, and data innovation. Whether you're an IT professional, business leader, developer, or data enthusiast, the M365 Show brings the knowledge, trends, and strategies you need to thrive in the modern digital workplace. Tune in, level up, and make the most of everything Microsoft has to offer.



Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-show-modern-work-security-and-productivity-with-microsoft-365--6704921/support.Copyright Mirko Peters / m365.Show - News, tips, and best practices for Microsoft 365 admins 政治・政府
エピソード
  • Entropy in the Lakehouse: Fabric’s Answer to Identity Chaos

    Entropy in the Lakehouse: Fabric’s Answer to Identity Chaos
    2025/12/27
    In this episode, we dive headfirst into one of the most quietly painful problems in modern data platforms: identity chaos. As organizations scale their analytics environments, especially within lakehouse architectures, identity, access control, and governance tend to sprawl faster than anyone wants to admit. The result is entropy. Confusing permissions, brittle security models, duplicated identities, and a growing gap between data teams and governance teams. This conversation explores how Microsoft Fabric approaches this challenge and why identity management is becoming a foundational concern for lakehouse design, not an afterthought. What This Episode Covers We break down how entropy creeps into lakehouse environments and why traditional identity models struggle to keep up with modern analytics platforms. From fragmented access policies to disconnected tooling, identity chaos directly impacts security, compliance, and developer productivity. You’ll hear a practical discussion of how Fabric simplifies identity by unifying experiences across data engineering, analytics, and governance, reducing friction without sacrificing control. Key themes include:
    • Why identity sprawl is inevitable in growing data platforms
    • How entropy shows up in real-world lakehouse deployments
    • The relationship between identity, governance, and trust in analytics
    • How Microsoft Fabric aligns identity across workloads
    • What data leaders should rethink about access management
    Why Identity Matters in the Lakehouse The lakehouse promises flexibility, scalability, and speed. But without a coherent identity strategy, those benefits collapse under operational complexity. Permissions become unclear, audits become painful, and teams slow down as they wait for access or work around broken models. This episode connects the dots between identity management, data governance, and platform reliability, showing why Fabric’s approach is designed to reduce entropy instead of adding another layer of abstraction. Who This Episode Is For This discussion is especially relevant for:
    • Data engineers and analytics engineers
    • Platform and cloud architects
    • Security and governance leaders
    • Organizations adopting or evaluating Microsoft Fabric
    • Anyone dealing with identity chaos in a lakehouse environment


    Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-show-modern-work-security-and-productivity-with-microsoft-365--6704921/support.

    Follow us on:
    LInkedIn
    Substack
    続きを読む 一部表示
    1 時間 5 分
  • The Teams Manager Illusion

    The Teams Manager Illusion
    2025/12/26
    (00:00:00) The Unseen Voice of Governance
    (00:00:43) The Readiness Review Cycle
    (00:07:19) The Never-Ending Loop of Governance
    (00:13:05) Unmanaged Objects: A Persistent Problem
    (00:20:47) Compliance Workshop: A Choreographed Dance
    (00:28:09) License True-Up: Sustaining the Narrative
    (00:34:05) The Rise of Script Run: Automation's Silent Entry
    (00:34:20) The Bot in the Chat
    (00:35:55) Automation and Reassignment
    (00:37:47) The Evolving Readiness Index

    Microsoft Teams promises order: dashboards, scores, policies, labels, and admin centers that suggest everything is being managed. But for many organizations, that sense of control is an illusion. In this episode, we pull back the curtain on Microsoft Teams governance and explore why so many environments feel “almost under control” without ever truly becoming stable, secure, or simple. From endless readiness reviews to dashboards stuck in permanent amber, this conversation examines how modern collaboration tooling quietly rewards motion over outcomes. We walk through what really happens inside large Microsoft 365 tenants after the initial rollout hype fades: orphaned teams multiply, guest access quietly expands, compliance tools remain in audit mode, and exceptions become permanent features. Meanwhile, leadership is reassured by scores, heatmaps, and maturity models that appear to show progress — even when the underlying risks remain unchanged. This episode challenges the belief that more tools automatically mean better governance. Instead, it asks harder questions about ownership, responsibility, and why Teams environments so often evolve into systems that justify their own complexity. In this episode, we discuss:
    • Why Microsoft Teams governance often feels “managed” without actually being controlled
    • How dashboards, readiness scores, and maturity models create false confidence
    • The hidden cost of Teams sprawl, orphaned groups, and unmanaged collaboration spaces
    • Why compliance tools stay in “audit mode” far longer than anyone admits
    • How guest access, exceptions, and admin bypasses slowly become the default
    • The difference between governance theater and real operational control
    • Why many Teams environments are designed to continue indefinitely, not resolve cleanly
    • What admins, architects, and IT leaders quietly experience behind the admin center glow
    Who this episode is for:
    • Microsoft 365 and Teams administrators
    • IT architects and security engineers
    • Compliance, risk, and governance professionals
    • Consultants working with Microsoft 365 tenants
    • Leaders who sense something is “off” with their Teams environment but can’t quite name it
    Key takeaway: If your Teams environment always feels “not quite ready,” it might not be failing — it might be functioning exactly as designed. The illusion isn’t accidental. It’s structural. This episode isn’t about blaming tools or people. It’s about understanding the loops we get caught in, the metrics we learn to trust without questioning, and how real control often comes from fewer dashboards and more deliberate decisions. If you’ve ever stared at a Teams admin panel late at night wondering why everything looks managed but nothing feels resolved — this episode is for you.

    Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-show-modern-work-security-and-productivity-with-microsoft-365--6704921/support.

    Follow us on:
    LInkedIn
    Substack
    続きを読む 一部表示
    4 時間 22 分
  • The Compliance Time-Loop: Why Your M365 Policies Are Lying

    The Compliance Time-Loop: Why Your M365 Policies Are Lying
    2025/12/25
    Everything is green. Policies are enabled. Dashboards are stable. Audit logs reconcile.So why does governance still drift? In this episode, we replay the same Microsoft 365 tenant, the same retention policies, and the same discovery queries—again and again—until we uncover the hidden truth: correct outcomes can still mask behavioral change. Creation compresses. Survival shortens. Discovery stabilizes on a shrinking corpus. This is not a failure story.It’s a story about meaning drifting while execution stays correct. What This Episode Is About Most Microsoft 365 compliance failures don’t show up as errors.They show up as silence. This episode walks through a real-world replay of:SharePoint Online versioningMicrosoft Purview retention labelsPreservation Hold Libraries (PHL)Unified Audit Log (UAL)eDiscovery (Standard & Premium)AutoSave and co-authoring behaviorPre-governance cleanup and survival timingEverything works.Nothing breaks.And yet—the meaning changes. Core Question Explored What happens when systems keep answering correctly, but the question has quietly changed? Instead of asking “Did the policy execute?”, this episode asks:Did creation preserve enough history?Did content survive long enough to be governed?Did discovery reflect what actually happened—or only what remained?Episode Structure (Chapter Breakdown) 🔁 Loop Zero — Defining “Green”Establishing a clean Microsoft 365 baselineRetention policies enabled and propagatedAudit logs active and reconcilingSecure Score and Compliance Manager stableeDiscovery returning expected resultsKey insight:Green dashboards prove repetition, not intent. ✏️ Loop One — Creation Drift Question: Does edit activity equal version history? What we observe:AutoSave and co-authoring aggressively consolidate editsFileModified events far exceed version incrementsSingle-author, spaced saves behave differently than co-authoring burstsRetention preserves versions that exist—not edits that occurredResult:Creation compresses meaning at birth. 🕒 Loop Two — Survival Drift Question: Does content live long enough to be governed? What we observe:Meeting recordings, temp exports, and OneDrive spillover disappear quicklyRetention labels often arrive after deletionPreservation Hold Libraries only capture what survives to first deleteGovernance clocks lose to operational cleanup clocksResult:You can’t retain what’s already gone. 🔍 Loop Three — Discovery Drift Question: Does stable discovery equal complete discovery? What we observe:Identical KQL searches return flat results week after weekUpload activity rises, but discoverable content does notExecution times stay flat because scope quietly shrinksDiscovery faithfully reflects what survived—not what happenedResult:Search consistency ≠ scope consistency. The Pattern Revealed Across all loops, the same pattern emerges:Creation compressesIntelligent versioning bundles editsFewer near-term recoverable states existSurvival shortensContent dies before governance intersectsCleanup precedes retentionDiscovery stabilizesSearches run fast over a thinner corpusFlat results mask upstream filtrationNothing failed.The behavior changed. The Lie Exposed “The policy executed, therefore the intent was enforced.” Execution proves availability.It does not prove meaning. Retention retains versions, not edits.Discovery finds what exists, not what briefly appeared.Green dashboards confirm repetition—not alignment with business intent. Practical Takeaways What to Measure Instead of “Green” 1. Creation RatioVersions created vs. FileModified eventsWatch for flattening under stable collaboration patterns2. Survival Hit RatePercentage of items labeled before deletionEspecially for recordings and transient content3. Discovery Coverage RatioDiscoverable items vs. created itemsFlat coverage during rising activity signals driftWho This Episode Is ForMicrosoft 365 ArchitectsCompliance & Records ManagerseDiscovery & Legal Operations teamsSecurity & Governance LeadsAnyone responsible for “retention” promisesIf you’ve ever said:“But the policy is on”“The search ran successfully”“Compliance Manager is green”…this episode is for you. One-Sentence Takeaway If your results never change, you’re governing repetition—not reality.Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-show-modern-work-security-and-productivity-with-microsoft-365--6704921/support.Follow us on:LInkedInSubstack
    続きを読む 一部表示
    1 時間 20 分
まだレビューはありません