AI Readiness · 1
Fabric Updates
Aug 18, 2026
2/5 · Tier B
AI ReadinessReport Authoring
announcement
<p><strong>Fabric data agents now render conversational charts with Fabric Visuals in preview.</strong> Responses can use line, bar, stacked bar, pie, scatter, area, and stacked-area charts across lakehouses, warehouses, and Power BI semantic models.</p><p>Visuals are enabled by default and can be requested explicitly or guided through agent instructions. The change improves formatting, legends, tooltips, markers, and axis scaling, but the extract does not describe preview limitations, cost, accessibility coverage, or accuracy controls.</p>
Preview data-agent visuals improve rendering consistency, but the announcement provides few limitations, costs, or governance details.
Governance · 5
<p>45 features - 19 must-know - 24 worth knowing.</p><ul><li>Git Integration and Deployment Pipeline – Item level permission restriction</li><li>Fabric Runtime 2.0 (Generally Available)</li><li>Data Agent is migrating from Assistants API to Responses API</li><li>CI/CD 2.0 with DacFx (Preview)</li><li>OneLake security improvements for SQL analytics endpoints (Generally Available)</li><li>Git Integration – Workspace Relation API (Preview)</li><li>Resource instance rules for OneLake (Generally Available)</li><li>Native Execution Engine performance improvements</li><li>Data Agent orchestrator upgraded to GPT 5.1</li><li>Identity columns with identity insert (Generally Available)</li><li>GPU Query Acceleration (Preview)</li><li>Secure data ingestion with COPY INTO and Workspace Identity (Generally Available)</li><li>Eventstream MQTT connector (Generally Available)</li><li>Reference data enrichment in Eventstream (Preview)</li><li>Eventstream observability in Workspace Monitoring re-enabled with per-Eventstream control (Preview)</li><li>Secure Azure Event Hubs Connections in Eventstream with Workspace Identity (Preview)</li><li>Workspace Outbound Access Protection (OAP) for Operations Agent (Preview)</li><li>Upgrade Dataflow Gen1 to Dataflow Gen2 (CI/CD) using the Upgrade Wizard (Preview)</li><li>Migration Assistant for SQL database in Fabric (Generally Available)</li></ul>
19 must-know of 45 features
<p><strong>Anonymous data access</strong> for Fabric Apps is available in preview. A tenant administrator first enables the capability for the organization or selected security groups; an app’s data model then explicitly grants the anonymous role operations such as read or create.</p><p>The layered design supports focused public experiences while keeping other entities and operations authenticated. Anonymous users have no identity claims, so the model must expose only minimum necessary fields and operations. Public endpoints also require protection against untrusted input, spam, automation, and unexpected traffic.</p><p>The capability is unsuitable for personal, confidential, financial, or internal business data. Because it is preview, I would validate behavior, monitoring, abuse controls, and rejected operations before production use.</p>
Preview anonymous access changes Fabric App security boundaries, with explicit tenant, model-role, and operation controls.
<p><strong>Eventstream workspace identity authentication for Azure Event Hubs</strong> is available in preview. Eventstream uses the Fabric workspace identity to obtain a Microsoft Entra ID token instead of storing an Event Hubs shared access key or connection string.</p><p>An administrator grants the workspace identity the <strong>Azure Event Hubs Data Receiver</strong> role through Azure RBAC. Developers then select Workspace identity when configuring the Eventstream source. Permissions can be changed at the Event Hubs namespace without recreating the connection, while separate workspaces retain separate access boundaries.</p><p>The feature removes manual secret rotation, but it remains preview functionality and requires administrators to configure both the workspace identity and Azure resource permissions.</p>
Preview identity-based Eventstream authentication reduces secret management and enables workspace-scoped Azure authorization.
<p><strong>Fabric workspace CMK APIs are generally available.</strong> Administrators can assign or rotate an Azure Key Vault key, inspect encryption state, reset a workspace to Microsoft-managed encryption, and list tenant workspaces with encryption details.</p><p>The APIs use versionless key URIs, so key rotation uses the same assignment operation. Microsoft Entra authentication and existing workspace or tenant-admin permissions govern access, while status values support auditing and drift detection.</p>
GA APIs make workspace CMK provisioning, rotation, auditing, and tenant-wide encryption governance automatable.
<p><strong>Fabric integration workloads use three primary connectivity patterns:</strong> a Microsoft-managed VNet data gateway, a customer-managed on-premises data gateway, or a direct cloud connection without a gateway.</p><p>Choose based on where the source resides and whether Fabric must cross a private network boundary. VNet gateways suit private endpoints and ExpressRoute-reachable sources without gateway virtual machines; standard gateways suit on-premises or privately hosted sources requiring customer-managed clustering and operations; direct connections suit publicly reachable cloud services.</p><p>This guidance covers Dataflow Gen2, pipelines, Copy Job, Mirroring, semantic models, and paginated reports. Notebooks and Spark workloads use Fabric Managed VNet and follow a different model.</p>
The guide clarifies gateway selection and private-network trade-offs across Fabric integration workloads, but adds limited new behavior.
Real-Time Intelligence · 3
<p><strong>Activator</strong> handles immediate responses to published Business Events, such as alerts, pipelines, notebooks, flows, or User Data Functions. <strong>Eventhouse</strong> stores events as queryable history for KQL analysis, operational dashboards, recurrence analysis, and machine-learning features.</p><p>The recommended pattern is fanout: publish once, then let Activator and Eventhouse consume the signal independently. This separates detection from operational response and preserves an analytical record without coupling publisher logic to downstream teams.</p>
The article gives a practical event-driven decision pattern for immediate actions, durable history, or both.
<p>The <strong>KPI visualization</strong> is generally available in Fabric Real-Time Dashboards. A numeric result from a KQL query can be displayed as a Number, Bar, Gauge, or Donut, with configurable minimum and maximum scales.</p><p>Authors can define healthy, warning, and critical ranges, reverse the threshold direction for metrics such as latency, format values and units, and add reference lines for SLAs or operating limits. The visual requires Fabric-enabled capacity and Editor permissions on the dashboard.</p>
GA KPI visualization adds configurable ranges, targets, formatting, and four display modes for operational dashboards.
<p><strong>Eventstream observability</strong> now uses a per-eventstream <strong>Log Eventstream activity</strong> toggle instead of enabling monitoring across an entire workspace. Monitoring is off by default, so teams can select only critical pipelines.</p><p>Enabled streams emit throughput and error metrics approximately every minute, plus node-status data approximately every six hours, into three monitoring KQL tables. Workspace Monitoring and its monitoring Eventhouse must already be provisioned. Diagnostic logs and broader connector coverage are not yet available.</p>
Per-eventstream observability adds practical monitoring controls and KQL metrics, but remains preview with limited diagnostics.
Warehouse · 4
<p><strong>IDENTITY columns</strong> are generally available in Fabric Data Warehouse, with support for <strong>IDENTITY_INSERT</strong> and reseeding. Tables can generate system-managed numeric surrogate keys during normal inserts, while migration or controlled backfill operations can explicitly preserve existing identity values.</p><p>Identity values are unique but not guaranteed to be sequential or gap-free because Fabric Warehouse generates them during distributed, parallel execution. This preserves load throughput but makes them unsuitable for assumptions about contiguous numbering.</p>
Fabric Data Warehouse identity insert and reseeding reach GA, directly improving migration and surrogate-key loading patterns.
<p><strong>Custom SQL Pools are preview workload-governance boundaries for Fabric Data Warehouse.</strong> They cap the share of warehouse resources available to classified workloads, allowing administrators to trade query latency for more predictable contention and consumption.</p><p>A bursty query scaling to 10 vNodes for 10 seconds can represent roughly 600 billed vNode-seconds under a one-minute minimum. A pool limiting it to five vNodes may extend runtime to 20 seconds while reducing the comparable allocation to roughly 300 billed vNode-seconds. This is not a spending cap or monthly budget limit.</p><p>Disabling <strong>Optimize for Reads</strong> may reduce cache-related consumption because cached resources otherwise remain allocated for at least five minutes, but query performance must be measured afterward. Background workloads also benefit from 24-hour smoothing behavior.</p>
Preview SQL Pools provide quantified workload isolation and consumption trade-offs, including billing-window and cache-retention implications.
<p>The preview <strong>Fabric Data Warehouse MCP Server</strong> gives compatible agents a managed way to execute T-SQL against Fabric Warehouses and SQL analytics endpoints. It supports a global endpoint or an item-scoped endpoint, with Microsoft Entra ID OAuth 2.0 authentication and the user’s existing Fabric and SQL permissions.</p><p><strong>Skills for Fabric</strong> provide task-specific instructions for warehouse authoring, consumption, and operations. Skills guide the agent; the MCP server executes queries and returns live results, allowing iterative validation, error correction, schema exploration, and query-performance investigation through queryinsights.</p><p>The feature is preview and exposes execution against live data. Existing permissions still constrain the agent, but organizations must govern which MCP clients and users can perform DDL, DML, or diagnostic queries.</p>
Preview remote MCP execution and Fabric-specific skills let agents query, author, validate, and diagnose warehouses under existing permissions.
<p>A maintainable Fabric Data Warehouse medallion design gives each layer one job: <strong>Bronze</strong> preserves traceable source data, <strong>Silver</strong> cleanses and conforms it, and <strong>Gold</strong> shapes trusted business outputs for analytics.</p><p>The implementation uses patterns such as <strong>COPY INTO</strong> for bulk Bronze ingestion, CTAS and INSERT...SELECT for Silver transformations, MERGE for incremental updates, and fact, dimension, view, or aggregate structures in Gold. Metadata such as ingestion timestamps and source filenames supports replay and auditing.</p><p>The main operational risks are cleansing too early, non-repeatable transformations, tiny trickle loads, uncontrolled schema changes, and business logic leaking into reports. Sensitive fields should be protected or removed before Gold consumption.</p>
Concrete T-SQL medallion patterns separate raw ingestion, cleansing, quality gates, and business-ready warehouse outputs.
