Data Governance Episodes

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, inconsistent security, unreadable audit trails, and reporting that turns into archaeology. Dataverse exists to stop that decay. It’s the Power Platform’s governed data backbone: relational schema with referential integrity, role/field-level security, managed environments (dev/test/prod), DLP/retention via Purview, reliable delegation, and first-class integration with Power Apps, Power Automate, Power BI, and Dynamics. The “Dataverse is expensive” objection is a cost illusion—SharePoint’s hidden rework, outages, and compliance risk cost more over time. Practical rule: use Lists for lightweight, short-lived, non-sensitive data; use Dataverse for anything relational, regulated, cross-app, or lon…

Azure Database for PostgreSQL – Flexible Server isn’t pricey because of traffic; it’s pricey because defaults quietly overprovision compute, storage, and HA. “Managed” means patched, not optimized—you still pay for VM cores at idle, disks that only grow, and standby replicas that double costs while doing nothing. The audit hits five leak paths: baseline vCores (and burstable traps), storage auto-grow with no auto-shrink, Premium SSD v2 overbuy (capacity + IOPS + MB/s), HA mirroring that bills 2× for zero business value in most tiers, and backups/maintenance that charge or reboot when you’re not looking. The playbook: right-size from observed metrics, cap/trim storage, reserve HA for revenue-critical writes, use read replicas where they earn their keep, set custom maintenance windows, and pair snapshots with tested logical dumps. Cost control isn’t a SKU—it’s discipline: measure, cap, schedule, and delete the “temporary” you forgot. Defaults prevent support tickets, not invoices.

For years, a “private” Azure Application Gateway still needed a public IP and outbound Internet just to talk to Microsoft’s control plane. Management (control plane) and user traffic (data plane) shared the same door—an architectural contradiction that forced ugly firewall exceptions, Azure-DNS dependencies, and auditor discomfort. The new Network Isolation model finally fixes it: control traffic now travels entirely over Azure’s private backbone, fully separated from your app’s data path. Enable a subscription flag, deploy new gateways, and you can drop the public IP, block all Internet egress, use your own DNS, and still keep WAF, probes, scaling, and cert automation humming. Caveat: isolation applies to new gateways (no in-place flip), and Private Link pairing isn’t supported yet on isolated builds. The move isn’t just config—it’s philosophy: Zero Trust by structure, not exception. Register the flag, redeploy, and retire every “temporary” rule that kept your “private” gateway kinda…

Your Fabric and Power Platform workloads aren’t slow because of Spark or DAX—they’re slow because your data lives far from your compute. Managed storage adds network hops, caps IOPS, and taxes every read/write with latency. The fix isn’t “more nodes”; it’s proximity. Azure Container Storage v2 (ACStor v2) puts hot data on local NVMe inside your AKS nodes, exposing silicon-speed via a lean, CSI-based, ephemeral driver that stripes across all NVMe disks for obscene throughput (multi-GB/s, ~M IOPS). No SANs, no LVM, no etcd—just raw speed you’re already paying for in L-series/Dv6/NC VMs. Use it for Spark shuffles, Dataflows Gen2 staging, Direct Lake caches, and AI model weights; keep durable truth in Blob/managed stores. Result: 3–5× faster pipelines and dashboards, lower Fabric capacity burn, and dramatically cheaper I/O. ACStor v2 reframes storage: NVMe = racetrack (hot, fast, disposable), Blob = archive (cold, durable, cheap). Bring the bytes to the CPU and watch “overnight jobs” fini…

Multi-cloud sounds like freedom—until physics and billing collide. Stitching Azure, AWS, and GCP together turns “resilience” into a toll road: you pay egress to leave one cloud, port/cross-connect fees in the colocation meet-me, and operational overhead to run three of everything (IAM, gateways, monitors, DNS). Latency adds a hidden tax: even with private interconnects, packets still traverse real buildings and fiber, so microseconds compound into slower pipelines and bigger clusters “to compensate.” The result: triple networks, triple consoles, triple invoices—often to move the same dataset in circles. Fixes aren’t shiny services; they’re disciplined design. Pick a primary cloud (where the data lives) and treat others as satellites. Prefer shared services/APIs over bulk data copies—compute near storage, move results, not raw tables. If multi-cloud is unavoidable, colocate smartly: choose regions in the same metro and land in the same carrier-neutral facility to cut latency and cos…

Most internal updates die in Teams noise. The fix isn’t a new platform—it’s wiring together tools you already own. Build a clean, repeatable newsletter pipeline inside Microsoft 365: target precisely with Dynamic Distribution Groups (Entra ID attributes), send consistently from a shared mailbox (branding + continuity), compose with a reusable Outlook template (clear blocks, predictable layout), automate the intake → approval → send workflow (Forms + Planner/Loop + Power Automate), and measure with Exchange traces + Delivery Reports → Power BI. Segmentation keeps messages relevant; a shared sender builds trust; templates train readers; workflow removes heroics; analytics replace guesswork. Wrap it all in light governance (roles, retention, versioned assets), then scale to other departments with the same pattern. The payoff: updates stop getting buried, audiences see only what matters, and leaders finally get measurable engagement—no extra licenses, just discipline across Outlook, Ex…

Your Power App didn’t get “hacked”—it was over-permitted. Treating Dataverse like SharePoint (big buckets, broad roles) turns guest access into a data breach waiting to happen. Dataverse is a relational fortress built on granular privileges (Create/Read/Write/Delete/Append/Append To/Assign/Share), scoped access (User, Business Unit, Parent:Child, Organization), and Business Unit boundaries. One accidental Organization-level privilege on a guest or team role overwhelms every careful filter and exposes records across the environment. This episode shows the failure pattern (cloned roles, Parent:Child scope, team inheritance) and then the fix: isolate external users in their own Business Unit, build minimal guest roles from scratch, prefer Team ownership + Access Teams for precise sharing, apply Field-Level Security to sensitive columns, and automate join/leave via Entra ID. Close with governance: audit ownership and roles, enforce DLP with Purview, monitor high-scope changes, and run …

Your dashboards aren’t just slow—they’re expensive. Every bloated column, lazy import, and tangled relationship silently taxes your Power BI Premium capacity and your team’s time. That inefficiency adds up to real money—often five figures a year. The cure isn’t a plug-in; it’s architecture. Move from kitchen-junk-drawer models to a proper star schema: lean fact tables (events) surrounded by descriptive dimensions (product, customer, date). Keep relationships one-to-many, single-direction. Use surrogate keys, not “unique-ish” natural keys. Then impose DAX discipline: push transformations to Power Query (M) instead of calculated columns, favor columnar ops over row iterators, build clean base measures and layer logic with CALCULATE. Avoid bidirectional filters by default; reach for CROSSFILTER/TREATAS only when you truly mean it. Measure and tune with DAX Studio until refreshes finish in minutes, not hours. The payoff: lower capacity burn, faster refreshes, higher adoption, and re…

Manual GRC reporting burns time and budget: exporting Purview logs to Excel, reconciling pivots, and hoping nothing changed overnight. Replace that drag with an autonomous GRC agent built entirely on Microsoft 365: Purview for audit truth, Power Automate for scheduled extraction + classification, and Copilot Studio for clean, human-readable summaries. The agent is deterministic—not guessy “AI.” You define sources, filters, thresholds, tone, and distribution. Pipeline: Power Automate (on a recurrence) pulls scoped Purview activities, filters noise, normalizes JSON, persists a slim history (Dataverse/SharePoint/SQL), classifies per user/event with numeric thresholds, and logs every run (success/failure) for auditability. It then calls a Copilot Studio endpoint with a structured payload to generate (1) exec summary, (2) technical appendix, (3) recommendations, which the flow publishes to Teams and archives to SharePoint—every time, same format, same metadata. Net effect: standardiz…

AI is not “just another app” you park on general-purpose servers. Enterprise AI behaves like an ecosystem — volatile workloads, bursty data, exotic compute, and constant model evolution. That’s why so many AI pilots glow in the lab then die in production. The five tells that you’re no longer dealing with a normal workload: (1) you need horizontal scale, (2) accelerators like GPUs/TPUs matter, (3) data pipelines must flood continuously not trickle, (4) models mutate across versions and require versioning, observability and drift monitoring, (5) integration with legacy systems becomes the real bottleneck. The escape from “pilot / proof-of-concept death zone” is MLOps + orchestration — a Factory model — where DataOps, MLOps and GenAIOps operate from a unified command deck: templates, RBAC, private networking, GPU scheduling, AutoLake-style consistent data surfaces, and repeatability over artisanal hacking. The engine room is hardware + data + algorithms — and balance across those three …

Your SharePoint isn’t “old” — your legacy workflows are. The episode shows how to modernize without rebuilding: keep your lists/libraries, then layer Power Apps for usable front-ends, Power Automate for reliable approvals, AI Builder to auto-classify/extract from PDFs, and Copilot Studio for conversational retrieval and actions. It stresses urgency: SharePoint 2010 workflows are retired; 2013 workflows are disabled for new tenants (Apr 2, 2024) and fully retire in SharePoint Online on Apr 2, 2026. Quick audits + replacements turn a “2013 dungeon” into an AI-powered hub—with governance intact (AI Builder training data stored in Dataverse, visible only to the model owner or approved admins).

Microsoft Fabric fundamentally changes how Power BI handles data. With OneLake and Direct Lake, Power BI can now query lakehouse tables directly with performance similar to Import mode — without creating duplicate copies or maintaining complex refresh cycles. The winning Fabric pattern is simple: Dataflows Gen2 → Lakehouse → Pipelines → Semantic Model → Direct Lake report OneLake becomes the governed vault (think: OneDrive for data). Purview delivers lineage + labeling from day one. Fabric admin controls let you enable it safely in trial capacity first — not in full production. Dataflows Gen2 hydrates the lakehouse. Pipelines keep it alive — and alert you when the 3am goblin breaks a step. Semantic models + Direct Lake then turn that hydrated lakehouse into fast, governed, analytics-ready Power BI. When you blend those moving parts — Fabric stops being a “feature” of Power BI and becomes the platform that powers it.

SharePoint Premium with SharePoint Advanced Management (SAM) is the governance backbone that keeps Copilot from turning oversharing into a data leak. You’ll learn how to spot risky sites with Data Access Governance (DAG), lock down visibility with Restricted Access Control (RAC), use Site Access Reviews to make owners accountable, and apply AI Insights to prioritize fixes. Think moat + walls + watchtowers: RBAC is the moat; SAM builds the walls; DAG/AI Insights are the watchtowers; owners are the guards.

In a recent podcast, Mirko Peters discussed the challenges of choosing between Synapse Link and Dataflow Gen 2 for Dataverse pipelines, emphasizing the importance of making informed decisions to avoid project failures. The conversation highlighted issues that arise when multiple teams create overlapping data links, leading to data duplication and governance chaos. Peters illustrated the differences between the tools: Synapse Link offers greater control and rollback capabilities but requires more complex setup, while Dataflow Gen 2 allows for quick, user-friendly data transformations but lacks robust governance features. He stressed the need for discipline in managing refresh schedules to prevent data loss and budget overruns. The discussion took place in the context of organizations needing to align their data management tools with their specific operational needs, advocating for a tailored approach rather than a one-size-fits-all solution. This topic is crucial as it addresses the po…

In this episode, we dive into how to replace measures in Power BI using DAX, helping you simplify your data model, improve report performance, and create more accurate, maintainable calculations. We explain what measures are, why they’re essential for interactive Power BI reports, and how they differ from calculated columns. You'll learn when and why replacing a measure makes sense—whether for performance gains, model cleanup, or updating outdated logic. We walk through the step-by-step process of replacing measures in Power BI Desktop, including analyzing existing DAX, deciding between a new calculated column or a revised measure, and updating visuals to ensure accurate results. We also cover common troubleshooting issues like broken visuals, context-related errors, and performance bottlenecks—and how to avoid them. The episode also explores DAX fundamentals, including essential functions like CALCULATE, VAR, SUM, and SWITCH, along with best practices for writing clean, efficie…

In this episode, we break down Microsoft Power BI’s pricing structure to help you understand the different license options, costs, and features available across the Power BI ecosystem. Whether you're comparing Power BI Free, Pro, Premium Per User, or Premium Per Capacity, this guide gives you a clear explanation of how each plan works and what it offers. We discuss how Power BI pricing supports everyone—from individual users exploring Power BI Desktop to large enterprises relying on dedicated capacity and advanced analytics. You’ll hear how each licensing model fits different business needs, what Power BI Pro includes for collaboration and report sharing, and when it makes sense to invest in Premium for scalability, AI-powered features, and improved performance. We also explore Power BI Embedded for app developers and explain how consumption-based pricing factors into capacity planning. The episode covers the key factors to consider when choosing a Power BI plan, including user …

In this episode, we explore how Power BI and Microsoft Teams work together to create a seamless, collaborative analytics experience. We break down how Power BI’s powerful data visualization capabilities integrate directly into Microsoft Teams, allowing organizations to share insights, discuss reports, and make data-driven decisions without switching apps. You’ll learn the basics of Power BI—connecting to data, creating reports, and publishing dashboards—alongside an overview of Microsoft Teams as a unified workspace for communication and collaboration. We explain how embedding Power BI reports into Teams channels enhances visibility, streamlines discussions, and keeps everyone aligned around the same analytics. The episode walks through practical steps for embedding, sharing, and accessing Power BI content in Teams using the Power BI app. We highlight how teams can collaborate in real time, discuss insights directly next to visualizations, and make reporting part of everyday wor…

In this episode, we dive into Microsoft Fabric, the unified data and analytics platform reshaping how organizations manage, analyze, and act on their data. Designed to bring Power BI, Data Factory, Azure Synapse, and other Microsoft services into one integrated environment, Fabric simplifies everything from data ingestion and transformation to advanced analytics and real-time reporting. You’ll learn what Microsoft Fabric is, why analytics play a central role in modern data platforms, and how Fabric creates a single source of truth across your organization. We break down the major components—Fabric Data Warehouse, Data Factory, data engineering tools, SQL capabilities, data science workflows, and seamless Power BI integration. These features enable businesses to build scalable data pipelines, perform complex analytics, and visualize insights effortlessly. The episode explains how Fabric enhances Power BI through real-time analytics, unified data access, and deeper integration wit…

In this episode, we dive into how R and SQL Server work together to create a powerful data analytics workflow. You’ll learn why SQL Server excels at storing, organizing, and retrieving large datasets, while R specializes in statistical analysis, visualization, and machine learning. When combined, these two tools streamline data processing, reduce duplication of effort, and enable deeper, more efficient data insights. We explore common use cases—such as running SQL queries from R, analyzing SQL Server data with R’s statistical packages, and using R to create visualizations or predictive models based on SQL data. The episode also walks through how to set up your environment, install the required R packages (RODBC, DBI, odbc, sqldf), and configure ODBC connections so R can query SQL Server directly. You’ll learn best practices for writing SQL queries inside R scripts, using T-SQL features, fetching data into R data frames, and mapping R data types to SQL Server types without losing…

In this episode, we explore how organizations can turn Dynamics 365 Business Central telemetry into powerful insights using Microsoft Power BI. Telemetry is one of the most valuable—and often underused—capabilities in Business Central. It captures performance data, user behavior, errors, and system activity, giving administrators a complete view of how their environment is running. We begin by breaking down what Business Central telemetry is, why it matters, and how it helps companies identify performance issues, track usage, and optimize their configurations. The episode explains how telemetry is collected through Azure Application Insights and what kinds of data Business Central emits—everything from page views and API calls to background sessions and extension behavior. Listeners learn the practical steps for enabling telemetry in the Business Central admin center and how Azure Application Insights becomes the hub for querying, monitoring, and alerting on system activity. We …

In this episode, we dive into one of the core engines behind Microsoft Fabric’s modern analytics ecosystem—Dataflows Gen2. We explore how this next-generation data ingestion and transformation tool is shaping the way organizations prepare, refine, and deliver data for analytics. We start with an overview of Microsoft Fabric, Microsoft’s unified analytics platform that brings together data engineering, data science, real-time analytics, Power BI, data factory, and lakehouse capabilities in a single integrated environment. Fabric is designed to simplify complex data estates, and Dataflows Gen2 plays a pivotal role in achieving that simplicity. Listeners get a clear explanation of what Gen2 actually means: improved architecture, better performance, expanded connectivity, stronger data prep features, and support for more complex data ingestion scenarios. Gen2 builds on traditional Power Query–based dataflows but offers scalability and reliability fit for enterprise-grade pipelines.…

In the evolving world of Microsoft Fabric, the Digital Twin Builder preview emerges like a quiet shift that changes everything without announcing itself loudly. You start by taking the world you already know—machines, rooms, sensors, movements, transactions—and giving it a second life inside the Fabric environment. This second life isn’t static or symbolic; it breathes with real-time data, always adjusting, always reflecting what’s happening right now. Data from sensors, logs, or operational systems flows into the Fabric lakehouse, and the builder reshapes it into a digital form that mirrors the physical world. The semantic canvas becomes the place where these connections come alive, letting you see how everything relates, how one action affects another, and how the digital counterpart shifts as the real world does. You wire event streams into the model, and suddenly the quiet digital structure begins to pulse with updates—temperature changes, equipment activity, stock movement, envir…

power bi keeps showing up in the background of every conversation about data because it does something most tools struggle with: it doesn’t just help you look at numbers, it helps people work together around them. the reports, the dashboards, the visuals—those are great, but the real power is how easily a team can gather around the same set of insights without fighting through email attachments or version chaos. you start with data from wherever it lives, pull it into power bi, shape it, build something that actually makes sense. but the magic happens the moment you hit share. suddenly the report isn’t just yours; it becomes something the whole team can poke at, question, filter, and react to. in the service, everything lives in the cloud, so no one needs to hunt for the right file or worry about sending the wrong version. everything updates in place. everyone sees the latest truth. workspaces add another layer, turning what used to be a solo project into a team studio. people c…

This episode argues that Syntex being folded into SharePoint Premium is not a naming joke — it’s Microsoft consolidating content processing, content experiences and governance into one platform so Copilot can stop guessing and start delivering real answers. SharePoint Premium = Brain (content experiences) + Muscle (content processing) + Bouncer (governance) When those three are unified → content becomes structured + governed + queryable → and that is what finally makes Copilot useful. Real-world proof: orgs like London Stock Exchange cut document processing time from hours → minutes. The real danger isn’t bad AI — it’s good AI running without guardrails and multiplying bad classification + oversharing mistakes. Governance is not optional. It’s the safety net. Key tactic: start with 1 high-value process (invoices/contracts), use prebuilt models first, measure time saved, then scale.