Fabric Data Agent Accuracy Is a Distribution, Not a Number
I asked a Fabric data agent 24 questions in three wordings, ten times each, on real AEMO data. It scored 82%, but only 39% of wordings were always right.
301 articles
I asked a Fabric data agent 24 questions in three wordings, ten times each, on real AEMO data. It scored 82%, but only 39% of wordings were always right.
Small files come from simple arithmetic, and every reader pays a cost per file. Where they come from, how to measure them, and how to compact them safely.
Fabric's preview data engineering agent runs with the launching engineer's permissions. What to delegate first, which settings to pick, and what stays human.
Fabric mirroring for BigQuery is GA, but it moves cost to Google: CDC compute, egress, keyless reseeds and schema ownership decide when to mirror or copy.
Fabric IQ is GA in Copilot Chat, Cowork and MCP. Treat each semantic model as an agent endpoint: RLS, OLS, metadata contracts and default-on access.
A query for one day should not read three years. How partition pruning works, the five ways it silently breaks, and how to pick partition columns.
The physical plan shows what Spark will actually do: shuffles, join strategy, pruning, Python UDFs. How to read one, and which plans should worry you.
Eventstream can now read Azure Event Hubs with workspace identity. How to move off SAS keys, the RBAC each side needs, and when a service principal still wins.
One hot key can make one task do a third of a job, and more nodes will not help. How to spot skew in the Spark UI, find the keys, and fix it properly.
Fabric Data Warehouse GPU query acceleration is in preview. Why the 7x benchmark won't predict your bill, and how to run a fair A/B test on your own queries.
Fabric data agents now use GPT-5.1 and a Responses API client. What notebook, Foundry and app callers must change, and why you need a full eval re-run.
Developer mode and PBIP are GA and PBIR becomes the default report format. Why that makes report review realistic, what breaks, and how to stage the move.
Fabric Runtime 2.0 is GA and set to become the default in late September. A plan to inventory, test libraries and Delta features, and pin runtimes first.
Power BI now converts single Direct Lake tables to Import in web modelling, making storage mode a per-table choice with real refresh and governance costs.
Event-triggered refresh for Fabric materialized lake views trades predictable capacity and clean ordering for freshness. Where events fit and where they don't.
Git integration and fabric-cicd ship Fabric items well. Workspaces, capacity, domains, roles and tenant settings still need their own source of truth.
Use a read-only service principal, the scanner APIs and the Fabric admin APIs to detect governance drift in a Fabric tenant, without handing it write access.
How identity flows through OneLake shortcuts: passthrough vs delegated, SQL endpoint access modes, the Direct Lake over SQL exception, and lost policy.
What a Fabric pipeline rerun actually runs again, why utcNow() and run IDs break recovery, and how to make rerun from failed activity safe.
How workspace splits, item names, descriptions, endorsement and domains decide what people find in the OneLake catalog, plus a findability test you can script.
Now that Fabric materialized lake views are GA: which raw-to-silver steps I'd move onto them, how to keep rejected rows, and where notebooks still win.
Why many data quality root-cause fixes come down to where the check runs, and how to build a write-audit-publish boundary on a Fabric lakehouse.
Put Fabric Real-Time Dashboards under Git so tile and query changes are reviewed, validated before Update from Git, and reverted cleanly when they break.
A write-audit-publish pattern for Fabric Data Warehouse: load, run SQL checks, then roll a warehouse snapshot forward so analysts only see verified data.
How to catch a slipping Fabric pipeline before its deadline: alert on missing and late runs, not just failures, using job events, KQL and the jobs API.
Fabric sensitivity labels apply per item, not per table, so item boundaries, defaults, inheritance and protection policies need designing before OneLake grows.
How to version a Fabric lakehouse table contract once several notebooks depend on it: change classes, a writer guard, pinned readers and safe renames.
How to run blameless reviews for data quality incidents: record who detected it, which control was missing, and turn each review into a tracked change.
Set Fabric Activator and KQL alert thresholds from the cost of a miss versus the cost of acting, then tier actions by the value at risk, not the raw reading.
A placement rule for Fabric: when data belongs in a Warehouse table you own, and when reading a lakehouse shortcut through the SQL analytics endpoint is enough.
How to keep Fabric pipelines readable as they grow: naming before the first Git commit, child pipelines with clear contracts, and variable libraries for config.
A passthrough OneLake shortcut adds speed but no boundary: how to give data science teams curated Fabric features without opening the whole lakehouse.
Why I split Fabric ingestion and curation at the landing table, when that means separate workspaces joined by shortcuts, and when one lakehouse is enough.
Measure data product reliability in good hours, catch bad data at the publish boundary, and let a failure budget decide when pipeline changes stop.
Use update policies, materialized views and a KQL state-change function in a Fabric Eventhouse to strip duplicates, chatter and flapping before anyone queries.
A triage runbook for disputed numbers in Fabric: check definition, timing, filters and logic in order, using time travel, snapshots and Semantic Link.
How to split a slow Fabric pipeline run into start delay, queueing, Spark start-up, copy transfer and idle gaps, with KQL and the activity runs API.
Treat every OneLake shortcut as a cross-team dependency: placement, identity, write paths, environment variables and a REST inventory of what points where.
Why slow Fabric silver loads often trace back to the raw zone: landing layout, header checks, small files and bronze table maintenance, with PySpark examples.
How to cut an inherited data quality rule set down to the checks that change decisions, using failure history, ownership and an explicit retirement path.
Use KQL baselines, week-over-week comparison and diffpatterns in an Eventhouse to tell a meaningful operational change from ordinary noise, and to explain it.
How to stop metric drift in Fabric by giving every metric one home layer and one named owner, then enforcing both rules with schemas, grants and versions.
How dependency conditions decide a Fabric pipeline's final status, why try-catch hides failures, and how to log, alert and still fail the run honestly.
How to stop Fabric workspace and item sprawl before it starts: lifecycle states, domains, tags, endorsement, retention settings and a weekly hygiene audit.
Why I keep a library of deliberately broken raw files for every Fabric bronze-to-silver transform, and how to run them as plain PySpark tests before release.
Why every data quality incident should produce two pieces of work, a containment action and a root-cause fix, and how to run both on a Fabric lakehouse.
How to design Fabric Activator and KQL queryset alerts that fire on transitions, carry an owner and a next step, and stop teams muting the channel.
How I design an analyst-facing schema in Fabric Data Warehouse: views as the contract, permissions scoped to it, and SQL checks that catch breaks first.
How to design Fabric Copy jobs and copy activities so a failed, partial or repeated copy never leaves duplicates, gaps or a watermark that moved too far.
Why adding people as Fabric workspace Contributors is the access shortcut that erodes OneLake boundaries, and a faster pattern that keeps them intact.
A table contract is half the job: assigning owners per layer, collapsing load outcomes to three, and mapping Fabric pipeline failures to runbooks.
Why I'd track five quality signals per feature table at the data engineering to AI handoff, and how to compute them in a Fabric notebook without a new tool.
Rules for Fabric Real-Time Dashboards that stay trusted: tiles with owners, visible data freshness, refresh costs you can afford, and thresholds in tables.
Why fact table grain, not clustering or statistics, sets the performance ceiling in Fabric Data Warehouse, and how to declare and test it in T-SQL.
How to remove brittle dependencies from daily Fabric loads with one orchestrating pipeline, readiness checks, idempotent writes and deliberate retries.
Why OneLake governance has to be designed before scale: table contracts, schema-enabled lakehouses, explicit owners and deliberate failure modes in Fabric.
Four decisions for a messy Fabric raw zone: contracts at silver, Delta constraints, quarantined rows with failed batches, and lakehouse schemas.
One sensor-monitoring design on Fabric Real-Time Intelligence: where to filter, enrich, aggregate and alert, and what Eventhouse retention costs you.
Why KQL is a baseline Azure skill, how its pipe model differs from SQL, and the operators, join defaults and has-vs-contains traps that matter most.
Every Fabric engine speaks Delta Lake, but not the same features. How to use the interoperability matrix so Spark tables still work in SQL and Power BI.
What consolidating Azure Data Factory, Databricks, Azure SQL and Power BI onto Microsoft Fabric delivered in production, and where the seams still show.
Eight years of data pipelines taught me to plan for reruns, late data and schema drift. The habits that matter, with Delta MERGE and Fabric examples.
Our Synapse to Fabric migration took twice as long as planned. Five lessons on scope, notebook refactoring, Direct Lake, capacity monitoring and training.
Why we moved Microsoft Fabric from F64 to F32: the three sizing mistakes, the monitoring and alerts we added, and when going smaller is the wrong call.
A practical decision guide for picking Azure Databricks or Microsoft Fabric as your primary data platform in 2026, and when running both is worth the cost.
An honest look at running Microsoft Fabric on an F64: what OneLake and Direct Lake deliver, how throttling really works, and what the bill looks like.
Azure AI Foundry unified the AI development experience, combining model catalog, deployment tools, and prompt management into a single platform. This…
Organizations struggle with data sprawl, unclear ownership, inconsistent definitions, and regulatory requirements. A unified governance approach addresses…
Each layer serves a specific purpose in the data refinement pipeline. Bronze captures raw data, silver cleans and conforms it, and gold delivers…
These Fabric updates demonstrate Microsoft's commitment to building a truly unified data platform that handles real-time and batch workloads while…
Batch processing introduces latency between data generation and insight availability. For fraud detection, operational monitoring, and customer engagement…
Without a feature store, teams often duplicate feature engineering work across projects. Features computed for training may differ from inference, causing…
Every write operation to a Delta table creates a new version. This transaction log enables point-in-time queries and rollback capabilities essential for…
Poor data quality leads to incorrect business decisions, failed ML models, and eroded trust in analytics platforms. A proactive approach to data validation…
Use Fabric notebooks to create interactive RAG applications that combine data exploration with AI-powered question answering over enterprise datasets.
For development and test environments, implement auto-pause policies to reduce costs during inactive periods. Monitor utilization patterns and adjust…
Fabric notebooks provide a seamless path from exploration to production, with built-in governance, collaboration, and scalable compute.
Data Activator monitors data streams and triggers actions based on conditions you define. It connects to Power BI reports, Eventstreams, and Fabric data…
Bronze holds raw ingested data. Silver contains cleansed and conformed data. Gold presents business-level aggregates ready for consumption.
Eventhouse is the storage layer optimized for time-series and streaming data. It automatically indexes data for lightning-fast queries.
Ask questions about your data in natural language and get executable code. Generate complex SQL from natural language descriptions.
Data Factory pipelines use a visual designer with activities that can be chained together.
Bronze tables store data exactly as received from source systems, preserving the original format for replayability and debugging.
Quality encompasses completeness, accuracy, consistency, timeliness, and validity. Each dimension requires specific checks.
Eventstreams support multiple source types including Azure Event Hubs, Azure IoT Hub, and custom applications. The visual designer makes it easy to…
Iceberg provides ACID transactions, schema evolution, time travel, and partition evolution for data lakes. Its format-agnostic design works with Spark…
Ignite remains the premier event for understanding Microsoft's enterprise AI direction. Planning your learning path around expected announcements helps…
VACUUM removes data files no longer referenced by the Delta log. Without regular vacuuming, your storage costs grow unbounded as old file versions accumulate.
A Lakehouse stores data in open formats like Delta Lake while providing SQL query capabilities, ACID transactions, and schema enforcement. In Microsoft…
Use descriptive table and column names that match business terminology. Add measure descriptions explaining what each calculation represents. Create…
Use Delta Lake constraints and expectations to ensure data quality at each layer. Fabric's Data Quality monitoring provides visibility into quality metrics…
For real-time inference, query the feature store directly from your model serving endpoint. Fabric's query optimization ensures millisecond-level feature…
Microsoft Fabric's Real-Time Intelligence workload has matured significantly since GA. Today I'm exploring how to build streaming analytics pipelines that…
Microsoft Fabric's Real-Time Intelligence workload has matured significantly since GA. We've implemented several production streaming scenarios, and I want…
Microsoft Fabric integrates AI throughout the analytics lifecycle from ingestion to insights.
This works on F2 and above now. For small businesses, this transforms how reports are built.
Fabric + AI creates a powerful platform for intelligent analytics. Leverage Spark's scale with AI's intelligence.
Build 2025 promises to be significant for data and AI professionals. Stay tuned for the actual announcements and be ready to experiment with new capabilities.
Fabric + AI creates a powerful combination for intelligent analytics. Start with simple enrichments and build toward complex AI-powered workflows.
Use GPT-4o structured outputs to draft a star schema from requirements, check it with plain code, and generate Fabric Warehouse DDL that respects its limits.
Answer plain-English questions from a Power BI semantic model by having Azure OpenAI choose measures and filters, then run them with semantic link.
A phased plan for rolling out data mesh on Microsoft Fabric and Purview in early 2025: what to build first, what's still preview, and when to stop.
A decision guide for placing filters, enrichment, aggregation and alerts across Eventstream, Eventhouse and Spark in Fabric Real-Time Intelligence.
Where Copilot in Microsoft Fabric stands in January 2025, what each workload's Copilot gets wrong, and how to review its output before it ships.
A January 2025 status check on Microsoft Fabric after Ignite 2024: which features are GA, which are preview, and how to sequence this year's work.
Success with Fabric comes from treating it as a platform transformation, not just a technology deployment. Invest in people, process, and governance…
1. Start with a focused use case Don't try to migrate everything at once 2. Embrace lakehouse architecture It's the foundation of Fabric 3. Invest in…
Fabric AI Skills, Copilot for Microsoft 365, and Copilot Studio all contribute to this trend.
OneLake AI Workloads bring AI capabilities directly to your data, eliminating data movement and enabling efficient large-scale AI processing.
The Fabric + Copilot Studio integration makes enterprise data conversationally accessible while maintaining security and governance.
This unification simplifies the developer experience and provides a clear path from experimentation to production.
Streaming ML enables intelligent real-time systems that continuously learn and adapt. Start with robust feature engineering and monitoring before enabling…
Real-time AI enables immediate, intelligent responses to streaming data. Start with well-defined use cases and gradually increase complexity.
Eventstream enhancements make real-time analytics more powerful and accessible. Start with simple streaming scenarios and progressively add complexity.
Analytics agents reduce manual toil while improving data reliability. Start with monitoring agents for quick wins, then expand to exploration and quality…
AI Skills democratize data access while maintaining governance. Start with well-defined domains and expand based on user feedback.
The Fabric platform continues to mature into a comprehensive, AI-native analytics solution.
The DP-600 certification is your gateway to becoming a recognized Microsoft Fabric expert. Good luck with your exam preparation!
The DP-600 certification demonstrates your expertise in Microsoft Fabric. Focus on hands-on practice and understanding the "why" behind each feature, not…
Stay informed about the Fabric roadmap to plan your data platform strategy effectively. The pace of innovation is rapid, so regular review of announcements…
Microsoft Fabric represents the natural evolution toward unified, AI-powered data platforms. Understanding this evolution helps you make informed decisions…
A unified data platform on Fabric eliminates the complexity of managing multiple systems while providing the flexibility to handle any data workload.
Unifying Transactional and Analytical Workloads in Fabric
HTAP in Microsoft Fabric enables unified transactional and analytical workloads without complex ETL pipelines. Design your schemas with both workloads in mind.
PostgreSQL in Fabric will bring familiar PostgreSQL capabilities to the unified data platform. Start preparing now by designing schemas that work well with…
SQL Database in Fabric brings enterprise-grade transactional capabilities to the unified data platform, with seamless integration to analytical workloads…
Fabric Databases bring operational database workloads into the unified Fabric platform, with automatic integration to OneLake.
Microsoft announced the preview of relational databases directly within Fabric, bringing transactional workloads into the unified platform.
Effective Microsoft Fabric governance requires attention to access control, data quality, cost management, and lifecycle management. This month's…
1. Collect comprehensively : Gather data from all sources 2. Aggregate appropriately : Different audiences need different views 3. Automate distribution :…
1. Tag everything : Consistent tagging enables accurate allocation 2. Use multiple methods : Combine direct, shared, and overhead allocation 3. Document…
1. Start with showback : Build understanding before chargeback 2. Keep it simple : Complex models create disputes 3. Automate collection : Manual processes…
1. Start with visibility : You can't optimize what you can't see 2. Allocate costs : Enable accountability through showback/chargeback 3. Automate policies…
1. Monitor regularly : Daily cost tracking enables early intervention 2. Set alerts : Budget alerts prevent surprises 3. Allocate costs : Understand which…
Smoothing averages capacity consumption over a time window, allowing brief spikes without immediate throttling.
Autoscale in Microsoft Fabric provides the flexibility to handle variable workloads while optimizing costs. Configure base capacity for typical load, allow…
1. Monitor utilization patterns : Understand your usage before optimizing 2. Stagger workloads : Avoid concurrent peaks 3. Right size jobs : Use appropriate…
Native execution bypasses traditional JVM-based Spark execution to run queries using native code optimized for modern CPUs.
1. Enable AQE : Adaptive Query Execution handles many optimizations automatically 2. Right size partitions : Target 128MB partitions 3. Broadcast small…
1. Filter early : Push filters as close to data source as possible 2. Use appropriate joins : Broadcast small tables 3. Enable AQE : Adaptive Query…
1. Always enable V Order : Low overhead, universal benefits 2. Add Z Order for specific needs : Known filter patterns 3. Limit Z Order columns : Maximum 3 4…
V-Order is a write-time optimization that physically reorders data within Parquet files to maximize compression and query performance, especially for Direct…
1. Enable by default : For most analytical workloads 2. Choose appropriate bin size : 128MB general, 256MB for Direct Lake 3. Combine with auto compact :…
1. Schedule regular compaction : Daily for high volume tables 2. Use partition aware compaction : Avoid rewriting entire large tables 3. Enable auto…
1. Target 128 256MB files : Optimal for most query engines 2. Use Snappy or ZSTD : Best compression/speed balance 3. Sort by filter columns : Improves…
Delta Lake provides a reliable, performant foundation for modern data platforms. Its ACID transactions, time travel, and schema evolution capabilities make…
1. Use managed identity : Preferred for Azure services 2. Leverage shortcuts : Don't copy data unnecessarily 3. Optimize file sizes : 128MB 1GB for best…
1. Use shared storage : ADLS as the common data layer 2. Standardize on Delta Lake : Compatible format for both 3. Optimize for readers : Both platforms…
Most enterprises use multiple clouds: 1. Minimize cross cloud joins : Materialize frequently joined data 2. Use shortcuts wisely : Only for data that…
1. Define clear domains : Each lakehouse should own specific data 2. Minimize cross domain joins : Materialize frequently joined data 3. Implement…
Traditional ETL moves data physically: Virtualization queries in place: Shortcuts create virtual pointers to external data: 1. Use for read heavy workloads…
CDC captures row level changes (inserts, updates, deletes) from source systems: The simplest option for supported sources: For more control over the CDC…
For sub second latency: For minute level latency with relational sources: Combine streaming and batch for different data types: Distribute data to multiple…
Open Mirroring provides a standardized way to: Write Delta Lake tables directly to a mirrored database location Maintain the mirrored database experience…
Mirroring eliminates the need for complex ETL between these systems.
Unlike SQL mirroring which uses change tracking, Cosmos DB mirroring leverages the built in analytical store: 1. Go to your Cosmos DB account 2. Navigate to…
1. Navigate to your workspace 2. Click New Mirrored Database 3. Select Azure SQL Database 4. Configure connection: Server name Database name Authentication…
Mirroring creates a continuously synchronized copy of your operational database in OneLake as Delta Lake tables: As of GA: Azure SQL Database : Full support…
This month we explored Microsoft Fabric comprehensively. Today I'm summarizing key learnings and best practices from my June 2024 deep dive.
Private Endpoints enable secure, private connectivity to Microsoft Fabric. Today I'm taking a deep dive into implementing private endpoints.
Network security provides defense in depth for your data platform. Today I'm exploring network security options in Microsoft Fabric.
Conditional Access enables Zero Trust security by controlling access based on conditions. Today I'm exploring how to implement Conditional Access for…
Data Loss Prevention (DLP) helps prevent accidental data exposure and ensures compliance. Today I'm exploring DLP implementation in Microsoft Fabric.
Sensitivity labels help classify and protect data based on its sensitivity level. Today I'm exploring how to implement data classification in Microsoft Fabric.
Security is foundational to any data platform. Today I'm exploring the security architecture and best practices in Microsoft Fabric.
Accessing external data is essential for hybrid and multi-cloud scenarios. Today I'm exploring external data access patterns in Microsoft Fabric.
Data sharing enables collaboration while maintaining security. Today I'm exploring data sharing patterns in Microsoft Fabric.
A data marketplace enables data discovery, sharing, and consumption across your organization. Today I'm exploring how to build one using Microsoft Fabric.
API-first data design treats data products as services with well-defined interfaces. Today I'm exploring how to build data APIs in Microsoft Fabric.
Data contracts formalize the agreement between data producers and consumers. Today I'm exploring how to implement effective data contracts in your data…
Data products are the deliverables of a data mesh. Today I'm exploring how to build, manage, and consume data products in Microsoft Fabric.
Federated governance balances domain autonomy with organizational standards. Today I'm exploring how to implement effective federated governance in…
Domain-Driven Design (DDD) principles apply to data architecture just as they do to software. Today I'm exploring how to design data systems around business…
1. Clear domain boundaries Define ownership clearly 2. Product thinking Treat data as a product 3. Self serve enablement Empower domain teams 4.…
Workspaces are the containers for collaboration in Fabric. Effective governance ensures organization, security, and efficiency. Today I'm covering workspace…
Tenant settings control what users can do in your Fabric environment. Today I'm covering the essential settings every admin should configure.
Effective capacity management is crucial for Fabric performance and cost control. Today I'm diving deep into capacity planning and optimization.
Fabric administration has matured significantly. Today I'm covering the latest admin capabilities for managing your Fabric environment effectively.
Copilot for SQL transforms natural language into T-SQL queries. Today I'm exploring how to leverage AI for data warehouse development in Fabric.
Copilot for Notebooks transforms how data engineers write code. Today I'm exploring practical patterns for leveraging AI assistance in Fabric notebooks.
Fabric Copilot has received significant updates. Today I'm exploring how AI assistants are transforming data work in Microsoft Fabric.
Automated actions are what make Data Activator powerful. Today I'm exploring all the ways you can respond to data conditions automatically.
Reflex triggers are the heart of Data Activator. Today I'm diving deep into building sophisticated automated workflows that respond to your data.
Data Activator monitors your data and triggers actions when conditions are met: A Reflex is a Data Activator item containing: Objects : Entities to monitor…
Real-time dashboards bring your streaming data to life. Today I'm exploring how to build effective real-time visualizations in Fabric.
KQL Querysets are the analysis layer of Real-Time Intelligence in Fabric. Today I'm exploring how to write effective KQL for real-time analytics.
Eventhouses are the foundation of Real-Time Intelligence in Fabric. Today I'm exploring their architecture and capabilities in depth.
Real-Time Intelligence is Fabric's answer to streaming analytics, combining the power of Azure Data Explorer with the unified Fabric experience.
Power BI continues to evolve with AI-driven features that make data analysis more accessible. Here's what's new in April 2024.
Automation is key to maintaining reliable data pipelines. This guide covers scheduling, orchestration, and automation patterns in Microsoft Fabric.
The Microsoft Fabric SDK provides a Pythonic interface for working with Fabric services. This guide covers installation, configuration, and common…
Microsoft Fabric's REST APIs enable automation and integration with your existing tools. This guide covers the key APIs and common use cases.
Implementing CI/CD for Microsoft Fabric ensures reliable, repeatable deployments of analytics artifacts. This guide covers building end-to-end deployment…
Microsoft Fabric's Git integration brings modern version control practices to analytics. This guide covers setting up and using Git with Fabric workspaces.
AI can transform raw data into polished, narrative reports. This guide covers building automated report generation systems that combine data analysis with…
Microsoft Fabric's Copilot transforms data analysis by enabling natural language interactions with your data. This guide shows how to leverage Copilot for…
Microsoft Fabric Copilot has received significant upgrades, making AI-assisted data analysis more powerful and contextually aware. Here's what's new and how…
Microsoft Fabric continues to evolve as a unified analytics platform. April 2024 brings significant updates across data engineering, science, and business…
Avoid over-partitioning. If partitions have < 1GB of data, consolidate. Use Data Pipelines, Not Just Notebooks
A readiness checklist for the Data Activator preview in Fabric: tenant switches, throughput and alert limits, failure modes, and when to wait for GA.
How Data Activator preview triggers really fire: objects, Is vs Becomes conditions, timers, Power Automate custom actions and the throughput limits to plan for.
The KQL habits that keep queries over streaming telemetry fast in Fabric KQL databases and Azure Data Explorer, and the shortcuts that quietly slow them down.
Practical Fabric Eventstream patterns: what belongs in the no-code event processor, what belongs in KQL, and what to fix before events arrive.
How Eventstream, KQL databases, Power BI and the Data Activator preview fit together in Fabric as of January 2024, and when to choose something else.
Design-time rules for Direct Lake in Fabric: size tables to your SKU's guardrails, move logic into Delta, avoid views, and control when models reframe.
How I decide OneLake layout in Fabric: workspaces as security boundaries, a lakehouse per layer, a flat Tables folder, and shortcuts where copies hurt.
A diagnose-first workflow for slow Fabric reports: check capacity, the visual, DAX, Direct Lake fallback, Delta file layout and Spark, in that order.
How Fabric smoothing, carryforward and the four throttling stages work, how to read them in the Capacity Metrics app, and which levers actually help.
A practitioner's triage of the Microsoft Fabric December 2023 update: %%configure, Git conflict resolution, KQL in OneLake and what to leave alone.
Five enterprise AI bets for 2024, each checked against what is generally available or still in preview on Azure as of 1 January 2024.
Cost optimisation isn't about cutting features — it's about aligning spend with business value. During holiday slowdowns I help teams identify idle…
Right-sizing Fabric capacity is a finance-and-engineering problem: choose a capacity SKU that matches peak loading patterns, instrument CU consumption, and…
Query performance is where UX and cost meet. My practical approach is to measure user-facing latency, inspect query plans, and prioritise optimisations that…
V-Order feels like a secret weapon because it's a write-time optimisation with outsized read-time benefits. In practice I enable V-Order on wide, heavily…
Direct Lake changes the Power BI performance story — but it's not automatic. Over the past months I've seen Direct Lake deliver dramatic improvements when…
Performance tuning in Fabric blends write-time optimisations (v-ordering, partitioning) with query-time strategies (predicate pushdown, materialised views).…
Fabric's component set is broad; the hard part is picking the minimal surface that solves your business need. This guide distils when to use Lakehouse…
Choosing Lakehouse vs Warehouse is an architectural trade-off: for open-format, large-scale analytics and ML, Lakehouse is the better fit; for classic T-SQL…
Designing for scale in Fabric is about decomposition and clear contracts between layers. The medallion architecture works well: small, composable…
Shipping Fabric into production exposes common anti-patterns — unbounded capacity use, duplicated data copies, and insufficient observability. The best…
There is no substitute for learning from real migrations: the patterns we reuse (lift-and-shift for bulk data, iterative modernization for dependent…
A practical Fabric adoption roadmap balances fast wins with platform work — start with a high-impact pilot, instrument the value stream, and invest in a…
Microsoft Fabric reached General Availability at Ignite 2023 — November 15-17 in Seattle — and it's the outcome I genuinely thought might take another six…
Copilot in Microsoft Fabric was announced at Ignite 2023 as the AI-powered natural language layer across the Fabric experience. The capabilities at launch…
Microsoft Purview and Fabric integration is the enterprise governance story that matters most for regulated industries and large organisations where data…
Data lineage in Fabric — the ability to trace where a piece of data came from, what transformations it passed through, and what items depend on it — is…
Fabric endorsement — the Promoted and Certified badge system for Fabric items — is a lightweight but important trust signal in a self-service analytics…
Fabric Domains are the tenant-level organisational construct that lets large enterprises apply data mesh principles to their Fabric deployment — grouping…
Fabric governance is where the platform's SaaS architecture creates both an advantage and a complication for enterprise security teams. The advantage…
Fabric licensing is genuinely different from the Azure pay-as-you-go mental model that most Azure practitioners are familiar with, and understanding the…
Microsoft Fabric reaching General Availability at Ignite 2023 (November 15-17) is the milestone that transforms the six-month public preview from an…
Best practices and lessons learned from implementing Microsoft Fabric solutions for enterprise analytics.
Best practices and patterns for deploying machine learning models in Microsoft Fabric.
Using the PREDICT function to apply machine learning models directly in Microsoft Fabric for seamless predictions.
Deep dive into the SemPy library for working with Power BI semantic models in Microsoft Fabric notebooks.
Understanding Semantic Link in Microsoft Fabric for seamless integration between Power BI datasets and Spark notebooks.
Building end-to-end data science workflows using Microsoft Fabric's integrated capabilities.
Exploring AI and machine learning capabilities within Microsoft Fabric for intelligent analytics.
Exploring Fabric Copilot capabilities for AI-assisted data engineering, analysis, and reporting.
Exploring the latest Microsoft Fabric updates and how they transform enterprise data analytics.
Tomorrow we'll explore Azure OpenAI Code Interpreter. MLflow Tracking Experiment Best Practices MLOps Patterns
MLflow in Fabric is the managed tracking layer that turns a Spark notebook into a reproducible experiment record. The integration is transparent — you…
Tomorrow we'll explore MLflow integration in Fabric. Model Management in Fabric MLflow Model Registry Model Deployment Guide
Data Science in Fabric brings ML experiment tracking, model registration, and batch prediction into the same platform where the training data lives — which…
Tomorrow we'll explore Fabric Data Science capabilities. Real Time Dashboard Documentation KQL Visualizations Dashboard Best Practices
Tomorrow we'll explore Real Time Dashboards for visualizing streaming data. Eventstream Documentation Event Hub Integration Streaming Best Practices
'{ "SoftDeletePeriod": "90.00:00:00", "Recoverability": "Enabled" }' '{ "DataHotSpan": "7.00:00:00", "IndexHotSpan": "14.00:00:00" }'
'{' ' "SoftDeletePeriod": "30.00:00:00",' ' "Recoverability": "Enabled"' '}'
Tomorrow we'll explore Fabric Real Time Analytics. Query Insights Documentation Performance Tuning Monitoring DMVs
Tomorrow we'll explore Query Insights for monitoring and optimization. Cross Database Queries OneLake Shortcuts Security Model
If you're coming to Fabric Warehouse from a SQL Server or Azure SQL Database background, the T-SQL compatibility is reassuring — CTEs, window functions…
The Fabric Warehouse is the part of Microsoft Fabric that surprised me most in hands-on testing. I expected it to be the Lakehouse's SQL analytics endpoint…
A Fabric pipeline isn't just a sequence of activities — it's an orchestration layer with conditional branching, parameter passing, loops, and error handling…
A month into production-style Fabric testing and Dataflow Gen2 has become my go-to recommendation for teams without Spark expertise who need repeatable data…
The Copy Activity in Fabric Data Factory is the same copy engine as Azure Data Factory — the underlying data movement service optimised for throughput with…
Tomorrow we'll dive deeper into Copy Activity patterns. Data Factory in Fabric Data Pipeline Documentation Pipeline Expressions
Data wrangling — getting messy, inconsistent, real-world data into a reliable clean form — is where most data engineering hours actually go. In Fabric…
Fabric Notebooks have some features I didn't notice until I'd been using them for a few weeks and wish someone had pointed out earlier. Inline data…
Fabric provides a managed Spark experience: Tomorrow we'll dive deeper into Fabric notebooks and their unique features. Spark in Fabric PySpark…
The theoretical benefits of Delta Lake — ACID transactions, time travel, schema enforcement — are easy to describe, but the practical payoff becomes clear…
A Lakehouse combines the best of data lakes and data warehouses: Once created, your Lakehouse has two main sections: The Files section is for unstructured…
OneLake Explorer is a Windows desktop application that lets you browse the contents of your organisation's OneLake the same way you'd navigate files in…
How you structure workspaces in Fabric matters more than most getting-started guides acknowledge. A workspace is the unit of security, capacity binding, and…
The Fabric trial is one of the more generous evaluation paths Microsoft has offered for a data platform — a 60-day, F64-equivalent capacity for free is a…
I've been onboarding several clients onto Fabric over the past few weeks and the first hour is always the same: getting oriented to an interface that's…
Six weeks into the Fabric public preview and I'm past the demo phase — I'm running actual data engineering workloads and discovering what holds up and what…
RLS provides essential data security for multi-tenant and sensitive data scenarios. Tomorrow, I will cover Azure OpenAI function calling patterns.
Item permissions provide the flexibility to share specific artifacts securely. Tomorrow, I will cover Row-Level Security in Fabric.
Proper role management is essential for secure and efficient collaboration. Tomorrow, I will cover Item Permissions in more detail.
Security is an ongoing responsibility. Tomorrow, I will cover Workspace Roles in more detail.
Fabric's capacity unit (CU) model is genuinely different from the per-resource billing in Synapse Analytics, and understanding it properly is the difference…
One of my first questions when evaluating any data platform for enterprise use is "how do I see what's actually running?" — and in the early Fabric…
Deployment Pipelines provide controlled, auditable content promotion across environments. Tomorrow, I will cover Fabric Monitoring.
Git integration in Fabric is something I've been waiting for since the first preview. Power BI's lack of proper version control has been a persistent…
Mirroring simplifies real-time data replication to Fabric. Tomorrow, I will cover Git integration in Fabric.
Dataflows Gen2 provide an accessible way to build data transformations. Tomorrow, I will cover Mirroring in Fabric.
Fabric Pipelines enable robust data orchestration with full control flow capabilities. Tomorrow, I will cover Dataflows Gen2.
Notebooks are the primary development environment in Fabric. Tomorrow, I will cover Fabric Pipelines for orchestration.
Semantic models provide the business logic layer that enables self-service analytics. Tomorrow, I will cover Fabric Notebooks.
Direct Lake is the quiet superpower of Microsoft Fabric, and I think it's underexplained in most of the post-Build coverage. The classic Power BI trade-off…
Of everything announced at Build 2023, OneLake shortcuts might be the feature I find most architecturally elegant. A shortcut is not a copy, not a linked…
Delta Lake isn't a bolt-on feature in Microsoft Fabric — it's the foundational table format for everything. Every table you write through a Spark notebook…
A week after Build 2023, I'm still unpacking what Microsoft Fabric actually means for how we design data platforms. The Lakehouse is the centrepiece — but…
Build 2023 had two dominant themes: 1. AI Everywhere : Generative AI integrated into every product and platform 2. Platform Unification : Simplifying…
At Microsoft Build 2023 on May 23, Satya Nadella announced Microsoft Fabric with the phrase "perhaps the biggest launch of a data product from Microsoft…
All in ONE cohesive experience with ONE security model and ONE business model. At the heart of Fabric is OneLake - think of it as "OneDrive for data." It's…
The fastest approach uses OneLake shortcuts to reference existing data without copying. Run Fabric alongside existing platform during transition.
Both Synapse and Fabric are excellent platforms. The choice depends on your specific requirements, existing investments, and organizational priorities.
A Fabric workspace is the collaboration boundary in Microsoft Fabric—the container where Fabric items (Lakehouses, Warehouses, Notebooks, Pipelines, KQL…
Understanding Fabric licensing helps you plan costs and ensure users have appropriate access. Tomorrow, I will cover Fabric Workspace configuration and…
A Fabric Capacity is a pool of compute resources that powers all Fabric workloads in assigned workspaces. Unlike traditional Azure services where you…
Power BI in Fabric provides seamless BI capabilities that connect directly to your unified data layer. Tomorrow, I will cover Fabric Capacities and pricing.
Real-Time Analytics in Fabric provides powerful streaming capabilities for time-sensitive workloads. Tomorrow, I will cover Power BI integration in Fabric.
The Fabric Data Warehouse provides enterprise SQL analytics without infrastructure management. Tomorrow, I will cover Synapse Real-Time Analytics for…
Fabric's Data Science experience integrates seamlessly with the rest of the platform, allowing you to go from raw data in Lakehouse to deployed models in a…
Synapse Data Engineering in Fabric provides a managed Spark experience that removes infrastructure concerns while delivering the full power of Apache Spark.…
Data Pipelines in Fabric are similar to Azure Data Factory pipelines but with deeper Fabric integration.
The Lakehouse is where most of your Fabric data engineering work will happen. Tomorrow, I will cover Data Factory in Fabric for orchestrating data movement…
OneLake is a single, unified, logical data lake for your entire organization. Think of it as "OneDrive for data" - automatically provisioned when you enable…
This fragmentation creates operational overhead that Fabric aims to eliminate.