AI In Microsoft 365 Episodes

Think spreadsheets are chaos? Cute. In this episode we stress-test Microsoft Fabric against the worst data you own: photorealistic 3D assets and full-fidelity digital twins. We break down why a single “file” is actually a sprawling supply chain of scans, meshes, textures, physics, and licenses — and how one sloppy ZIP export can turn into a global compliance nightmare. You’ll learn how Fabric turns governance from theater into an always-on safety system: Entra ID–backed identity, object-level security, lineage that behaves like a black-box recorder, rights-as-code, and streaming with signed tokens instead of random file copies. We walk through real workflows for artists, simulation engineers, and robotics teams, and show how to version twins so “latest” stops being a ticking time bomb. If you’re still trusting folders, shared drives, and good intentions to protect multi-gigabyte 3D assets, this episode is your wake-up call. Hit play to see why, if your governance can hold a 1:1 …

Your Copilot isn’t smart – it’s a very expensive autocomplete. In this episode, we break down why classic RAG (retrieve-augment-generate) quietly fails the moment your truth lives in more than one system, and how “agentic RAG” on Azure turns Copilot from a context tourist into an actual reasoning engine. You’ll hear how Planner, Retriever, and Verifier agents running on Azure AI Agent Service can roam Microsoft Fabric, SharePoint, and external data, cross-check their own answers, and deliver evidence-linked insights that auditors, CISOs, and data leaders can actually trust. We dig into On-Behalf-Of auth, RLS/CLS, and Purview labels so your AI respects the same permissions as your humans, instead of leaking CFO forecasts to interns. If you’re a CIO, CDO, architect, BI lead, or security/GRC owner who’s tired of hallucinated KPIs and pretty-but-useless dashboards, this is your blueprint. Learn how to cut decision latency from months to minutes, turn SharePoint chaos into a semantic…

Typing to Copilot is the new fax machine—and your thumbs are the bottleneck. In this episode we break down how to give Copilot an actual voice, a memory, and a legal department, so it can keep up with the way you think, not the way you type. You’ll hear how GPT-4o Realtime turns Copilot from a slow, QWERTY-bound chatbot into a true conversational partner that listens while you speak, lets you interrupt mid-answer, and responds in milliseconds. Then we plug that voice into a real brain: Azure AI Search with RAG, so every answer is grounded in your own policies, standards, and FAQs—fully cited, fully governed. We walk through the blueprint step by step: Blob Storage, Azure AI Search, a hardened proxy layer, and secure M365 voice integration in Copilot Studio, Power Apps, and Teams. No biometrics, no cowboy connectors, just Entra ID, Purview, DLP, and logs your CISO can sleep on. If you’re still typing into Copilot, you’re leaving productivity—and compliance-grade insight—on the…

Stop your cloud migration. Seriously. If you’re still bragging about being “cloud first,” this episode will show you why your shiny Azure estate is actually AI hostile. 🧨 We break down the brutal truth: lift-and-shift doesn’t modernize anything—it just moves your technical debt into someone else’s data center. Your VMs won’t give Copilot safe, governed access to data… they’ll give it a front-row seat to your permissions sprawl, lineage gaps, and compliance nightmares. You’ll learn: Why cloud ≠ AI (and how your 2015 migration is blocking 2025 AI use cases) The Fintrax case study: “cloud-first” optics, AI pilot failure, compliance incident, and a 70% cost blowout The 3 pillars of real AI readiness: data discipline, MLOps maturity, and governance talent A no-BS 3-step playbook: Unify → Fortify → Automate so every AI decision becomes traceable and defensible If your roadmap still reads like a relocation plan instead of an AI architecture, hit play before you burn the next dec…

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.

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.

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…

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.

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.

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.

Copilot Notebooks feel magical — a conversational workspace that pulls context from SharePoint, OneDrive, Teams, decks, sheets, emails — and synthesizes answers instantly. But the moment users trust that illusion, they generate data that has no parents. Every Copilot output — a summary, paragraph, bullet list — is derived content that contains fragments of sensitive sources… but inherits none of the original sensitivity label, retention policy, audit trace, or Purview detection scope. Result: enterprises are silently creating a Shadow Data Lake — an ocean of unlabeled, untraceable derivative insight. The core problem isn’t Microsoft’s security model — it’s that governance frameworks assume lineage, and AI isn’t generating lineage. Solution: treat AI output as first-class content. Label by default. Apply Derived Data policies. Time-box Notebook containers. Limit sharing. Make AI summaries review-gated. AI productivity accelerates — and so does compliance debt — unless…

GPT-5 in Copilot is dazzling—but its fluency can fool you. It produces executive-ready prose fast, yet lacks defensible provenance. That makes it great for creation (drafts, outlines, brainstorming) and terrible for compliance (anything that must survive audit). The Researcher Agent is the counterweight: slower, source-driven, and methodical. It asks clarifying questions, fetches and cites sources, logs retrieval, and builds an auditable chain of reasoning. In regulated environments, that difference is existential: GPT-5 gives velocity; the Agent gives veracity. Use Copilot for momentum; use the Agent when lineage, citations, and reproducibility are mandatory—governance docs, financial/regulatory reporting, internal knowledge articles, Entra/security audits, and exec-level market analysis. The winning pattern is a hybrid workflow: ideate with Copilot → verify critical claims with the Agent → reintegrate citations and let Copilot polish language. Keep layers separate to avoid “governan…

The SharePoint Knowledge Agent is marketed as an autonomous librarian; in practice, it’s an overconfident intern that needs supervision. It can suggest metadata, set simple natural-language rules, and answer questions across libraries—but it amplifies whatever chaos already exists. Auto-tagging mirrors your inconsistencies (duplicate/variant columns), rules fire unreliably (timing/indexing fragility), and chat answers can surface sensitive or misleading content because fluency ≠ judgment. The biggest hidden risk is metadata inflation and AI drift: casual prompts quietly spawn new columns and rules, fragmenting taxonomy and contaminating Copilot results downstream. The fix isn’t to ban it—it’s to sandbox and govern it: run pilots in curated libraries, review every suggested column, lock naming conventions, monitor column/rule creation, and gate publication. Used deliberately, it speeds broad classification and search. Used as “autopilot,” it manufactures governance debt at machine spee…

Most “analysis” in Excel is disguised janitorial work: inconsistent dates, mixed data types, rogue spaces, and copy-pasted chaos that later poisons Power BI, Power Automate, and Fabric. The fix isn’t heroics—it’s Excel Copilot acting as an AI janitor that understands structure, enforces types, and prepares data for downstream systems. Two modes matter: Chat (diagnose, explain) and App Skills (actually change the sheet). The practical playbook: 1) Normalize Everything (types, dates, casing, spaces, IDs), 2) Validate & Flag Outliers (rules for missing/absurd values, deviation checks), 3) Transform for Integration (summaries, tidy tables, headers for Power BI/Flows). Once clean, Copilot upgrades sheets from neat to smart—sentiment tagging, segmentations, “Think Deeper” diagnostics—then hands results straight to Power BI/Power Automate without brittle CSV shuffles. The manual phase is over: treat Copilot as a preprocessor at data intake, codify cleanup as prompts, and promote analysts fro…

Power Apps forms turn knowledge workers into typists—rigid fields, copy-paste from emails/PDFs, and slow, error-prone decay that pollutes Dataverse, Power BI, and downstream automations. The fix isn’t more validation; it’s an interpreter: the AI Data Entry Agent. Inside model-driven apps, it converts unstructured input (Smart Paste) and file uploads (OCR) into clean, schema-aligned records—with source snippets, confidence cues, and your existing validation rules enforced. Complex cases shine: multi-address suppliers, related child tables, and certifications become structured data in seconds, not spreadsheets. Architecture matters: entity extraction → schema alignment → pre-submit validation, all within tenant boundaries and Dataverse security. Caveats: premium licensing/AI capacity, regional compliance, domain jargon limits, and “it maps to what exists” (no auto-schema). Roll out with guardrails—pilot libraries, telemetry, naming sanity—then scale. Net result: forms stop demanding typ…

Enterprises reflexively “modernize” by migrating data—Lists → Dataverse → Fabric—burning time and budget to recreate what already works. The myth: Copilot needs data moved to “enterprise-class” stores. The reality: Copilot Studio now connects directly to SharePoint Lists—live, permission-aware, no ETL, no duplication. Authentication replaces replication. Governance is inherited (same ACLs/MFA/audit), risk drops (fewer copies), and answers reflect real-time list updates. Performance? Modern Lists scale when designed sanely (index columns, filter views); slowness is usually architecture, not platform. When to migrate: high-velocity transactions, strict relational integrity, or ERP-grade complexity. Otherwise, keep Lists where business actually happens and let Copilot converse with them. Strategically, Lists flip from “pre-database staging” to living knowledge cells—departmental truth that Copilot queries on demand (up to ~15 lists per agent). New commandment: stop moving data; start con…

Canvas Apps gave pixel freedom but bred fragility: endless containers, brittle Power FX, and hours lost to layout therapy while data modeling and governance languished. The game has changed. Generative Pages inside Power Apps shift creation from craft to command: you describe intent (“ideas tracker with category filters and a bar chart”), and AI generates responsive, accessible, Dataverse-aware pages on a React stack—prewired CRUD, filters, charts, theming, and role-respecting security. The App Agent iterates via natural language, producing reversible diffs instead of formula spaghetti. Architecture—not artistry—drives speed, consistency, and scale: schema-aligned components, tokenized theming, built-in accessibility, and versionable changes. Developers don’t vanish; they graduate—owning schema, governance, performance, and policy while AI handles layout. Keep Canvas for quick sketches or ultra-bespoke surfaces; use Generative Pages for production apps that must be maintainable and co…