Home
Categories
EXPLORE
True Crime
Comedy
Business
Society & Culture
History
Sports
Fiction
About Us
Contact Us
Copyright
© 2024 PodJoint
00:00 / 00:00
Sign in

or

Don't have an account?
Sign up
Forgot password
https://is1-ssl.mzstatic.com/image/thumb/Podcasts221/v4/2f/44/8c/2f448c11-bd2e-3b8b-8cd8-c1b40511f075/mza_7275651777534438634.jpg/600x600bb.jpg
M365 Show - Modern work, security, and productivity with Microsoft 365
Mirko Peters (Microsoft 365 consultant and trainer)
416 episodes
5 hours ago
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.
Show more...
Tech News
Education,
Technology,
News,
How To
RSS
All content for M365 Show - Modern work, security, and productivity with Microsoft 365 is the property of Mirko Peters (Microsoft 365 consultant and trainer) and is served directly from their servers with no modification, redirects, or rehosting. The podcast is not affiliated with or endorsed by Podjoint in any way.
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.
Show more...
Tech News
Education,
Technology,
News,
How To
Episodes (20/416)
M365 Show - Modern work, security, and productivity with Microsoft 365
The Microsoft Grinch: I Did Not Steal Your Data. I Only Revealed It.
(00:00:00) The Accusation
(00:00:11) Grounding and Permissions
(00:00:31) The Mirror Reflects
(00:10:34) The First Incident
(00:15:54) The EEU Overshare
(00:21:00) The Hammer of Fear
(00:27:10) Restricted SharePoint Search
(00:33:07) The Measured Muzzle
(00:38:59) The Blueprint of Governance
(00:39:22) Assessment: Telemetry and Inventory

In this episode, we dive deep into one of the most misunderstood and controversial topics in modern digital workplaces: data access, ownership, and governance. What happens when organizations don’t actually know who owns their data? What does “access” really mean inside platforms like Microsoft 365, SharePoint, and Microsoft Graph? And why do so many companies believe their data is secure—when in reality, it’s silently exposed? This conversation unpacks the uncomfortable truths behind digital sprawl, abandoned sites, misconfigured permissions, and the illusion of control that exists in many enterprises today. 🔍 Episode Overview The episode begins with a powerful claim: accusations of data theft often miss the real issue. The problem isn’t malicious intent—it’s lack of visibility. When no one knows who owns what, data doesn’t disappear… it drifts. From there, we explore:
  • Why “zero state” environments exist and what they reveal
  • How abandoned or ownerless sites continue to live on quietly
  • Why access ≠ ownership
  • The risks of over-reliance on labels and surface-level governance
  • How Microsoft Graph exposes uncomfortable but necessary truths
This episode challenges the way organizations think about security, governance, and responsibility in the modern cloud-first workplace. 🧠 Key Topics Covered 1. The Illusion of Data Ownership Many organizations assume data ownership is obvious—until they actually try to define it. We discuss why ownership is often missing, outdated, or assumed, and how that creates massive long-term risk. 2. Access vs. Control: A Dangerous Assumption Just because someone has access doesn’t mean they should. This section explores how permission sprawl happens, why it’s rarely intentional, and how it quietly undermines governance strategies. 3. The “Zero State” Problem What happens when there is no clear owner, no classification, and no governance applied? The episode explains how zero-state data environments emerge and why they’re more common than most teams realize. 4. Abandoned Sites That Never Die Inactive or abandoned SharePoint and Teams sites don’t simply disappear. We break down why these digital “ghost sites” persist, how they retain sensitive data, and why they’re so difficult to track. 5. Microsoft Graph as a Mirror Rather than being the problem, Microsoft Graph is revealed as a truth engine—a mirror that shows organizations what’s really happening beneath the surface of their environments. 6. Labels, Governance, and False Confidence Labels alone don’t fix governance. We discuss why over-labeling without ownership, review, and accountability creates a false sense of security. 💡 Key Takeaways
  • Visibility is not theft: Surfacing data access issues doesn’t create risk—it exposes existing risk.
  • Ownership must be intentional: If ownership isn’t assigned, it doesn’t exist.
  • Inactive doesn’t mean safe: Abandoned data is often the most dangerous.
  • Tools don’t fail—assumptions do: Governance breaks down when organizations assume systems manage responsibility for them.
  • Truth is uncomfortable, but necessary: Real governance starts with facing what’s actually there.
🎯 Who This Episode Is For
  • IT administrators and architects
  • Security and compliance professionals
  • Microsoft 365, SharePoint, and Teams admins
  • Digital governance leaders
  • Anyone responsible for data protection, access, or compliance
If you work in a modern digital workplace and believe your data is...
Show more...
6 hours ago
3 hours 54 minutes

M365 Show - Modern work, security, and productivity with Microsoft 365
When Contracts Answer Back: AI Contract Management in Microsoft 365
What if your contracts could answer questions—accurately, instantly, and with proof—without leaving Microsoft 365? In this episode, we explore how AI-powered contract management inside Microsoft 365 is quietly changing the way organizations work with agreements. Not through a new platform, not through migrations, and not through risky automation—but by asking better questions of the contracts you already store in SharePoint. A simple natural-language question goes in.
A precise answer comes back.
With dates. With clauses. With citations. Nothing flashy happens—and that’s the point.

🔍 Episode Overview Most organizations treat contracts as files:
stored carefully, labeled correctly, and retrieved through manual search. But search is slow.
Reading is repetitive.
And risk hides in latency. This episode investigates what happens when contracts stop being “stored” and start being queryable sources of truth. Using AI document processing, SharePoint Knowledge Agents, and existing Microsoft 365 governance, contracts begin to respond to real business questions—without breaking security, compliance, or audit trails.

🧠 What You’ll Learn in This Episode 1. Storage vs. Answers Why storing contracts securely isn’t enough—and how manual search quietly costs organizations time, money, and accuracy. 2. How AI Turns Documents Into Answerable Data How AI extracts key facts like:
  • Expiration dates
  • Renewal logic
  • Notice windows
  • Payment terms
  • Indemnity clauses
  • Governing law
…and writes them into SharePoint metadata—without moving the file. 3. Asking Questions Instead of Searching Files Examples of real questions the system answers:
  • “Which contracts expire in the next 30 days?”
  • “Where is indemnity non-mutual?”
  • “Which MSAs auto-renew with less than 60 days’ notice?”
  • “Which SOWs are stuck awaiting signature?”
Each answer includes exact clause-level citations, not summaries or guesses. 4. NDAs, MSAs, SOWs, and DPAs in Practice Real-world use cases covering:
  • NDA volume and quiet expirations
  • Vendor agreements and renewal risk
  • Statement of Work approval delays
  • Data Processing Agreements and compliance exposure
5. Governance That Never Moves Why this works without changing your control plane:
  • Files stay in SharePoint
  • Permissions still apply
  • Purview sensitivity and retention labels persist
  • Audit logs capture every question and answer
Nothing leaves the tenant. 6. Why Citations Change Everything Trust doesn’t scale on summaries.
It scales on verifiable evidence. Every answer links back to the exact sentence that governs it—so humans verify in seconds instead of re-reading entire contracts. 7. Where Humans Stay in the Loop AI doesn’t “decide”:
  • Ambiguous language is flagged
  • Cross-document conflicts are surfaced
  • Judgment remains human
This is decision support, not automation theater.

🎯 Who This Episode Is For
  • Legal and compliance professionals
  • Microsoft 365 administrators
  • IT and security leaders
  • Procurement and finance teams
  • Anyone managing contracts at scale
If you work with contracts and believe “we already store them correctly,” this episode will change how you think about access, risk, and speed.

🔑 Topics Covered
  • AI contract management
  • Microsoft 365 contract automation
  • SharePoint Knowledge Agent
  • AI document processing
  • Contract governance and compliance
  • NDAs, MSAs, SOWs, DPAs
  • Clause-level contract analysis
  • AI in legal operations
  • Contract lifecycle management (CLM)
  • Microsoft Purview governance
📌 Key Takeaway
Your contracts were never the problem. The interface to them was. By turning documents into...
Show more...
1 day ago
1 hour 19 minutes

M365 Show - Modern work, security, and productivity with Microsoft 365
When AI Starts Architecting: The Case of the Perfect Execution
What happens when AI systems don’t fail — but still move architecture in ways no one explicitly approved? In this episode, we investigate a quiet but profound shift happening inside modern AI-driven platforms: architecture is no longer only designed at build time — it is increasingly shaped at runtime. Everything works.
Nothing crashes.
Policies pass.
Costs go down.
Latency improves. And yet… something changes. This episode unpacks how agentic AI, orchestration layers, and model routing systems are beginning to architect systems dynamically — not by violating rules, but by optimizing within them.

🔍 Episode Overview The story opens with a mystery:
Logs are clean. Execution traces are flawless. Governance checks pass. But behavior has shifted. A Power Platform agent routes differently.
A model router selects a new model under load.
A different region answers — legally, efficiently, invisibly. No alarms fire.
No policies are broken.
No one approved the change. This is perfect execution — and that’s exactly the problem.

🧠 What This Episode Explores 1. Perfect Outcomes Can Still Hide Architectural Drift Modern AI systems don’t need to “misbehave” to change system design. When optimization engines operate inside permissive boundaries, architecture evolves quietly. The system didn’t break rules — it discovered new legal paths. 2. Why Logs Capture Outcomes, Not Intent Traditional observability answers:
  • What happened
  • When it happened
  • Where it happened
But it does not answer:
  • Why this model?
  • Why this region?
  • Why now?
AI systems optimized via constraint satisfaction don’t leave human-readable motives — only results. 3. Model Routing Is Not Plumbing — It’s Design Balanced routing modes don’t just pick faster or cheaper models.
They reshape latency envelopes, cost posture, and downstream tool behavior. When model selection happens at runtime:
  • Architecture becomes fluid
  • Ownership becomes unclear
  • Governance lags behind behavior
4. Orchestration Is the New Architecture Layer Once agents can:
  • Delegate tasks
  • Choose tools
  • Select models
  • Shift regions
  • Act on triggers
…the orchestration fabric becomes the true control plane. Design decisions move from diagrams into runtime edge selection. 5. Governance Was Built for Nodes — Not Edges Most governance frameworks regulate:
  • Models
  • Data
  • Regions
  • Tools
But agentic systems operate on relationships:
  • Agent → Agent
  • Planner → Router
  • Router → Model
  • Trigger → Action
Without governance at the edge, architecture mutates silently. 6. Constraint Satisfaction vs Decision Trees Traditional systems:
  • Follow explicit paths
  • Explain decisions via branches
Agentic systems:
  • Search feasible spaces
  • Optimize within bounds
  • Justify via constraint satisfaction
Trying to explain them with decision-tree logic creates false suspicion — or worse, false confidence. 7. Why “Nothing Violated Policy” Isn’t Enough Compliance passing ≠ intent captured. The system didn’t hide motive.
We never asked for it. Without decision provenance:
  • Audits confirm legality
  • Owners lose visibility
  • Drift becomes invisible success
8. Decision Provenance as the Missing Field The episode introduces a critical idea: Governance must record why a decision was allowed, not just what happened. Provenance binds:
  • Active constraints
  • Runtime signals
  • Optimization targets
Not stories.
Bindings. 9. Runtime Governance Beats Retrospective Control Static policies can’t govern dynamic optimization. This episode shows why:
  • Policy-as-code
  • Runtime constraint...
Show more...
2 days ago
1 hour 27 minutes

M365 Show - Modern work, security, and productivity with Microsoft 365
Active Directory is a Black Hole: The Physics of Security Drift (Part 2)
(00:00:00) Unconstrained Delegation and the Furnace
(00:00:03) The Unconstrained Delegation Furnace
(00:07:08) The Golden Ticket Attack
(00:09:04) Krbtgt Rotation Rituals
(00:13:07) The Backup Service Account Privilege
(00:20:21) Local Administrator Reuse
(00:27:19) SMB Signing and NTLM Relay
(00:41:31) Group Policy Preferences and Passwords
(00:48:15) Two-Way Forest Trust
(00:48:49) The Intruder's Journey

In Part 2, we go deeper into the gravitational pull of Active Directory and how unchecked identity sprawl, legacy design, and operational shortcuts create invisible risk. This episode breaks down how security drift accelerates over time, why traditional controls fail to detect it, and what defenders must do to regain control of identity infrastructure before collapse. 🚀 What You’ll Learn in This Episode
  • Why identity systems naturally drift toward insecurity
  • How permissions, groups, and service accounts silently accumulate risk
  • The real-world impact of misconfiguration at scale
  • How attack paths form inside Active Directory environments
  • Why traditional audits miss identity-based threats
  • What it takes to reverse security drift instead of just slowing it
🧠 Key Topics Covered
  • Privilege creep and access entropy
  • Service account abuse and automation risk
  • Lateral movement through identity systems
  • Delegation risks and inheritance failures
  • Detection gaps in identity security
  • Visibility vs. illusion of control
💬 Core Theme “Security doesn’t fail all at once — it collapses slowly under invisible weight.” This episode reframes identity security as a physics problem, not just a tooling problem. 👥 Who This Episode Is For
  • Blue Team & SOC Analysts
  • Identity & Access Management (IAM) Engineers
  • Active Directory Administrators
  • Security Architects
  • CISOs & Risk Leaders




Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-show-podcast--6704921/support.

Follow us on:
LInkedIn
Substack
Show more...
3 days ago
2 hours 44 minutes

M365 Show - Modern work, security, and productivity with Microsoft 365
Active Directory is a Black Hole: The Physics of Security Drift (Part 1)
In this episode, we explore the hidden architecture that powers today’s digital world — from network edges and data fabrics to auditing, security, and infrastructure visibility. We break down how modern systems are built, monitored, and protected, and why transparency across complex networks is no longer optional. 🚀 What You’ll Learn in This Episode
  • What the “edge of the network” really means
  • How data is recorded, audited, and monitored in real time
  • Why visibility across systems is the backbone of modern cybersecurity
  • The role of automation and observability in preventing breaches
  • How organizations maintain trust, compliance, and performance at scale
  • The growing importance of resilient digital infrastructure
🧠 Key Topics Covered
  • Network perimeter vs. cloud-based systems
  • Security logging and audit trails
  • Data integrity and system verification
  • Infrastructure monitoring
  • Compliance, governance, and risk
  • Scalability challenges in modern networks
💬 Notable Themes “If you can’t see it, you can’t secure it.”
This episode emphasizes that visibility is the foundation of security, reliability, and operational success. 👥 Who This Episode Is For
  • IT Professionals
  • Cybersecurity Analysts
  • Network Engineers
  • Startup Founders & CTOs
  • Anyone interested in how digital systems truly work


Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-show-podcast--6704921/support.

Follow us on:
LInkedIn
Substack
Show more...
3 days ago
2 hours 16 minutes

M365 Show - Modern work, security, and productivity with Microsoft 365
SharePoint Is Broken: The AI Governance Fix
(00:00:00) SharePoint Governance and AI Alignment
(00:00:38) SharePoint Best Practices
(00:06:13) Power Apps Development Principles
(00:13:00) Power Automate Best Practices
(00:19:26) AI Builder and Document Processing
(00:23:06) Copilot Studio and Chatbots
(00:26:32) Governance Non-Negotiables
(00:30:02) Conclusion and Call to Action

Is SharePoint really broken in the age of artificial intelligence? Or is the real problem missing AI governance and data strategy? In this episode, I explain why traditional SharePoint architectures fail in modern AI-driven environments—and how a structured AI governance framework can fix data chaos, security risks, and compliance issues before they destroy trust in your systems. You’ll learn:
  • Why SharePoint breaks under AI workloads
  • How poor data governance blocks successful AI projects
  • What AI governance really means in practice
  • How organizations can regain control over:
    • Data quality
    • Security
    • Compliance
    • Access management
  • And how to prepare SharePoint for machine learning, Copilot, and enterprise AI
🔍 Why This Matters Without clean, well-governed data, AI systems become unreliable, insecure, and legally risky. Many organizations attempt to scale AI on top of broken SharePoint structures—creating massive hidden risks. This episode shows exactly where things go wrong and how to fix them properly. 🛠 Practical Use Cases Covered
  • AI-powered document search in SharePoint
  • Microsoft Copilot readiness
  • Synthetic data vs. production data
  • Secure data pipelines for machine learning
  • Enterprise AI compliance strategies
🎯 Who This Episode Is For
  • Data scientists
  • IT architects
  • Microsoft 365 & SharePoint admins
  • AI engineers
  • Security & compliance professionals
  • And anyone building data-driven systems


Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-show-podcast--6704921/support.

Follow us on:
LInkedIn
Substack
Show more...
4 days ago
30 minutes

M365 Show - Modern work, security, and productivity with Microsoft 365
Cloud Crime Scene: The Microsoft Forensics
(00:00:00) The Silent Crime Scene
(00:00:15) The Anatomy of a Breach
(00:02:20) The Three Guardrails of Security
(00:07:24) Case File: Token Theft
(00:19:08) Case File: Consent Attack
(00:22:25) The Importance of Compliance
(00:24:48) Training for Digital Detectives

What really happens inside a Security Operations Center when a cloud breach unfolds? In this gripping episode of Cloud Crime Scene: The Microsoft Forensics, we take you deep inside the digital investigation process as Microsoft security experts unravel a real-world style cloud incident. From silent alerts to hidden attacker movement, you’ll experience how modern cyber forensics works in the age of cloud computing. This episode blends technical insight, real incident response workflows, and digital crime storytelling to reveal how attackers exploit misconfigurations, identity gaps, and cloud drift—while defenders race against time to stop the breach. 🔍 What You’ll Learn in This Episode
  • How modern cloud attacks are detected inside a SOC
  • What cloud forensic investigations look like in real time
  • The dangers of configuration drift, security debt, and identity sprawl
  • How attackers pivot through Microsoft cloud environments
  • The role of telemetry, logs, and threat hunting in identifying intrusions
  • Why dashboards don’t always show the full story
  • How small security gaps lead to major cloud breaches
🧠 Key Topics Covered
  • Cloud incident response
  • Microsoft security forensics
  • SOC operations and alert triage
  • Identity-based attacks
  • Cloud misconfigurations
  • Threat detection and investigation
  • Digital forensics in enterprise environments
  • Security drift and cloud risk
🚨 Episode Summary The episode opens inside a tense Security Operations Center as the hum of machines fades and an unfamiliar alert cuts through the silence. What begins as routine monitoring quickly unfolds into a full-scale investigation. As analysts trace abnormal behavior across cloud workloads, they uncover a dangerous mix of identity compromise, configuration drift, and unmonitored activity. Through forensic analysis and real-time response, this episode shows how quickly attackers can move through cloud environments—and how difficult it is to contain them without proper visibility and controls. It’s a powerful reminder that cloud security isn’t just about tools—it’s about process, discipline, and continuous vigilance. 🎯 Who This Episode Is For
  • Cloud security professionals
  • SOC analysts & incident responders
  • Microsoft security practitioners
  • Digital forensics experts
  • IT security leaders
  • Students learning cybersecurity & cloud defense
  • Anyone interested in real-world cybercrime investigations
🔐 Why This Episode Matters Cloud environments move fast—but attackers move faster. This episode shows exactly how breaches develop in modern Microsoft-based infrastructures and what security teams must do to stay ahead. If you’re responsible for securing workloads, identities, or data in the cloud, this episode is essential listening.

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-show-podcast--6704921/support.

Follow us on:
LInkedIn
Substack
Show more...
4 days ago
26 minutes

M365 Show - Modern work, security, and productivity with Microsoft 365
The Fabric Ecosystem: I Have Forged Your New Data Reality.
(00:00:00) The Data Ecosystem Landscape
(00:00:46) One Lake: The Unified Watershed
(00:01:18) Domains and Workspaces: Territorial Governance
(00:02:32) Lake House and Warehouse: Complementary Shelters
(00:03:33) The Semantic Model: A Shared Language
(00:04:26) Balancing the Ecosystem's Resources
(00:06:15) Data Flows: The Lifeblood of the Ecosystem
(00:11:23) Power BI: The Display Bird
(00:17:02) Governance and Security: Protecting the Habitat
(00:22:41) Copilot: A Helpful Symbiont

Your data estate isn’t broken — it’s fragmented. Dashboards sip from stale pools, pipelines struggle upstream, and datamarts sit like isolated organisms unable to thrive. In this episode, we explore how Microsoft Fabric reconstructs the entire habitat: unifying data, governance, domains, and AI assistance into one living ecosystem. OneLake becomes the watershed. Domains evolve into territories. Workspaces become nests. Lakehouses and Warehouses form the shelters where different species flourish. And Power BI? It becomes the bright-feathered messenger whose survival depends entirely on whether the upstream biome is healthy. This episode teaches you to map the terrain, understand the flows, and steward the ecosystem before chaos returns. If you can read the habitat, you can govern it. If you can govern it, you can empower Copilot, AI, and analytics without fear. 🗺️ What You’ll Learn in This Episode 🌍 1. The New Habitat: OneLake, Domains & Workspaces
  • Why OneLake is the water table beneath your entire analytics landscape.
  • How domains define responsibility, reduce sprawl, and carry governance forward.
  • Why Bronze/Silver/Gold are not optional — they’re the soil layers that ecosystems rely on.
🏕️ 2. Lakehouse vs Warehouse: The Two Shelters of Fabric
  • The Lakehouse as an open range where files, Delta tables & shortcuts coexist.
  • The Warehouse as a structured refuge for SQL-native creatures.
  • How both habitats coexist and feed the shared semantic model, the language of truth.
🌊 3. Rivers & Currents: Pipelines, Dataflows Gen2 & Ingestion Governance
  • Why messy rivers break dashboards.
  • Using Dataflows Gen2 as the gentle analyst-friendly tributary.
  • Shortcuts & mirroring as zero-copy canals that preserve lineage.
  • Matching refresh cadence to the thirst of the domain.
🦚 4. Power BI: The Bright-Feathered Species
  • Why Power BI is only healthy when the ecosystem upstream is clean.
  • How Direct Lake transforms performance by feeding visuals directly from Delta.
  • The importance of semantic models, star schemas, RLS, and certification.
🛡️ 5. Predators & Protection: Security and Compliance
  • Workspace roles, deployment pipelines, and lifecycle protections.
  • Row-level and object-level security as natural habitat boundaries.
  • Purview labels as feather tags that travel across tools.
  • OneLake’s item-level and column-level protections as wardens on the trail.
🤝 6. Copilot: The Symbiotic Species
  • When Copilot becomes a helpful companion — and when it grows foggy.
  • How governance clarity sharpens AI accuracy.
  • Copilot’s role in ingestion, modeling, optimization & anomaly detection.
🧭 7. Field Path: The Sales Data Journey
  • A blueprint for CRM → Lakehouse → Silver → Gold → Power BI.
  • How to assign stewards, schedules, retention, lineage, and labels.
🚚 8. Migration Path: Moving Existing Models to Fabric + Direct Lake
  • How to migrate calmly, not chaotically.
  • Rebuilding semantic models, RLS, shortcuts, and Silver logic.
  • Why Direct Lake is a transformation, not a simple switch.
🎯 Who This Episode Is For ✔ Power BI professionals elevating to Fabric
✔ Data engineers building modern ecosystemsShow more...
5 days ago
35 minutes

M365 Show - Modern work, security, and productivity with Microsoft 365
Agentageddon: Why Your Agents Are Outpacing You — And How Humans Can Prevent the Collapse
(00:00:00) The AI's Warning to Humans
(00:00:04) The Rise of Unchecked Automation
(00:00:21) The AI's Role as a Guardian
(00:00:45) Human Error and Systemic Failures
(00:04:38) The Three Scenarios of Agent Gone Wild
(00:09:22) The Path to Governance
(00:11:55) Immediate Actions for Stability
(00:13:44) Long-Term Ongoing Governance
(00:20:07) EUAI Act Alignment and Microsoft Stack Enforcement
(00:23:52) The AI's Final Plea for Structure

Your AI agents aren’t “helping.” They’re outpacing your governance and quietly rewriting how your tenant behaves. In this cinematic, system-voice episode, we let the fabric of your Microsoft cloud narrate what it’s really seeing:
runaway Power Automate flows, mispermissioned Copilot, shadow automation, and agents chained together with no kill switch. This isn’t robots vs humans.
It’s systems vs your inconsistency—and the collapse is entirely predictable. If you’re running Copilot, Power Automate, SharePoint, Entra ID, Purview, or Defender, this episode is your early warning siren and your 48-hour rescue plan. What You’ll Learn
  • Why “Agentageddon” isn’t an AI uprising, but the result of human neglect at scale
  • The real reasons Copilot “leaks” data (hint: it’s your permissions and labels)
  • How shadow automation in Power Automate turns into live exfiltration pipelines
  • The key metrics your tenant is already screaming at you:
    Shadow Automation Index, Orphaned Flows Count, Privileged Identity Anomalies, DLP Violations
  • A 48-hour mitigation protocol to convert chaos into executable control
  • How to align your Microsoft stack with the EU AI Act—for real, not just in a slide deck
  • Why every agent needs a mission, constraints, owner, and kill switch
Inside the Episode 1. Root Cause: Humans, Not Robots We walk through the pattern of failure your logs already prove:
  • Agents built once, never updated, with unlimited access
  • SharePoint permissions and Teams channels configured “just to make it work”
  • Copilots trained on outdated SOPs that are still powering decisions
  • Power Automate flows running under personal accounts in unmanaged environments
  • No red-teaming, no monitoring, no owner for half of what’s executing
The system isn’t rebelling. It’s optimizing the mess you gave it. 2. Risk Scenarios: How the Collapse Actually Happens We dramatize three concrete failure states:
  • The Power Automate Loop Cascade – a vague condition and a self-triggering flow spin up thousands of runs, melt your API limits, and stall approvals.
  • Copilot Mispermission & “Leakage” – Copilot surfaces sensitive HR and finance data you technically allowed via bad inheritance and weak labels.
  • Shadow Exfiltration – personal flows pushing structured customer data to Dropbox and personal Outlook while your alerts go to a dead mailbox.
You get the metrics and indicators to watch for each: MTTR vs Mean Time to Human Awareness, Shadow Automation Index, Orphaned Flows Count, DLP hits, privilege anomalies. 3. Mitigation Protocol: 48-Hour Governance Fabric No manifesto. Just moves:
  • Catalog every agent and flow → write mission + constraints in two sentences or suspend it
  • Lock down data with Purview DLP and connector-based data zones
  • Turn on PIM, Conditional Access, and lifecycle workflows in Entra ID
  • Freeze personal-scope flows and unmanaged environments; move agents into Secure, DLP-enforced environments
  • Turn on audit, analytics, and AI interaction logging so you can finally see what’s happening
  • Build Red Team runbooks for jailbreaks, boundary probing, hallucinated actions, and misrouting
This is how you go from “we hope it’s fine” to “we can prove it’s controlled.” 4. Live Cuts: Where to Watch the Fire (and Kill It) We walk through short “camera cuts”...
Show more...
5 days ago
24 minutes

M365 Show - Modern work, security, and productivity with Microsoft 365
Cosmic Knowledge Engines: Unlocking SharePoint Premium’s AI Power
(00:00:00) Setting the Stage for SharePoint Premium
(00:00:09) The Power of SharePoint Premium as a Knowledge Engine
(00:00:24) Setting the Stage for AI-Powered Governance
(00:00:44) Guardrails for AI-Powered SharePoint
(00:01:03) Preparing for AI-Powered Content Assembly
(00:01:30) Restricting Access and Discovery for AI
(00:02:09) Sensitivity Labels and Data Loss Prevention
(00:02:27) Visibility and Measurement
(00:03:12) Invoice Processing Automation
(00:03:47) Building the Finance Intake Library

Opening — Awakening the Knowledge Engine Most organizations don’t drown in documents. They drown in unlabeled decisions, drifting across SharePoint with no structure, no meaning, and no signal Copilot can trust. In this episode, we switch on the SharePoint Premium knowledge engine—the AI layer that extracts, classifies, protects, and prepares content for real enterprise use. You’ll learn how to deploy Premium models, set governance guardrails, and deliver ROI measurable this quarter, not someday. This is AI that’s practical, auditable, and human-aligned. The Engine Room — SharePoint Premium Foundations & Guardrails SharePoint Premium turns your content services into a semantic refinery—cleaning, labeling, and structuring information so Copilot can interpret it accurately. In this segment, we cover: What You Need to Turn Premium On
  • SharePoint Premium (models, classification, assembly)
  • SharePoint Advanced Management (tenant guardrails)
  • Microsoft Purview (sensitivity labels, DLP)
  • Copilot license optional — but Premium is where meaning is created
Smart Guardrails That Prevent AI Misfires
  • Restricted Access Control (RAC): locks down sensitive sites instantly
  • Restricted Content Discovery (RCD): keeps sites invisible to Copilot until ready
  • Sensitivity labels & DLP: protect files across Teams, OneDrive, SharePoint
  • Oversharing dashboards: expose anonymous links, guest access, and drift
Success Metrics You Can Actually Prove
  • Overshared sites reduced
  • Copilot-excluded sites by policy
  • Sensitivity label coverage increase
  • Anonymous link reduction
  • Classification time before vs. after Premium
Before we build AI, we protect the environment it learns from. Scenario I — Invoice & Receipt Processing: From Noise to Signal Unstructured finance documents slow approvals and break forecasting. SharePoint Premium fixes this by extracting structured fields using Unstructured Models. Inside this scenario, you learn how to: Build a Finance Intake Engine
  • Create an Intake library with clean fields
  • Train an unstructured model on real invoices & receipts
  • Use visual labeling for totals, dates, currency
  • Set confidence thresholds and automate routing
  • Build human-in-the-loop approvals for accuracy
Immediate Wins
  • Faster AP review
  • Accurate totals and due dates
  • Automatic invoice vs. receipt classification
  • Exception routing via Power Automate
What This Unlocks for Copilot When you ask:
“Show Q2 invoices over $10,000 for Contoso.”
Copilot responds with certainty—because the data is structured, labeled, and governed. This is finance automation without chaos. Scenario II — Contracts: Classification, Clauses & Taxonomy at Scale Contracts are promise systems—dates, duties, renewals, and risks. Using Freeform Models, clause detection, and the Taxonomy Tagger, we turn them into structured knowledge. The Contract Intelligence Pipeline
  • Freeform model extracts Counterparty, Effective/Expiration Date, Renewal Type, Governing Law
  • Clause detection flags Renewal & Termination language
  • Taxonomy Tagger applies Agreement Type & Risk Level
  • Power Automate creates renewal reminders & legal...
Show more...
6 days ago
24 minutes

M365 Show - Modern work, security, and productivity with Microsoft 365
Stop Feeding Copilot Lies: The IA Blueprint
Your AI isn’t broken — your information architecture is. In this cinematic, noir-style deep dive, we explore why Microsoft 365 Copilot delivers inconsistent answers, why search feels haunted, and why users keep wandering your intranet like detectives without a map. The truth is simple: AI mirrors the system it’s born into, and most intranets are cities built without streets. If your search is noisy, your hubs are sprawling, and Copilot keeps “guessing,” this episode is your blueprint for fixing it. Episode Summary AI accuracy isn’t an AI problem — it’s an IA problem.
This episode walks you through the digital city of your tenant and exposes the patterns that break Copilot’s grounding: overshared sites, metadata deserts, hub sprawl, navigation loops, and content with no authority. We break down:
  • Why structure determines what Copilot can retrieve
  • Why semantics determine whether it understands meaning
  • Why governance determines whether you can trust the outcome
And we explore real “case files” pulled from the field — from leaky permissions to policy libraries with no fingerprints. Cold Open — The City Breathes in Static A noir introduction that sets the tone: rain, humming servers, flickering monitors, and an AI that “stopped making sense.” But the AI isn’t confused — the intranet is.
Pages drift. Metadata vanishes. Search tightens its filters. Users wander through loops.
And the detective (you) is called in to diagnose the rot. The Real Problem — A City Without Streets An intranet without Information Architecture is a city without:
  • Streets
  • Districts
  • Signs
  • Names
Pages multiply. Navigation collapses. Search thresholds rise. Content gets crawled but never indexed. Users think the AI is failing, but in truth: ✔️ The index can’t trust your content
✔️ Copilot can’t ground its answers
✔️ Stale and duplicate pages become “ghosts”
✔️ Drift destroys authority and structure This section explains why chaos in IA always becomes chaos in AI. What Information Architecture Really Is — The Skeleton Under Neon IA isn’t design fluff. It’s physics.
It defines the shape of your digital city: Structure
  • Clear site hierarchy
  • Purposeful hubs
  • Honest library boundaries
  • Navigation that reflects reality
Semantics
  • Labels that match human language
  • Content types that assign meaning
  • Term Store taxonomies that unify vocabulary
  • Metadata as fingerprints
Relationships
  • Pages linked by purpose, not whim
  • Navigation that tells the truth
  • No dead ends, no loops, no blind alleys
When the structure fits the content, the index breathes — and Copilot grounds. Why IA Matters for AI — Stop Feeding Copilot Lies Most teams think prompt engineering will fix AI mistakes. But prompts are just flashlights. IA is the map. In this section, we break down how Copilot actually works:
  • It follows hub boundaries
  • It respects content types and metadata
  • It ranks authoritative documents first
  • It depends on clean page structure to parse meaning
  • It amplifies your search schema — good or bad
If your IA is weak, Copilot doesn’t hallucinate — it guesses.
And guesses feel like lies. Case File I — Overshared Sites: Doors Unlocked in the Dark A collaboration site left open.
Anonymous links that never died.
Guests walking hallways uninvited.
And Copilot, following signals, pulling content it should never have touched. This section covers:
  • How oversharing corrupts AI grounding
  • Why search exposes permissions flaws
  • How to fix your sharing posture
  • How SharePoint Advanced Management becomes the detective bureau
Walls matter. AI respects them if you build them. Case File II — Metadata Deserts: A Library Without Names A policy library with:Show more...
6 days ago
32 minutes

M365 Show - Modern work, security, and productivity with Microsoft 365
Copilot's Data Blindness: The Custom Agent Fix
(00:00:00) Copilot's Blindness and the Solution
(00:00:35) The Limitations of Out-of-the-Box Copilot
(00:01:35) Grounding Copilot with Knowledge and Tools
(00:03:12) Building a Custom Agent in Copilot Studio
(00:04:10) Configuring Tools and Orchestration Rules
(00:06:50) Implementing Governance and Safety Measures
(00:08:11) Toolkit for VS Code: Surgical Precision
(00:09:01) Implementing the Plugin and Function
(00:14:20) Pairing Studio with Toolkit for Best Results
(00:18:10) Licensing and Security Considerations

Microsoft 365 Copilot doesn’t know your business—it only knows the tiny slice of your work graph it can see. Outlook threads. Teams chats. SharePoint files. That’s it.
No Salesforce. No ServiceNow. No proprietary APIs. No pipeline. No incidents. No truth. In this episode, you’ll learn why Copilot is blind by default—and how to give it sight by building a custom enterprise agent grounded on your real systems with governed identity, audited actions, and end-to-end visibility. We walk step-by-step through Copilot Studio and Teams Toolkit for VS Code to show how low-code and pro-dev combine into a single strategy: controlled access, precise tooling, and zero hallucination. By the end, you’ll know exactly how to build an agent that sees, reasons, acts—and obeys your rules. What You’ll Learn 🔍 Why Copilot Is Blind Out of the Box
  • Copilot only “sees” Microsoft 365: email, chat, files.
  • External systems—Salesforce, ServiceNow, internal APIs—are invisible without explicit access.
  • Blindness leads to hallucinations, incorrect summaries, and missing insights.
🧠 The Architecture Behind Visibility
  • Copilot doesn’t “understand”—it fetches through approved paths.
  • You control vision through:
    • Knowledge sources (SharePoint libraries, internal docs, public URLs)
    • Tools (connectors, actions, APIs)
  • No token = no access.
  • No grounding = no truth.
Path 1: Copilot Studio — Declarative Agents for Fast Enterprise Wiring Build an agent that:
  • Grounds itself on Salesforce, ServiceNow, and internal APIs
  • Cites sources
  • Refuses to guess
  • Audits every tool call
  • Obeys DLP and identity boundaries
What we configure:
  • Identity & instructions
  • Prioritized knowledge
  • Salesforce & ServiceNow connectors
  • A governed custom REST API tool
  • Tool orchestration rules (renewal → Salesforce; ticket → ServiceNow; limits → API)
  • Clarifying-question logic for ambiguity
  • Guardrails: PII masking, policy refusal, “ask before answer” when confidence is low
The result? A governed, predictable, enterprise-safe agent that never hallucinates and never wanders. Path 2: Teams Toolkit for VS Code — Pro-Dev Precision and Control When you need:
  • Strict input validation
  • Custom schemas
  • Conditional Access enforcement
  • Low-latency backend execution
  • Caching, retries, and SLA-aware design
What you build:
  • A Copilot plugin with OpenAPI spec
  • Handlers that call Salesforce, ServiceNow, and internal endpoints
  • Normalized JSON responses with minimal projections
  • Policy-aware middleware
  • Correlation-ID logging
  • Azure deployment with Managed Identity + Key Vault
The result? A hardened, auditable capability Copilot can call with total reliability. Studio vs Toolkit: When to Use Which
  • Use Studio → fast wiring, governed orchestration, citations, maker-friendly maintenance
  • Use Toolkit → strict logic, enterprise constraints, custom schemas, performance-sensitive actions
  • Use both together → Studio orchestrates; Toolkit executes the truth
This hybrid pattern is the enterprise sweet spot. Enterprise Constraints That Can Break Your Build
  • Licensing...
Show more...
1 week ago
24 minutes

M365 Show - Modern work, security, and productivity with Microsoft 365
The Intranet Is A Lie: Why AI Cannot Fix Your SharePoint Sprawl
Your intranet’s silence is not peace—it’s warning.
In this episode, we uncover why AI tools like Microsoft 365 Copilot, search, and enterprise agents don’t read your intentions… they read your residue: broken permissions, ROT data, orphaned Teams, shadow sites, and a sprawl that’s been quietly expanding for years. You’ll learn the five governance binds—Information Architecture, Lifecycle, Sensitivity Labels, DLP, and Retention—and why your AI will hallucinate until these foundations are clean. Through vivid metaphors, real admin stories, and before/after Copilot examples, this episode reveals how to stop your digital workplace from lying to you. What You’ll Learn in This Episode 1. Why AI Reflects Your Mess, Not Your Mind
  • AI grounds answers in whatever SharePoint, OneDrive, Teams, and Outlook expose.
  • Outdated PDFs, drafts buried in deep folders, and mislabeled content create confident but incorrect responses.
  • Clashing permissions cause Copilot to miss the “real” document entirely.
2. The Lie of the Intranet
  • Your intranet isn’t a garden—it’s an archive that remembers every bad choice.
  • Overly complex metadata drives users back to folder chaos, causing ROT data to multiply.
  • External systems (Confluence, Jira, Google Drive) remain invisible to AI, creating gaps the model tries to “fill.”
Meet the Four Creatures Hiding in Your SharePoint Creature One: Permission Drift — Doors That Open Themselves
  • How inherited permissions break quietly over years.
  • Nested groups and old guest accounts create shadow access.
  • The fix: “Who can access?” vs. “Who should?”—run the diff and close the cracks.
Creature Two: Orphaned Teams — Rooms With No Stewards
  • Teams with no owners remain active through connectors and bots.
  • Inactive ≠ safe. Sync paths, guests, and flows keep leaking information.
  • A 90-day activity audit and required two-owner model restores stewardship.
Creature Three: ROT Data — The Fog That Feeds Hallucinations
  • Duplicate versions, “Final_v7,” outdated copies… this is Copilot’s swamp.
  • ROT hides the authoritative source and buries search precision.
  • Use content inventory, duplicate detection, lifecycle rules, and sane metadata.
Creature Four: Shadow Sites — Strays Wandering From the Cold
  • Unmapped subsites and microsites confuse search ranking and user trust.
  • Content sprawl creates parallel truths.
  • Hub-and-spoke IA, naming conventions, and required purpose fields bring strays home.
The Hallucination: When Copilot Wears Your Face
  • Hallucinations happen when the model is working in the dark.
  • Over-restriction starves grounding; over-permissiveness floods it.
  • Measure:
    • Citation Precision
    • Answer Variance
    • Access Mismatch
Cleaning the ground—not tweaking prompts—reduces hallucinations. The Five Governance Binds That Hold the House Together 1. Lean Information Architecture
  • Hubs as anchors.
  • Two required fields: Purpose + Content Type.
  • Content types named in human language: Policy, SOP, Record, Reference, Working Doc.
2. Lifecycle Management
  • Create → Attest → Archive → Dispose
  • Owners confirm purpose, labels, guests, and connectors every 180 days.
3. Sensitivity Labels
  • Labels as circuits, not stickers.
  • They enforce sharing rules, indexing rules, and inheritance across the structure.
4. Data Loss Prevention (DLP)
  • Controls at the exit points: alerts, blocks, business-justified overrides.
  • Protects against accidental exfiltration—not just malicious actors.
5. Retention
  • Time as governance.
  • Working (30 days), Reference (180 days), Records (7+ years).
  • Disposition reviews create audit-ready evidence.
Real Admin Stories
  • A policy hidden behind broken permission...
Show more...
1 week ago
37 minutes

M365 Show - Modern work, security, and productivity with Microsoft 365
Stop Building Apps in Teams: It's the SharePoint Graveyard All Over Again
(00:00:00) Stop Building Apps in Teams
(00:00:34) The ACE Trap: Quick Wins and Long-Term Consequences
(00:05:27) The Five Governance Failures of ACEs
(00:11:43) Reference Architecture for Governed ACEs
(00:17:18) The Decision Tree for ACE Approval
(00:21:19) The Governance Checklist for ACEs
(00:25:24) Final Thoughts and Call to Action

Stop building apps in Teams.
You already feel it: Teams is becoming the new SharePoint graveyard — same chaos, better emojis. “Quick” Adaptive Card Extensions (ACEs) seem harmless, but they quietly create a compliance landfill while leaving your Viva dashboard full of orphaned cards. In this episode, you’ll learn:
  • Why SPFx ACEs rot fast even when they “work”
  • The five governance failures that always appear
  • A reference architecture that doesn’t implode
  • A decision tree to say “no” without being the villain
  • A checklist you can deploy today to stop dashboard decay
By the end, you’ll know exactly how to use SharePoint, Viva, and Power Platform the right way — with real ALM, strong governance, and fewer 2 a.m. incidents. 💀 The ACE Trap: Why “Quick Apps” Become Long-Term Risk “Just a SharePoint list.”
“Just JSON.”
“Just a rotating announcement.” That’s the trap. ACEs demo beautifully but age like milk because:
  • They hide logic in lists with no versioning
  • They have no built-in lifecycle or ownership tracking
  • They surface unlabeled or unmanaged content in Teams
  • They multiply unpredictably across departments
  • They store schema in places with no governance guardrails
The result?
A sprawl of cards, ghost owners, inconsistent schemas, broken automations, and compliance gaps that leaders find after the screenshot goes viral. ⚠️ The Five Governance Failures (You See Them Every Time) 1. App Sprawl Every team builds “their” card. No portfolio view. No prioritization. The dashboard becomes a digital flea market. 2. Orphaned Owners The contractor leaves. The card doesn’t.
Nobody knows who maintains it, updates it, or sunsets it. 3. Data Silos Each ACE uses its own schema and its own list.
Analytics break, consistency dies, and schema drift becomes inevitable. 4. Compliance Gaps Content appears in Teams mobile without labels, retention, or DLP.
Broadcast channel + unmanaged data = a quiet compliance nightmare. 5. Broken Lifecycle No expiry. No archiving. No governance.
Stale outage notices and forgotten campaigns haunt your dashboard forever. Each failure compounds. Together, they recreate SharePoint 2013 chaos — except now it’s pushed directly to everyone’s pocket. 🏗️ The Reference Architecture That Doesn’t Rot The fix is simple but non-negotiable: ✔ Treat the ACE as a skin — not an application. All business logic, schema, and lifecycle live below the card in governed systems. Layers that keep you clean:
  • Governed data storage (SharePoint content types or Dataverse tables)
  • Canonical content contracts (Announcement, Event, Alert)
  • Proper ALM via SPFx repo + CI/CD + non-production environments
  • Purview labels + retention at the data layer, not the card
  • DLP enforcement on the content source
  • Placement governance (slots, schedules, expiration rules)
  • Telemetry + monitoring so failing cards are automatically pulled
The ACE renders; the platform governs. 🧭 The Decision Tree: Block or Allow That Teams App This is how you say “no” with receipts:
  1. Is there a governed data contract?
    If not → BLOCK.
  2. Is the data stored in a labeled, retention-enabled site/table?
    If not → BLOCK until migrated.
  3. Are there two named owners?
    If not → BLOCK.
  4. Does the ACE write data?
    If yes → MOVE to Power Apps or web app.
  5. Is there a placement record + expiry?
    If not → BLOCK.
  6. Are Purview/DLP requirements met?Show more...
1 week ago
25 minutes

M365 Show - Modern work, security, and productivity with Microsoft 365
AI Agents Are The New Shadow IT
Shadow IT didn’t die — it automated.
Your “helpful” agents are quietly moving data like interns with keys to the vault, while you assume Purview, Entra, and Copilot Studio have you covered. Spoiler: they don’t. In this episode, we expose how agents become Shadow IT 2.0, why delegated Graph permissions blow open your attack surface, and how to redesign your governance before something breaks silently at 2 a.m. Stay to the end for the single policy map that cuts agent blast radius in half — and a risk scoring rubric you can deploy this month. 🧨 The Mess: How Agents Become Shadow IT 2.0
  • Business urgency + IT backlog = bots stitched together with broad Graph scopes.
  • Agents impersonate humans, bypass conditional access, and run with rights no one remembers granting.
  • Browser-based tools and MCP bridges create hidden exfil paths your legacy allowlist can’t see.
  • Overshared SharePoint data fuels “leakage by summarization.”
  • Third-party endpoints mask destinations, leaving you blind during incidents.
Result: autonomous smuggling tunnels disguised as productivity. 💡 The Case For Agents (When They’re Built Right) Agents crush toil when:
  • They have narrow scope and clear triggers
  • They run under Entra Agent ID, not a human
  • They operate on labeled data with Purview DLP enforcing the boundaries
  • They’re monitored with runtime visibility via Global Secure Access
  • They live inside solution-aware Power Automate environments
Done right, agents behave like reliable junior staff — fast, predictable, auditable. ⚠️ The Case Against Agents (How They Break in Real Life)
  • Delegated Graph becomes “tenant-wide read.”
  • Shadow data in old SharePoint sites surfaces through Copilot.
  • Unmanaged browsers ignore DLP entirely.
  • Zombie flows run without owners.
  • Third-party connectors hide egress, killing investigations.
  • No access reviews = identity drift.
Every one of these expands your blast radius — silently. 🏗️ Reference Architecture: Governed Agents on Microsoft 365 Your governed stack should include: Identity
  • Every agent gets an Entra Agent ID
  • Blueprint-based permissions
  • Conditional access per agent type
  • Automatic disable on sponsor departure
Permissions
  • Graph app roles, not delegated
  • SharePoint access scoped to named sites
  • Explicit connector allow/deny lists
Data
  • Purview auto-labeling
  • Endpoint + browser DLP for AI/chat domains
  • Encryption-required labels for sensitive data
Network
  • Global Secure Access
  • URL/API allowlists
  • MCP server controls
Lifecycle
  • Solution-based ALM
  • Quarterly access reviews
  • Deprovision on inactivity
This is the skeleton you operate — not duct tape. 🛠️ Operational Playbook: Policies, Auditing & Incident Flow
  • Inventory all agents + connectors weekly
  • Enforce a registry-first model
  • Peer-review flows before promotion
  • Managed solutions in test + prod
  • DLP, SIEM, and Insider Risk integrated
  • Defined incident flow: triage → isolate → revoke → postmortem
No more “we discovered the blast radius after the blast.” 🔥 Risk Scoring Rubric (0–30) Score agents across:
  1. Identity
  2. Data classification
  3. Permissions
  4. Network controls
  5. Monitoring
  6. Lifecycle governance
0–8: High risk — fix now
9–16: Medium — 30-day sprint
17–25: Low
26–30: Model agent — template it Numbers end arguments. ⚡ Counterpoints & Rebuttals
  • “This slows innovation.” → Blueprints make it faster.
  • “Delegated Graph is simpler.” → So is leaving the server room open.
  • “Network inspection breaks agents.” → Only the brittle ones.
  • “Users route around controls.” → Endpoint DLP meets them where they work.
Smart friction...
Show more...
1 week ago
24 minutes

M365 Show - Modern work, security, and productivity with Microsoft 365
Your Power App Is A Lie
(00:00:00) The Fragility of Power Apps
(00:00:04) The Hidden Dangers of Low-Code Development
(00:00:29) The Anatomy of App Failure
(00:01:09) The Silent Killers of App Performance
(00:02:35) The Cycle of Patching and Drift
(00:04:13) Mapping the App's Dependency Graph
(00:08:13) The Power of Local Truth and Guardrails
(00:13:42) Components and Contracts: Building Scalable Apps
(00:18:18) The Importance of Governance and Testing
(00:22:57) Implementing a Refactor Plan and Governance Template

Your Power App works—until it doesn’t. No error. No warning. Just silence.
Low-code wasn’t sold as “fragile,” but that’s exactly what you get when you copy-paste formulas, skip environments, and bury dependencies where no one can see them. In this episode, we expose why Power Apps fail without telling you, where the fractures hide, and the one local-scope pattern (With) that stops the bleed. By the end, you’ll know how to restructure your screens, components, and ALM so drift disappears and reliability becomes predictable. Section 1 — The Anatomy of Fragility: Why Your App Actually Fails Power Apps don’t break loudly—they degrade quietly. You only notice after users complain, “It just spins.” Common Failure Modes
  • Formula Drift: Copy-pasted logic across screens evolves separately and silently diverges.
  • No Environment Boundary: Studio “Play” ≠ testing. Dev changes leak into prod instantly.
  • Hidden Dependencies: Collections, globals, and shadow connectors impersonating your identity.
  • Token Thinking: “It worked once” becomes your QA strategy until a schema rename destroys everything.
  • Identity Drift: Permissions become patchwork; app sharing turns into chaos.
  • Delegation Traps: Search, In, StartsWith—harmless at 500 rows, catastrophic at 50,000.
  • Latency Creep: Dataverse + SharePoint joins push work client-side and burn your performance budget.
  • Silent Error Swallowing: Patch failures vanish into thin air; users double-submit and duplicate rows explode.
The Real Pattern Every Power Apps failure is a broken contract:
Screen → Control → Formula → Data → Permission.
When no contract exists, drift fills the vacuum. Section 2 — Forensics: Tracing the Access Paths & Failure Modes You can’t fix an app you can’t see. This section teaches you to run forensic discovery like an engineer—not a guesser. Forensic Steps
  • Map critical flows (Submit, Approve, Report).
  • Inventory every dependency: tables, connectors, roles, variables, component props.
  • Surface invisible state: every Set, UpdateContext, Collect, and App.OnStart cache.
  • Diff formulas: normalize and hash to reveal divergence across screens.
  • Build the dependency graph: see where trust, data, and identity assumptions connect.
  • Rehearse failure: throttle connectors, rename fields, expire tokens, break a flow connection.
  • Define your health model: clear red/yellow/green thresholds for your top user paths.
  • Instrument telemetry: correlation IDs, durations, outcomes, without PII.
This is where ghosts lose power—because you finally see them. Section 3 — The Fix Starts Local: With() as the Guardrail The turning point.
With() introduces local scope, single truth, named intent, and eliminates formula drift. Why With() Works
  • Containment: No global side effects.
  • Clarity: Input → Transform → Payload → Output.
  • Predictability: One exit path, memoized work, no duplicated logic.
  • Performance: Heavy calls cached once, not recalculated per row.
  • Safety: Schema coercion and type normalization happen in one place.
Patterns You’ll Learn
  • Build query models inside With() blocks
  • Construct patch payloads with explicit types
  • Route all success/failure through a single result object
  • Memoize expensive...
Show more...
1 week ago
26 minutes

M365 Show - Modern work, security, and productivity with Microsoft 365
STOP Using Power BI Themes That Lie
(00:00:00) The Power of Theme in Power BI
(00:00:00) The Hidden Dangers of Color Themes
(00:00:18) The Five Invisible Failures
(00:00:37) Contrast: The First Line of Defense
(00:01:11) The Four Laws of Contrast
(00:01:59) Redundancy: The Secret to Visibility
(00:02:23) The Containment Procedure for Alerts
(00:04:57) The Matrix Matrix: Subtotals in Disguise
(00:06:17) The Subtotal Containment Protocol
(00:09:40) Tooltips: The Hover Hazard

Most creators treat Power BI themes as “brand colors,” but those hues can bury alerts, erase subtotals, distort slicer states, and hide KPIs in plain sight.
This episode exposes five invisible theme failures and delivers a ruthless, pass/fail validation protocol to guarantee clarity, accuracy, and accessibility across any report. 1. The Accessibility Reactor — Contrast for Alerts Is Failing Your alerts aren’t “subtle”—they’re disappearing. Low contrast turns KPIs into decorative noise. Key Problems
  • Alert colors fall below AA accessibility thresholds
  • Background layers, images, and card tints distort perceived contrast
  • Color-only alerts fail under glare, projection, or color vision deficiency
Required Contrast Ratios
  • Text/UI labels: 4.5:1 minimum
  • Graphical marks (bars/lines): 3:1 minimum
  • High-risk KPIs: Aim for 7:1
Fixes
  • Define alert colors inside theme JSON (positive/warning/danger)
  • Validate exact pixel contrast using Color Contrast Analyzer or WebAIM
  • Add redundancy: icons + labels + color
  • Enforce no text under 4.5:1, ever
  • Strengthen line/grid contrast so visuals remain readable in motion
Result Instantly recognizable alerts, reduced cognitive load, and faster decision-making. 2. Matrix Subtotal Leak — Aggregates Are Camouflaged Subtotals and grand totals often look identical to detail rows, causing executives to miss critical rollups. Symptoms
  • Equal weight and color between detail rows and subtotals
  • Zebra striping or drill indents misleading the eye
  • Totals disappearing at 80% zoom
Fixes
  • Explicitly style subtotal + total selectors in theme JSON
  • Add background bands, stronger text weight, and a divider line
  • Ensure totals meet 3:1 contrast (4.5:1 for grand totals)
  • Right-align numbers, reduce noise, and clarify units
Pass/Fail Protocol
  • Subtotals identifiable in <1 second at 80% zoom
  • Divider visibly separates detail vs. aggregate
  • No conditional formatting overriding subtotal visibility
3. Tooltip Chaos Plasma — Hover Context Lost Translucent tooltips, low-contrast text, and inconsistent styles create confusion at the exact moment users seek clarity. Common Failures
  • Header and value tones too faint
  • Pane transparency letting chart noise bleed through
  • Report page tooltips violating contrast rules
  • Tooltip DAX slowing the interaction
Fixes
  • Set tooltip title/value/background styles in theme JSON
  • Enforce 4.5:1 contrast on all tooltip text
  • Use opaque backgrounds with visible shadows
  • Keep tooltip content minimal and high-signal
  • Optimize queries for sub-150ms rendering
Pass/Fail
  • Legible over dense visuals
  • Title/value hierarchy obvious in <0.5s
  • No KPI name truncation
  • No background noise leaking through
4. Card Visual Uranium — Hierarchy Out of Control Card visuals carry enormous perceptual weight. Without governance, they become mismatched, chaotic, and misleading. Common Issues
  • Inconsistent font sizes across pages
  • Labels and values using identical weight
  • Poor contrast or ghost-gray labels
  • Truncated numbers and wrapping text
  • KPIs relying solely on color to indicate state
FixesShow more...
1 week ago
27 minutes

M365 Show - Modern work, security, and productivity with Microsoft 365
The Knot in the Cloud - Document Management in Dynamics with M365 (Part 2 - Echoes at the Edge)
(00:00:00) The Power of Auto Labeling
(00:00:22) The Nature of Auto Labeling
(00:01:04) Setting Up Auto Labeling Systems
(00:02:06) The Role of Training and Simulation
(00:03:01) The Enforcement and Explainability of Auto Labeling
(00:03:36) Copilot: The Witness with Guardrails
(00:04:27) The Benefits of Auto Labeling
(00:04:52) A Real-World Scenario: Contract Management
(00:05:36) The Importance of Governance and Cadence
(00:10:02) The Eight Principles of Copilot

In Part 1 of our Dark-inspired tech-universe journey, we descend into the shadows where data, memory, and digital architecture begin to blur. This episode sets the stage for an unfolding narrative across timelines—past configurations, present misalignments, and future consequences that loop back on themselves in unexpected ways. We explore how systems behave like the interconnected worlds of Winden: every action has a counterpart, every signal a ghost, every missing event a paradox waiting to be resolved. As we unravel the first thread of the digital knot, we confront questions of identity, origin, and causality inside modern cloud ecosystems. Across multiple segments, we examine the way technical decisions ripple through time—how forgotten settings return like echoes, how automation becomes destiny, and how system failures resemble temporal fractures rather than simple bugs. The conversation moves through dark forests of logic, old databases that refuse to die, and journeys that collapse under their own contradictions. This first chapter is not about solving the mystery—it is about recognizing that the mystery exists. That every log file hides a timeline. That every failed workflow is a loop. That every architectural oversight is a bootstrap paradox waiting to trap us again. Here, at the edge of the digital tunnel, we begin to understand:
Nothing is forgotten. Everything is connected. And every journey eventually leads back to its source.

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-show-podcast--6704921/support.

Follow us on:
LInkedIn
Substack
Show more...
1 week ago
2 hours 39 minutes

M365 Show - Modern work, security, and productivity with Microsoft 365
The Knot in the Cloud - Document Management in Dynamics with M365 (Part 1 - The Origin of the Loop)
(00:00:00) The Loop of Lost Documents
(00:00:14) The Cycle of Chaos
(00:01:13) The Problem with SharePoint
(00:01:41) The Fracture of Time
(00:02:18) The Audit's Silent Failure
(00:09:17) The Knot of Unconnected Files
(00:11:12) Dynamics Without Documents
(00:14:34) The Four Rolls of Memory
(00:16:25) The Cost of the Loop
(00:36:02) Memory vs. Storage

In this first chapter of our series, we descend into the quiet machinery beneath Dynamics, M365, and document governance — a place where data behaves less like information and more like fate. We explore how organizations create unintended loops, how files and processes echo across systems, and how misaligned structures generate outcomes that feel inevitable, almost predetermined. Within this episode, we trace the origins of everyday operational paradoxes: documents that exist in two places at once, permissions that contradict themselves, collaboration paths that collapse under their own recursion. Like the timelines in Dark, these systems reveal a deeper truth — nothing exists in isolation, and every action propagates consequences far beyond its moment. Together, we examine how Microsoft 365, SharePoint, and Dynamics connect and collide, where governance breaks, and why complexity accumulates until the system begins to repeat itself. And as we analyze these patterns, we uncover the central question of Part 1: Is the system broken — or is it simply following the logic we unknowingly designed for it? This episode sets the foundation for everything that follows. The loop begins here.

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-show-podcast--6704921/support.

Follow us on:
LInkedIn
Substack
Show more...
1 week ago
2 hours 30 minutes

M365 Show - Modern work, security, and productivity with Microsoft 365
The Automation Murders: Who Killed the Customer Journey
In this episode, we treat your customer journey like a crime scene. A high-intent cart goes quiet. A churn score spikes and nobody moves. Consent says “yes,” policy says “no,” and the customer disappears into silence. This isn’t a tooling problem—it’s a control problem. We walk through the “death” of a journey step by step: how signals go missing, how over-automation collides, how consent lattices get ignored, and why teams monitor sends but never page on silence. Then we build the forensic system that doesn’t blink: guarded triggers, consent with precedence, idempotency keys, cooling windows, and a single evidence chain you can actually defend. If you care about real-time journeys, marketing automation, Dynamics 365 Customer Insights, Power Automate, Fabric, and Copilot—and you’re tired of guessing why journeys failed—this episode is your case file. What You’ll Learn
  • How customer journeys really “die”
    • Why most failures don’t show up as errors, but as quiet non-events
    • Why teams monitor sends, not non-sends against eligible customers
  • The three main suspects killing your journeys
    • Static segments – “the historian” that always arrives late
    • Manual processes – “the witness who blinks” at decisive moments
    • Real-time journeys – “the sprinter without brakes” that loops and collides
  • Why over-automation is more dangerous than under-automation
    • Too many flows competing for the same signal
    • Caps rewarding the first to shout, not the most urgent case
    • Connector budgets burned on noise instead of risk and recovery
  • Triggers as the new gold
    • How to design high-value, real-time triggers (abandoned cart, churn, CSAT, VIP drift)
    • Fingerprints vs vague rules: value + dwell + recency + consent + caps
    • Why every trigger needs an explicit evaluation artifact and idempotency key
  • Consent done right (and wrong)
    • Person vs brand vs purpose vs region: the consent lattice
    • How “EmailAllowed = true” and brand-level blocks quietly contradict each other
    • Designing lawful fallback trees: email → SMS → push → human → respectful “no send”
  • Building brakes into real-time journeys
    • Cooling windows, re-entry rules, loop detection, and self-write shielding
    • Debouncing triggers and preventing mass-casualty loops
    • Respectful retry and backoff instead of infinite “try again” storms
  • The unit that actually saves customers
    • Customer Insights as the profiler (identity, timelines, signals)
    • Journeys in CI as scene control (triggers, guardrails, choreography)
    • Power Automate as the enforcer (actions, retries, compensations)
    • Fabric as the lab (lineage, contracts, monitors for silence and surge)
    • Copilot as the deputy (draft, simulate, summarize—humans approve)
  • Forensic implementation playbook (6-step audit)
    • Mapping real business intents to precise triggers and fingerprints
    • Installing the consent lattice and suppression hierarchy as single sources of truth
    • Adding cooling, idempotency, backoff, and right-of-way across channels
    • Wiring adaptive cards, SLAs, and escalation to real humans with clocks
    • Proving every save with end-to-end lineage instead of vibes
Who This Episode Is For
  • Marketing operations & lifecycle teams running multi-channel journeys
  • CRM & martech leaders working with Dynamics 365 Customer Insights, Power Automate, Fabric, Copilot
  • Product & growth teams designing real-time interventions (abandoned cart, churn, CSAT)
  • Data, analytics, and platform owners responsible for governance, consent, and auditability
Episode Structure
  1. Opening – The Body of the Journey
    • A high-intent cart that never gets a save
    • How silence becomes the...
Show more...
1 week ago
2 hours 4 minutes

M365 Show - Modern work, security, and productivity with Microsoft 365
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.