Episodes

🔍 Key Topics Covered 1) The Misunderstood Middleman — What the Gateway Actually Does - The real flow: Service → Gateway cluster → Host → Data source → Return (auth, TLS, translation, buffering—not a “dumb relay”). - Modes that matter: Standard...

Still dragging cards around in Microsoft Planner like it’s 2015? In this episode, I show you how to stop babysitting boards and start speaking tasks into existence with a “Task Planner” Copilot agent.You’ll learn how Planner, Copilot Studio, and Power Automate actually fit together: Planner keeps the board tidy, Copilot reasons over your requests, and Power Automate quietly runs the rules in the background.Step by step, we build an agent in Copilot Studio with tight instructions and locked-in Group/Plan IDs so it can safely create, list, and update Planner tasks from natural language — including “tomorrow”, “next Friday”, or “set everything to Friday”.Then we push it into Microsoft 365 Copilot and Teams so you can say things like “Create three tasks for next week’s sprint” or “List my open tasks, then set them all to Friday” without touching a single card.We wrap with the unsexy parts that actually matter: governance, DLP, connector ownership, context limits, and how t…

This episode explains how to eliminate manual Excel work by using an autonomous agent that completes spreadsheet-based RFIs without human involvement. Instead of relying on macros or step-by-step automation, the system watches for incoming Excel files, interprets the questions inside them, generates accurate responses using defined knowledge, writes the answers back into the spreadsheet, and sends the completed file automatically.The episode emphasizes the difference between simple automation and true autonomy. Automation waits for instructions, while an agent acts independently by observing, reasoning, and completing tasks end to end. RFIs are used as the ideal example because they are structured, repeatable, and clearly define what “done” looks like. This structure allows the agent to behave predictably rather than creatively, reducing errors and eliminating wasted effort.A major theme is the importance of structure and discipline. Clean inputs, consistent spreadsheet layout…

Your Copilot sounds smart but secretly knows nothing about your business. It’s guessing from Wikipedia while your real memory—orders, invoices, inventory—sits locked in SQL Server behind the firewall. This episode exposes the fix: the Power Platform Data Gateway, a locked-down, outbound-only “spinal cord” that lets Copilot read and write live SQL data without exposing your database.You’ll hear how to plug Azure SQL into Copilot Studio as a Knowledge Source so every chat can fire real-time T-SQL through the gateway instead of stale CSV exports. Then it gets wild: SQL Actions turn Copilot from a chatty analyst into a digital employee that can safely insert and update records with confirmations, least-privilege access, and full audit trails.Finally, you’ll blueprint the “hybrid brain”: SQL as memory, the gateway as spine, Copilot + Power Platform as brain, and Teams/Web as the face your users see. With clusters, indexes, telemetry, and a battle-tested checklist, you’ll ship an AI…

Think adding Model Context Protocol to Copilot Studio is “just a custom connector”? This episode blows that lie apart. We unpack why the shiny MCP dropdown only talks to Microsoft’s own sources, and why your “connected” MCP is usually a dead tunnel, not a live bridge. You’ll learn what MCP really is (a streaming context protocol, not a data feed), the exact gotchas that keep your custom connector invisible or silent (host/base URL, schemas, streaming, TLS, proxies), and how to actually prove it works with real-time markdown, citations, and logs. Most importantly, we show why all this fiddly setup isn’t nerd vanity—it’s how you turn Copilot from a hallucinating chatbot into a compliant, auditable analyst your security and compliance teams can live with.

Cloud Flows vs Agent Flows: The Budget Bombshell Microsoft Hoped You’d MissYou’re building automations like it’s 2019 and it’s quietly draining your budget. The premium connector trap turns one small flow into a company-wide license bill. Hidden API throttling slows down your automations without warning. AI Builder double-pay means you’re getting charged twice for one result. Agent Flows include premium and custom connectors with no extra tax. Real math: 300 actions cost about forty cents. Learn when to use Agent Flows versus Cloud Flows and how to convert old Cloud Flows into Agent Flows—it’s one-way. Message-based billing ends surprise invoices. One model charges you for existence, the other charges you for work. If it starts in chat, is personal, or spikes in usage, use Agent Flows. If it’s shared, scheduled, or cross-team, use Cloud Flows. Save your budget, save your weekend, and stop paying for idle automation.

Microsoft just made Python “run natively” inside Power Platform — and chaos followed.From Copilot Studio’s Code Interpreter to Azure Functions, everyone’s suddenly a Python dev… until the flows time out, the files hit 512 MB, and IT gets a heart attack.In this episode, we break down the great Python illusion: why “runs natively” ≠ “runs anywhere,” what the Code Interpreter actually is (a sealed glass terrarium for code), and when to stop pretending it’s production infrastructure.Then we contrast it with Azure Functions, the real grown-up runtime — scalable, governed, auditable — and explain how to move from prototype to production without setting your tenant on fire.

Microsoft says Copilot is now free across Word, Excel, PowerPoint, Outlook, and OneNote. But here’s the twist: it’s not magic — it’s your data, orchestrated. In this episode we rip off the marketing gloss and show how Microsoft Graph pipes your emails, files, meetings, and notes into a single “AI brain.” You’ll see how Copilot actually works, where it really saves time, and why privacy, DLP, and audit workloads spike the moment you switch it on. Faster workflows? Yes. Free compliance? Not a chance.

Your “intern” just became your scariest, smartest coworker—and it’s made of code.In this episode, we unpack how Microsoft Security Copilot is quietly turning traditional Security Operations Centers into AI-driven defense factories. Forget drowning in alerts, phishing noise, and endless Patch Tuesday chaos. These synthetic analysts—autonomous agents baked into Defender, Entra, Intune, and Purview—are triaging phishing emails, tightening conditional access, and pre-planning vulnerability remediation before most humans finish their first coffee.You’ll meet three “interns” that:Read thousands of emails a day and never get alert fatigueConstantly patrol identities and access policies for silent privilege creepAct as a 24/7 digital medic for vulnerabilities across your endpointsThen we go a step further: you can build your own agents with plain English prompts, effectively staffing a synthetic workforce tailored to your environment.Is this the end of SOC analysts—or …

Most companies think Copilot = instant productivity.Wrong.Copilot isn’t the ROI engine — Power Automate is.Copilot only “suggests.” Power Automate does the work.In this episode we expose the 5 hacks that turn Copilot from a chatty intern into a revenue-generating automation machine — including Custom Connectors that unlock your hidden data, Adaptive Cards that turn AI suggestions into one-click actions in Teams, and telemetry that finally proves AI impact in real numbers — not hype.If you want actual business outcomes, not AI vibes — this is the episode.

AI inside the Microsoft Power Platform isn’t just about 'Copilot writes formulas' anymore. In 2025, Microsoft introduced four innovative capabilities that transform how apps, data, and automation are developed: Dataverse Prompt Columns, AI Form Filler / Form Assist, Generative Pages, and Copilot Agents. These aren’t just new features — they represent a new build model where you describe your intent, and the platform constructs the logic automatically. For instance, Dataverse Prompt Columns enable reasoning within Dataverse records, while AI Form Filler Automation turns emails and screenshots into structured data with a simple paste. Generative Pages facilitate UI layout as a conversational process, and Copilot Agents act as trained teammates to delegate tasks efficiently. The core shift is from knowledge of syntax to mastering how to craft effective prompts. Makers who rely solely on procedural methods risk falling behind those who design outcomes using natural language. This emerging…

Managing identity in 2025 shouldn’t feel like running a smartphone next to a rotary phone, but that’s exactly what happens when organizations rely on both on-prem Active Directory and Microsoft Entra ID. This episode breaks down the real cost of that dual-directory setup: mismatched policies, sync drift, failed Conditional Access checks, and endless “I can’t log in” tickets.We start by explaining the Source of Authority—who actually owns your users and groups—and why hybrid sync was meant to be a bridge, not a permanent home. You’ll learn how the IsCloudManaged property flips ownership from AD to Entra ID and why that shift is essential for Zero Trust, modern governance, and consistent authentication.Before moving anything, preparation is key. We walk through cleaning up stale AD objects, checking synchronization health, enforcing MFA, and documenting the attribute and app dependencies that can break during migration.Finally, we cover why groups should move first, how to i…

This might be the week the bots stop “assisting”… and start working.Microsoft quietly flipped a switch — and Copilot Studio can now literally use your computer.Not API calls. Not connectors. Not cloud sandboxes.Actual mouse movement. Real keyboard input.A legit AI agent that can launch your Power App, fill the fields, and submit the form — like a disturbingly compliant intern.In this episode we unpack the feature Microsoft calls Computer Use — the update that turns Copilot into a hands-on operator of Windows machines. We walk through setup, the security ceremony no one warns you about, and then watch the AI stumble, misclick, recover, adapt… and eventually succeed. It’s messy, slow, hilarious — and also historic.This is agentic AI in the enterprise — the moment automation stops being a diagram and becomes a digital worker.If your business runs on legacy apps, intranet buttons, and “almost integrated” everything… this is the episode you need to hear. Because this is…

In this episode of the M365 Show, we unpack the most common Power Apps mistake in the Microsoft 365 ecosystem: assuming SharePoint is a “free database.” We break down why SharePoint lists look like a database, but architecturally behave like a file-centric collaboration layer—not a transactional data engine. From delegation limits to the infamous 2,000-record wall, we explain how apps built on SharePoint scale beautifully for a month… then collapse under load, concurrency, throttling and lookup chains. If you’ve ever heard “we’ll just use SharePoint for now,” this episode will save future performance pain. Learn what a real database is, how Dataverse and SQL handle indexing + relationships correctly, and why treating SharePoint like SQL is the fastest way to kill a Power App.

Power Apps charts are obsolete. They look like a 1990s Excel demo and they can’t be styled, can’t be made dynamic, and can’t be made modern without pain.We stop trying to fix them.The new move is simpler: don’t render charts inside Power Apps at all. Let AI draw the chart image for you — on demand — in the exact style you want. Power Apps then just displays the Base64 image the AI returns. It becomes a host, not a renderer.You can press a button, pass JSON to apiprompt.predict, and the AI generates the visual: bar, line, lollipop, area, whatever. With real time app data. Zero Power BI dependencies. Zero native chart control. Zero template limits.This turns charts into prompts instead of properties. You describe the chart you want, AI draws it, Power Apps shows it. That’s the future.

Most “inventory systems” are just Excel sheets LARPing as ERPs — and that’s why warehouses lose assets, fail audits, and end up with phantom spreadsheets nobody trusts. Barcode scanning isn’t a gimmick — it’s the only sane way to ingest perfect data into Dataverse once — not typed twice. Power Apps barcode scanning isn’t about “cool phone camera toys” — it’s about forcing referential integrity at ingestion. The moment you scan, Dataverse locks reality to a record. That’s how you get traceability, audits that pass, automation that triggers, and CFOs who stop sweating missing laptops.

Power Apps makes it dangerously easy to build an app on a SharePoint list—and most beginners assume that if it works instantly, it must be the right foundation. It isn’t. SharePoint was never engineered to act like a real transactional database, and when you scale—users, data size, queries—delegation breaks, filters lie, and performance collapses invisibly. Early success hides future failure. The platform rewards you with a fast prototype that slowly becomes a production liability. Dataverse is built for data. SharePoint is built for collaboration metadata. Use the wrong one, and Power Apps becomes fragile, inaccurate, and untrustworthy at scale.

You paid for AI synapses — but you’re parking fossils. Fabric was engineered for real-time intelligence, semantic relationships, live context, and AI agents that reason. Most orgs treat it like a network share. The result? Zero cognition, zero AI, zero advantage — just expensive cold storage with better Microsoft branding.

Your company isn’t blocked by data—it’s blocked by syntax.Copilot Studio turns plain-English questions into governed Fabric queries, so “What was our revenue by quarter?” finally gets an instant, secure answer—no SQL, no tickets, no waiting. It’s not a chatbot; it’s a translation engine that remembers context, respects permissions, and makes your warehouse talk back like a smart analyst. The real bottleneck has never been tables—it’s been language. This is the fix.

Power BI is lying to you.Those neat, orderly “Applied Steps” you trust are a façade.Power Query is secretly rearranging, deferring, collapsing and sometimes ignoring the way you wrote your transform steps — which is why your filters don’t filter, your merges get weird, and refreshes suddenly go from 20 seconds to 10 minutes.The only way to stop getting blindsided is to understand the invisible engine + query folding… because THAT is the real execution order — not the thing you see in the pane.

Copilot didn’t hallucinate — you hallucinated first.Your schema lied → Fabric believed it → Copilot repeated it with confidence.Bad Bronze → leaky Silver → fake Gold = executive decisions built on fiction.Fix the Medallion discipline + fix the semantic layer — or keep paying for an AI that politely invents your reality.

Power BI isn’t failing because of visuals — it’s failing because nobody plans. 60–70% of BI projects become expensive wallpaper. This episode exposes the 3 discipline steps that separate strategic intelligence from dashboard vanity — why most organizations confuse activity for progress, and how to finally stop the “successful failure” of Power BI.

You Thought Your Power BI Maps Were Safe breaks down the Bing Maps → Azure Maps eviction — and why this is not optional, not cosmetic, and not “a visual upgrade.”As of Oct-2025, Bing Maps visuals are deprecated.If you don’t migrate, your map visuals become blank boxes.This episode explains what’s actually changing, why Azure Maps is a compliance-era replacement — not a skin swap — and the admin switches you MUST flip in the tenant before anything works.We cover the migration traps, the false comfort of “auto convert,” and the difference between visuals that render and visuals that survive production.This is not a warning — it’s a countdown.

Power BI Collaboration — from Wild West → Hub-and-SpokePower BI self-service feels empowering… until every department defines “revenue” differently and no one agrees which dashboard is real. In this episode, we break down why the chaos isn’t a tooling problem — it’s an architecture problem — and how the Hub-and-Spoke model fixes it.We walk through how to create one shared semantic truth (the Hub) — with certified datasets, owners, refresh discipline, and version control — while still letting departments move fast in their own exploration spaces (the Spokes).This is the roadmap to move your analytics org from “faith-based metrics” to governed trust.