Converting Direct Lake Tables to Import: Designing Hybrid Models
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.
Thoughts on data engineering, cloud architecture, and technology. 2205 articles and counting.
Showing 24 of 2205 posts — page 2 of 92
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.
Pre-upgrade validation for Azure PostgreSQL Flexible Server is GA and Extended Support is now billed. An upgrade runbook and a version policy to avoid paying.
Grain is what one row of a table means. Most wrong numbers come from a join or aggregation that quietly changed it. How to declare grain and test it.
Claude hosted on Azure in Foundry now runs web fetch, web search, tool search and an MCP connector for you. Decide which belong behind your own gateway.
Every pipeline gets retried eventually, and a non-idempotent write turns each retry into duplicates. Four patterns that make a write safe to repeat.
Hosted agents in Foundry Agent Service are GA. How they compare with Agent Framework on Container Apps or AKS on identity, networking, cold starts and tracing.
Event-triggered refresh for Fabric materialized lake views trades predictable capacity and clean ordering for freshness. Where events fit and where they don't.
Foundry Model Router picks from OpenAI, Anthropic, DeepSeek, xAI and Meta models. Treat subsets, policy and model logging as governance, not tuning knobs.
GPT-5.6 in Foundry has a 5x price spread across Sol, Terra and Luna. Choose a tier for each workflow step, back it with eval gates, then pick deployment types.
The Agent Framework Harness bundles planning, memory, compaction, approvals and telemetry. When to accept its opinions and when a plain Agent is better.
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.
Why Synapse serverless SQL infers strings as varchar(8000), why Spark-created lake tables behave differently, and where Power BI string contracts belong.
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.
A response cache only speeds up the requests it hits, so the tail stays slow until hit rates get very high. Here's the arithmetic and what fixes p95 instead.
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.
Decide what an agent does when a tool fails, a step runs out of budget or grounding is weak before launch, and make the release check fail without it.
Azure AI Search and Cosmos DB fuse keyword and vector results for you; pgvector doesn't. What owning RRF in PostgreSQL involves, and when it pays.
Before an eval score becomes a product metric, join its verdicts to real outcomes like escalations and re-asks, and check whether failing answers do worse.
Structured outputs fix the shape of a model's answer, not its meaning: a two-layer contract between a Foundry model and the systems that consume it.
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.