Dataverse isn’t “included.” It’s a premium, enterprise-grade platform with costs that stack fast: licenses, capacity, environments, storage (db/file/log), and API limits. Most sticker shock comes from assumptions—thinking M365 covers Dataverse, that guests are free, or that storage is cheap. Use…
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 conver…
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…
Generative Pages feel “free” because they turn a sentence into a working Power Apps page. But the instant you click Generate, you’re on Dataverse—and that’s premium land: governed data, model-driven scaffolding, audit, flows, and a license bill. The UX hides the escalation: scaffolding a React page…
“Vibe coding” (Generative Pages) turns plain-English prompts into responsive, Dataverse-aware React pages, replacing the pixel babysitting of manual canvas apps. The upside: speed, consistency, accessibility, and built-in governance via Dataverse metadata and roles. The downside: speed can mask fra…
“Low-code for everyone” was a great story—but the sequel is Vibe Code: Power Apps Code Apps (React + TypeScript + Git) living inside the same governed Power Platform. Low-code (Canvas/Model-Driven) still wins for speed and business-led prototyping, but it hides complexity, fragments UI, and resists…
Generative Pages feel like low-code’s endgame: describe a page, get React that talks to Dataverse, ship in minutes. The trap is hidden in one click—Edit Code. The second you crack open JSX, Power Apps stops shielding you. You inherit npm drift, security patches, schema changes, auth gaps, and AI “h…
Model-Driven Power Apps sell “enterprise-grade” credibility but often deliver ceremony over outcomes. The catch is Dataverse: powerful, yes—but it drags licensing, security matrices, solution layers, environment sprawl, and governance latency into problems that needed a shared list and three notifi…
SharePoint Lists feel “free” and familiar, so teams prototype apps on them—and then accidentally build departments on sand. As lists multiply, you get broken lookups, 5k-item throttling, rogue permissions, attachment bloat, and schema drift. Governance collapses quietly: no environment isolation, i…
Most Power Apps look “off” because makers skip Containers and reinvent UI on every screen. The fix is structural (containers) and systemic (component libraries). Containers replace fragile X/Y positioning with responsive layout physics—stack, align, distribute, and resize automatically across devic…
Opening – The Power Automate Delusion Everyone thinks Power Automate is an integration engine. It isn’t. It’s a convenient factory of automated mediocrity—fine for reminders, terrible for revenue-grade systems. Yet, somehow, ...
Most organizations don’t lack coding talent — they lack capacity because requests are funneled into a tiny central dev team. This creates a backlog that burns out developers and traps massive value inside manual work. The unlock isn’t “more IT,” it’s enabling citizen developers—frontline employees …
Power Pages validation shouldn’t feel like rolling a natural 1. In this episode, you’ll learn how to pair VS Code + Power Platform Tools + GitHub Copilot Chat (with the @powerpages participant) to fix flaky validations, demystify Liquid, and speed up front-end work without duct tape. We start by ma…
Model-driven apps aren’t here to dazzle—they’re here to survive schema change, scale security, and ship to production. In this episode you’ll watch a blank Dataverse table become a themed, role-aware app with custom forms, views, relationships, security roles, and automation. We contrast the “flash…
Dataverse migrations aren’t “move some rows on Friday.” They’re an org redesign: data model, security, automations, integrations, licenses, and cutover. This episode shows how to pick Dataverse for the right reasons, audit what you have, map legacy lists/custom tables to a relational schema, keep f…
Power Automate approvals shouldn’t be a single “Start and wait” glued to an email. Build them like software: dynamic approvers, restartable stages, clean audit logs, modular child flows, and sane reminders/escalations that don’t spam. This episode shows how to turn fragile, one-off flows into resil…
No-code/low-code (e.g., Power Apps) ships fast, but that speed often bypasses guardrails—creating hidden risks in data movement, compliance, and ownership. Pro-code moves slower, yet enforces discipline because you must design identity, networking, logging, and release gates up front. Security isn’…
Power Platform is great for everyday business automation, but it isn’t built for heavy workloads or complex integrations at enterprise scale. As usage grows, you’ll hit limits—throttled connectors, missing API operations, and execution timeouts—especially in flows with nested logic or large dataset…
Locking down Power Platform feels safe but backfires: demand shifts to shadow IT, data leaves your tenant, and compliance visibility disappears. Disabling or yanking licenses cleans up dashboards—not risk. Real safety comes from guided use: give people sanctioned lanes and watch what they build. Th…
PowerApps turns plain SharePoint forms into slick apps fast—but the real test starts after go-live. Under production load, the usual suspects appear: slow loads, flaky saves, and validations that don’t match SharePoint’s rules. This episode walks through where forms typically break (scale, client-s…
Compliance fails when it’s static. Checklists freeze rules in time, but regulations keep moving. In this episode, you’ll learn how to turn compliance from a brittle, manual checklist into a self-updating, feedback-driven system using Power Automate + SharePoint/Dataverse + Power BI. We cover recur…
Manual GRC reporting is a risk multiplier—copy-paste errors, stale data, and missed escalations. With Power Automate, you can stitch together SharePoint, Excel, Dataverse, and ticketing tools into a real-time pipeline that standardizes data, assembles evidence, and publishes audit-ready packs autom…
Dataverse “slowness” is often schema, not size. Fix table bloat, simplify relationships, and add the right indexes to turn crawling forms and timing-out flows into crisp responses. Design for performance from day one—balance normalization, limit cascades, and index what you filter on.
“Add a connector” isn’t an AI strategy. Real deployments pair Power Apps or Dynamics 365 with Power Automate orchestration, Azure OpenAI for intelligence, and Azure API Management for security, throttling, and observability. This episode details the end-to-end pattern: clean and enrich payloads in …