Power Platform Episodes

Your SharePoint isn’t messy – it’s a digital landfill you’re paying to host. Dead projects, duplicate “final_v7_REAL_final” files, ghost guest access, broken links, and a Copilot happily hallucinating on rotten content. This video shows you how to turn that chaos into a governed, measurable, adult-run SharePoint and Microsoft 365 environment – using licenses you already own. No third-party tools, no fluffy “best practices”, just enforcement. You’ll learn how to stop SharePoint sprawl at the source with standardized site provisioning, templates, and naming that actually stick, then enforce lifecycle with automated inactivity checks, owner attestations, and read-only/archival rules in both E3 and E5. We’ll define what a “healthy” site really is, expose inactive and ownerless sites, cut duplicate content, and reduce search noise so users finally hit the right document on the first click. We go deep on retention labels vs retention policies, how to auto-apply labels using metadata, …

Python is NOT the language of AI inside the Microsoft stack—and in this episode, I show you why that belief is quietly wrecking your Power Platform projects, inflating defects, and burning your budget. If you’re cramming Python into Power Automate, Power BI, Fabric, or custom connectors as “glue code,” this is your wake-up call. We break down why Python is amazing for analytics, ML, and Fabric notebooks—but a terrible choice for everyday orchestration inside Power Automate, Power BI Dataflows Gen2, Dataverse, and Microsoft 365. You’ll learn how Office Scripts (TypeScript-flavoured), Copilot, and agent-style orchestration (like type-agent) can write and run the glue for you, with typed contracts, native connectors, and AI-generated scripts that actually respect your schemas and governance. Instead of debugging brittle Python in Azure Functions at 2:14 a.m., you’ll see how to: Keep Python where it shines: Fabric notebooks, advanced analytics, ML. Use Copilot + Office Scripts to …

Your SharePoint / Microsoft 365 document libraries are quietly killing productivity — and Microsoft already shipped the fix. In this episode, I show you how the NEW Doc Libs UX, Forms, Autofill and Copilot turn your “final_v3_REALLY_final.docx” graveyard into an intelligent workflow that actually guides work instead of hiding it. You’ll see how enhanced breadcrumbs, visible filter pills, board view and saved views slash “where did my file go?!” drama, and how one adoption-killing mistake in your forms is sabotaging everything. Then we flip the front door: idiot-proof intake with Forms, smart metadata from Autofill (reading time, abstracts, categories) and a simple triage routine that keeps your response folders from turning into purgatory. Finally, we weaponize Copilot inside Doc Libs: instant version comparisons, punchy abstracts, audio overviews and grounded Q&A that turns a file pile into decisions on demand. Implement the five switches from this episode and your library stop…

Your Power BI dashboards aren’t broken – you’re just using them for the wrong job. This episode shows why “Export to PDF” is a lying screenshot, and how paginated reports (in the Service, Report Builder, or Visual Studio) finally give executives the print-perfect, audit-ready PDFs they keep asking for. In under half an hour, you’ll learn exactly which tool to pick, how to avoid layout disasters, and a simple upgrade path from “quick hack” to fully governed reporting suite.

You thought VAL vs EXPR was harmless syntax sugar. In reality, it decides when your metrics are evaluated, which means the same function, same arguments can return a completely different “truth” — clean visuals, perfect totals, and numbers that are confidently wrong.

Stop treating the cloud like a USB stick from 2007. In this episode, we unpack why “Sync Everything” secretly trashes your CPU, storage, bandwidth, and governance—and how OneDrive shortcuts turn that wheezing laptop into a fast, curated workspace. If your fan is screaming, your sync queue is stuck on “processing changes,” and your C: drive is one bad folder away from full, this is your intervention: doors to the source, not copies of the building.

Still paying sky-high cloud rent for servers you can’t even touch? This episode shows you how to bring “the cloud” home, slash your Azure bill, and keep all the governance, security, and automation you actually care about. You’ll learn how Azure Arc lets your own mini-PCs and edge boxes wear an Azure badge, so they obey the same policies, Defender rules, RBAC, and monitoring as any public region. Then we go step-by-step through Azure Local: zero-touch voucher USB enrollment, spinning up a private Azure region on a shoebox-sized PC, and deploying VMs and AKS from the same portal you already use. We expose the AD trap and replace it with certificate-based identity in Azure Key Vault for cleaner, auditable zero-trust at the edge. Finally, we break down the economics: swap 24/7 VM rent for one-off hardware, tiny power draw, and predictable Capex—while keeping burst workloads in the public cloud. If you’re a CIO, architect, or DevOps lead tired of roulette-cloud billing, this is your playb…

Your GPUs aren’t the problem. Your data fabric is. In this episode, we unpack why “AI-ready” on top of 2013-era plumbing is quietly lighting your cloud bill on fire—and how Azure plus NVIDIA Blackwell flips the equation. Think thousands of GPUs acting like one giant brain, NVLink and InfiniBand collapsing latency into microseconds, and Microsoft Fabric finally feeding models at the speed they can actually consume data. We break down the Grace-Blackwell superchip, ND GB200 v6 rack-scale VMs, liquid-cooled zero-water-waste data centers, and what “35x inference throughput” really means for your roadmap, not just your slide deck. Then we go straight into the uncomfortable truth: once you fix hardware, your pipelines, governance, and ingestion become the real chokepoints. If you want to cut training cycles from weeks to days, slash dollars per token, and make trillion-parameter scale feel boringly normal, this is your blueprint. Listen in before your “modern” stack becomes the …

🔍 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…

Learn how to connect an MCP server to Copilot Studio with custom connectors, authentication, schemas, testing, streaming, and troubleshooting.

Cloud Flows vs Agent Flows: The Budget Bombshell Microsoft Hoped You’d Miss You’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.

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…

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.

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.

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-Spoke Power 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.