A new look and new capabilities in the Capacity Metrics App (Preview)
As announced at FabCon 2026 in Barcelona, we're releasing meaningful enhancements to the Capacity Metrics app in preview, designed to accelerate time to insight. This includes new and enhanced visuals and metrics across the health, compute, and storage pages—alongside improved navigation and a refreshed user interface design. A new item details page builds on the existing item history page, providing key insights for individual items running on the capacity. The aim is to support key user journeys, including: Identifying issues as they happen. Reviewing issues that have occurred over the last two weeks. Identifying risks before they result in throttling. Improved experiences An admin can now land on the health page and quickly identify capacities most in need of review. New metrics introduce easily understandable concepts like percentage of time spent in throttling, which can be compared across capacities and time periods. zation, and various types of throttling – providing the capacity admin a view across capacities to help them keep operations smooth. Once a capacity is identified for further review, the new compute page provides rich detail on the health state of the capacity and the biggest items impacting the capacity for the selected period. Key new visuals include: An updated utilization graph which expresses capacity unit (CU) consumption in CU seconds rather than a percentage, making it easy to see if your capacity has been scaled up or down, while also showing the current throttling state through conditional formatting. A new heat map visual that shows the capacities most utilized/overutilized state for each hour, making it easy to spot daily or hourly patterns. A new CU consumption table, which shows the item impacting the time window being reviewed (to a granularity of 1 hour). The visual shows smoothed CU consumption, meaning this truly reflects the highest impact items for the time being reviewed. on, all within a specified date range. Once an item is identified as a possible cause of high utilization, or if the user just wants to see additional detail on the item, the new item details page provides a 14-day history. The page has been designed from the ground up to give detailed insights which were previously unavailable. One key visual is the new CU utilization chart which shows the impact the selected item had on the overall capacity. Given the new experiences include changes to the existing metrics, it is being released as a preview alongside the existing app generally available experience, allowing time for you to adapt to the new app while still having access to the existing version. When you install the new version of the app, you will see the new preview as an additional option alongside the existing generally available versions of the reports. Getting started To support adoption of the new experience, explore the following resources for each new page: Existing Fabric Capacity Metrics app users will be notified when an update is available. Select Get it from the notification to update your current installation or install the latest version in a new workspace. Alternatively, you can install the app directly from the Microsoft Marketplace. Technical documentation with embedded video guidance: Health page Compute page Storage page Item details page User journey documentation, which explains how the app can be used in different situations. We're excited to put these new capabilities into your hands and look forward to your feedback as we continue evolving the Capacity Metrics experience to help you better understand, manage, and optimize your Fabric capacities.
My workspace governance improvements (Generally Available)
My workspace governance features, which give administrators governance controls over their users' personal My workspaces, are now generally available. As My workspaces continue to be used for business-critical content, organizations need governance capabilities that scale with their environment. These enhancements give administrators greater flexibility to access, manage, and recover content when needed, while enabling automation that reduces operational overhead and improves consistency across the tenant. These enhanced tenant administrator controls for My workspace are also available in government clouds. What's new Two new admin REST APIs make temporary admin access to a personal workspace fully programmable: Grant Admin Temporary Access: grants a Fabric administrator 24-hour access to a user's My workspace. Remove Admin Temporary Access: revokes that access before the 24-hour window ends. Both can be called by a Fabric administrator or by a service principal. The service principal identity must be enabled for Admin API access in your tenant settings. SPN support and these new APIs allow tenant administrators to automate management of tenant users’ My workspaces contents instead of doing it by hand in the Admin Portal. Reminder: Restoring orphaned My workspaces When a user is hard deleted in Microsoft Entra, their My workspace becomes orphaned and moves to a Deleted state, with contents retained for 30 days. During that window, you can restore it with the Restore Workspace API. Important: new workspace name is required when restoring a former My workspace, and you assign a new admin to own the recovered content. Try the Admin controls and new APIs and let us know what you think in the comment section.Custom SQL Pools in Fabric Data Warehouse (Generally Available)
Custom SQL Pools in Microsoft Fabric Data Warehouse are now generally available, along with statement type classification. Custom SQL Pools give administrators more control over how compute resources are allocated across different workloads in a Fabric workspace. You can isolate workloads into separate pools, set maximum resource allocation percentages, and help ensure that one workload doesn’t consume resources intended for another. For example, you can create separate pools for data ingestion, reporting, and ad hoc analysis, then configure the maximum percentage of compute resources each pool can consume. Custom SQL Pools complement the autonomous workload-management capabilities built into Fabric Data Warehouse while giving organizations additional control for predictable and business-critical workloads. Classify workloads by statement type Statement type classification provides a simple way to separate read and write workloads. When configuring Custom SQL Pools, you can classify distributed SQL requests into two categories: SELECT for read queries. NONSELECT for statements such as data loading and modification operations. Fabric creates separate pools for the two statement categories, with an initial maximum allocation of 50% for each pool. Administrators can adjust these percentages based on workload requirements, provided their combined maximum allocation doesn’t exceed 100%. Statement type classification is useful when organizations want to protect interactive reporting capacity from intensive ingestion or data-transformation workloads without relying on application names or connection properties. Custom SQL Pools also support application-based classification using an exact application name or a regular expression. Administrators can select the classification model that best reflects how workloads connect to and use their Fabric workspace. Get started To learn about Custom SQL Pools, supported classifiers, resource allocation, and workload behavior, review the Custom SQL Pools documentation. For instructions to create and configure pools in the Fabric portal, review the Configure Custom SQL Pools in the Fabric Portal documentation.OneLake Security on the SQL Analytics Endpoint
OneLake Security centralizes fine-grained data access for Microsoft Fabric data items and enforces it consistently across engines. Currently in Preview and opt-in per item, it lets you define roles over tables or folders and optionally add Row-Level Security (RLS) and Column-Level Security (CLS) policies. These definitions govern what users can see across Fabric experiences. When you first opt in, a DefaultReader role preserves prior read access. You can remove or adjust this role to transition toward a least-privilege model. OneLake Security in the Context of SQL Analytics At its core, OneLake Security is an item-scoped RBAC and policy layer. You can: Create data-access roles Attach tables or folders Add policies (RLS, CLS, object-level permissions) Membership can be: Explicit – users or groups within the workspace (for example, those assigned the Viewer role) Inherited – via shared items such as a Lakehouse or shortcut Once published, these rules apply to data access from all engines, including the SQL Analytics Endpoint. (See Microsoft Learn.) Understanding OneLake Security for SQL Endpoint The SQL Analytics Endpoint is a read-only surface over Lakehouse data. When OneLake Security is enabled on a Lakehouse, the endpoint enforces those same Lakehouse policies in one of two access modes. Write operations continue to be governed by workspace roles within the Lakehouse experience.” (See Microsoft Learn.) Since there are two access modes, let’s look at how each determines security enforcement: User identity mode (central governance in OneLake) The signed-in user’s identity is passed through to OneLake; table reads are governed entirely by OneLake roles and policies (SQL GRANT/REVOKE on tables is ignored). You still can use SQL permissions for non-table objects (views, procs, functions). This gives 'define once, enforce everywhere' behavior across Power BI, notebooks, Lakehouse, and SQL. Delegated identity mode (SQL-centric control at the endpoint) The endpoint reads OneLake using the item/workspace owner identity; SQL enforces access (roles, GRANT/REVOKE, SQL-defined RLS/CLS, DDM) for the querying user. Use this when you need classic DBA patterns or utilize SQL specific security functions. Ensure the owner has read access in OneLake; otherwise, queries will fail. Differences Between the Modes Tables: User identity: controlled by OneLake roles; SQL GRANT/REVOKE is not allowed on tables. Delegated identity: controlled by SQL; full GRANT/REVOKE. Views / Stored Procedures / Functions: Both modes allow SQL permissions (e.g., GRANT SELECT on views, GRANT EXECUTE on procs/functions). RLS/CLS/DDM: User identity: RLS/CLS are defined in OneLake role UI; DDM isn’t part of OneLake Security. Delegated identity: RLS/CLS/DDM are defined in SQL (security policies, column grants, masked columns). Workspace roles: In User identity, Admin/Member/Contributor bypass OneLake policies; Viewer or read-only sharing is required for enforcement. Shortcuts: Remote Data Ownership and Practical Considerations Shortcuts surface data from another Lakehouse (or external source) into your item. The security policy is enforced at the source; when SQL queries shortcut tables, the system honors the originating OneLake roles/RLS/CLS. Security sync also validates shortcuts, so remote policies aren’t bypassed. Design tips: Document role mappings across items (consumer ↔ source) so troubleshooting is straightforward. Expect validation when shortcut targets change (rename/move); allow brief propagation time. Configuration: Enabling and Setting OneLake Security for SQL Endpoint Opt-in to OneLake Security on the Lakehouse (Manage OneLake security). Review the DefaultReader behavior; remove it or adjust to move to least-privilege. Create roles → select tables/folders → add explicit/virtual members → optionally set RLS/CLS. In the SQL Analytics Endpoint → Security, choose OneLake access mode: User identity (enforces OneLake roles only). Delegated identity (enforces SQL permissions + OneLake security for the owner) Confirm the change in the pop-up. Important switching behavior: Switching to User identity ignores SQL table permissions and can delete existing SQL roles on tables; switching to Delegated stops applying OneLake roles/policies to table reads for all users except the owner. Plan cutovers and back-ups accordingly. How It Works Under the Hood: Security Sync and (Meta)Data Validation When the endpoint runs in User identity mode, a background security sync service keeps SQL aligned with OneLake: it detects role changes, user assignments, and table/policy updates; it translates OneLake RLS/CLS into SQL-compatible constructs and validates that shortcut targets remain consistent, so the source’s policies are honored. Expect non-instant propagation (measure in minutes, not hours) and explicit errors if policies reference dropped/renamed columns—fix in OneLake and re-publish. In Delegated identity mode, SQL is authoritative for the end user access. The endpoint authenticates to OneLake as owner, and the SQL permission model (roles, grants, RLS/CLS/DDM) determines access. Any mismatch between owner access to the Lakehouse and SQL grants will surface as query failures until corrected. Bringing It All Together OneLake Security brings a single, authoritative policy surface to Fabric and lets you decide how the SQL Analytics Endpoint enforces it: Choose User identity when you want to define once in OneLake, enforce everywhere (and ensure workspace users are Viewer/read-only so policies apply). Choose Delegated identity when you need classic SQL control (roles, grants, RLS/CLS/DDM) or to align with existing DBA tooling. By unifying governance across SQL and Lakehouse, Fabric helps teams move faster while staying secure. We’re actively working on additional features, so stay tuned for more updates! Resources To learn more, refer to the OneLake Security for SQL analytics endpoints (Preview), OneLake security overview documentation, and The next evolution of OneLake security (Preview) blog post.
Introducing Rayfin: A new AI-first way to build, deploy, and govern application backends
The way organizations are building apps is changing. AI and coding agents have made it easier than ever to turn an idea into an app. But keeping those applications secure, compliant, and governed has only gotten harder.
Build, deploy, and govern Microsoft Fabric at scale
If you haven’t already, check out Arun Ulag’s hero blog “FabCon and SQLCon 2026 in Barcelona: Building the data foundation for Microsoft Copilot and Agents” for a complete look at all of our FabCon and SQLCon announcements across both Fabric and our database offerings. Getting a data project working is only the beginning. As AI makes it easier for more people to build applications, explore information, and create agents, the harder questions arrive sooner: can the solution be deployed consistently, can a team explain what changed, and will someone notice when a dependency fails? Developers need room to experiment, but they also need a dependable route from an isolated feature branch to a production workload that others can operate. Manual setup, disconnected monitoring, and unclear data context make that route harder to repeat. Administrators face the other side of that growth. More workspaces, users, and workloads mean more decisions about access, compute, spending, and accountability. A capacity spike can affect an unrelated team; a broad security setting may not fit every project. Admins need controls that reflect organizational requirements without turning each development step into a permission request. Developers, in turn, need those boundaries to be understandable and built into their workflows, rather than discovered just before release. Today, we're announcing Microsoft Fabric platform updates to help you tackle both sides of that challenge. They connect operational signals with investigation, make delivery more repeatable, and bring governed discovery into the tools you use. We're also expanding your options for managing compute demand and applying controls across your estate. Introducing observability in Fabric (Preview) A failed job rarely tells the whole story. With the introduction of observability in Fabric, you can connect signals across jobs, workspaces, items, and capacities rather than investigate each in isolation. A Monitor item acts as a single management unit across capacities and your tenant, bringing early detection, contextual investigation, and central management into one operational experience. Unified workspace monitoring (Preview) We're introducing unified workspace monitoring so you can choose which Eventhouse receives your telemetry and consolidate multiple workspaces into that shared store. Instead of monitoring workspaces individually, you can bring related signals together and manage their storage centrally. You control retention and caching policies to suit your investigation and operational needs. When a failure crosses workspace boundaries, for example, you can correlate the telemetry in one place and follow the issue across those boundaries. Most Fabric items will be available at launch, with additional workloads becoming available over time. The new experience also simplifies how you connect monitoring to your own tools. A custom endpoint on the monitoring Event Stream lets you copy data to external or custom destinations, while public APIs support integration with your external observability tools. Simplified, API-backed onboarding makes setup repeatable for automation and agents. You can establish a shared monitoring approach, then extend it to additional workspaces without treating every setup as a separate manual exercise. Refreshed Monitor Hub (Preview) The refreshed Monitor Hub helps you see where attention is needed before opening individual investigations. We're adding ready-made, at-scale views across workloads, jobs, apps, agents, alerts, and capacities, with a centralized health overview and data health monitoring. That broader view helps you spot emerging issues and consider their downstream impact rather than starting with a single failed activity. Capacity consumption and available headroom sit alongside operational signals, so you can consider resource pressure as you assess an issue. Start with the health overview, narrow your focus to the affected area, and move into investigation with that context. The hub connects navigation and operational visibility; the capacity administration actions described later let you respond when the next step is a control change. Agentic investigation and alerting with operations agents and Activator We're also adding the ability to use operations agents to investigate end-to-end causes, develop evidence-backed hypotheses, assess impact, and recommend next steps. You can engage with the investigation, refine its direction, and choose your response. This brings the supporting evidence and relevant dependencies into the conversation instead of leaving you to assemble every clue yourself. Currently this capability can help you investigate pipeline failures, with further support planned. New Activator-powered job alerts notify you about successes as well as failures. You can automate alerts and configure responses, connecting investigation with the operational workflows your team uses. Together, these enhancements help you move from noticing an event to understanding its likely impact and deciding what to do next. Repeatable delivery and governed discovery for developers Operational confidence starts before deployment. The latest enhancements, designed with developers in mind, help you package a solution, review changes, move definitions between environments, and find reusable data worth reusing with fewer manual handoffs between those steps. Introducing deployment plans (Preview) With the deployment plans now in preview as first-class workspace items, you can define the exact deployment order on a visual canvas, with YAML as the source of truth. You can include pre- and post-deployment steps, such as hydrating a lakehouse with a notebook, running a pipeline before dependent items, or validating data after deployment. Your plan follows the solution through Git branch-out, initial sync, updates, deployment pipelines, and bulk import. Preparation and validation become part of the deployment sequence rather than a separate checklist. Bulk Item Definition APIs, quotas, and API limits (Generally Available and Preview) Bulk import and export item definition APIs are also now generally available. You can move multiple definitions in one call; imports automatically determine deployment order and update references for the destination workspace. This supports workspace-as-code, CI/CD, and migration. We're also enhancing the Fabric API platform with a unified quota model and increased limits for core APIs. These updates provide more consistent throttling and quota management while supporting higher-scale automation, CI/CD, and enterprise workloads, making it easier to build and operate Fabric solutions at scale. Git integration enhancements (Generally Available and Preview) The new branch workspace administration delegation capability, now in preview, gives developers a governed, self-service way to create branch workspaces without permission to create workspaces or assign capacity. Administrators define the branch workspace admin profile, including the role, admins, capacity, and delegated settings applied to each new branch workspace, helping teams move faster while maintaining consistent guardrails. We're also expanding the Git workflow with file-level commits for supported items (Preview) and contributor branch switching (Preview). You can commit only the files that are ready while leaving unfinished changes in the workspace, and contributors can switch the Git branch connected to a workspace when administrators enable the capability. Additionally, selective branching, change comparison and commits, and branched workspace relationships, now generally available, helping teams keep feature work focused, review changes before acting, and manage branching from a clearer source control experience. Discover data in OneLake catalog and your coding workflow The OneLake catalog gives you a richer, more granular way to explore and understand data across Fabric before you use it. With the latest updates, you can go beyond finding Fabric items to explore individual tables and columns, review descriptions, and preview the underlying data directly in the catalog. Quick actions, personalized views, and filters, including domains and tags, add business context so you can evaluate whether data is right for your needs before you start working with it (Generally Available). We've also expanded the OneLake catalog search API to return relevance-ranked Fabric items, OneLake tables from lakehouses, mirrored sources, and semantic model tables in one result set (Preview). This brings the same granular discovery to programmatic search, helping applications find relevant data across Fabric regardless of where it lives. OneLake catalog discovery in GitHub Copilot CLI is now generally available through Skills for Fabric. You can find Fabric items and tables from the CLI before writing code, bringing this richer, governed discovery experience directly into your coding workflow rather than requiring a separate search. Bring catalog discovery into Excel and Microsoft Foundry Finally, OneLake catalog in Excel is now in preview, enabling you to discover and analyze Fabric data in your workbooks without copying or moving the underlying source data. OneLake row- and column-level security and Microsoft Purview label-based protections apply, connecting familiar analysis with the protections associated with your source. New OneLake catalog additions in Microsoft Foundry bring enterprise data discovery into your AI development workflow (Preview). With an embedded catalog and a unified view across Fabric and Foundry, you can find trusted data and add it to knowledge, agents, and workflows. Effectively administer capacities and spending As your solutions reach production, capacity administrators need to optimize spend for steady demand while seamlessly managing bursts. With today’s announcements, we are adding new billing choices and capacity controls, as well as tools that help you investigate usage, automate responses, and act across capacities. Introducing on-demand compute and zero-provisioned capacity (Preview) As data and AI workloads grow, organizations need flexible ways to align costs with actual usage. Building on Autoscale Billing for Spark, we're introducing on-demand billing across Microsoft Fabric in preview soon, enabling workloads to scale elastically when needed, minimizing throttling during demand spikes, and allowing you to pay only for the compute you consume. We're also introducing Fabric zero-provisioned (F0), a new entry point to Fabric and OneLake that removes the need to provision compute before getting started. With on-demand billing enabled by default, organizations can immediately access Fabric services and pay only for the resources they use. Together, on-demand billing and Fabric zero-provisioned make it easier to start small, scale as demand grows, and combine consumption-based pricing with reserved or provisioned capacity to optimize both performance and cost. These capabilities will be available in the coming weeks. Whether you're running workloads that tend to spike, experimenting with new projects, or supporting production applications, on-demand billing gives you greater flexibility without requiring upfront capacity planning. Surge protection, overage, and larger capacities (Generally Available) Workspace-level surge protection will be generally available soon. You can set a workspace consumption limit, automatically isolating runaway or non-critical workloads so they don't impact mission-critical workloads or cause capacity-wide throttling. You can manage these controls in OneLake catalog or Monitor Hub, which also allows you to mark mission-critical workspaces exempt from the limit. Additionally, capacity overage is now generally available, letting you use additional paid compute with configured spending thresholds and notifications rather than sizing capacity solely for rare peaks. For sustained high demand, we've added the F4096 and F8192 capacity SKUs (also Generally Available), extending your options for larger workloads. Monitor, act, and automate your capacities Monitoring helps you understand who's consuming resources, identify demand spikes, and ensure critical workloads continue to perform as expected. New capacity metrics app enhancements help you investigate health-state duration, capacity units per second, daily and hourly heatmaps, and top item contributors (Generally Available). Clearer drilldowns support deeper analysis, while chargeback app integration helps you allocate usage. Capacity overview events in Real-Time Hub (Generally Available), with new operation events (Preview) adding workspace- and item-level visibility. These signals enable proactive capacity monitoring by helping administrators identify emerging hotspots, usage anomalies, and resource-intensive operations before they impact users. Connect them to Real-Time Intelligence, Eventhouse, and Activator to automate alerts and actions, retain history for capacity planning, or integrate insights into your existing monitoring systems. With the refreshed Monitor Hub, we're taking the first step toward bringing capacity insights and management actions together in a single experience. Capacity Insights & Actions (preview) lets administrators identify emerging issues and immediately respond by adjusting surge and overage settings, migrating workspaces, or resizing capacity. Use Monitor Hub for monitoring and operational decisions, and the capacity metrics app for deeper usage analysis. Unify governance, security, and control in the OneLake catalog As AI helps more people build with data, tenant admins are responsible for governing an estate that’s growing in both size and complexity. More workspaces, data items, and access requests mean more decisions about what people can share, which settings they can change, and how to protect sensitive data. Admins need to support new projects without turning every decision into a manual review, or losing visibility into how data is used. That balance between enabling teams and maintaining the right guardrails is critical. As Jayakumar Pankajatchan, Distinguished Engineer at KPMG, shared, “Client trust starts with security. Every engagement needs clear data boundaries and strong guardrails, so information flows only where intended. With Microsoft Fabric, we strengthen governance across engagements while enabling teams to deliver insights with confidence at scale.” We’re expanding governance and security in Fabric to help organizations put those guardrails into practice without slowing teams down. With more centralized management, AI-assisted governance guidance, granular policies, and broader network protection, you can give your teams room to innovate while maintaining controls that reflect your organization’s requirements. Introducing policies in Fabric (Preview) With policies in Fabric (Preview), we're introducing precise, attribute-based controls that help organizations enforce governance requirements based on user and data attributes, rather than relying solely on broad settings. Policies enable granular controls for key scenarios, with item creation and workspace security supported at launch and external data sharing coming soon. A centralized policy management experience, monitoring, APIs, and CI/CD integration support policy lifecycle management at scale, supporting more consistent and automated governance across your organization. Figure: Creating an item creation policy with attribute-based conditions and controls. "Fabric’s Item Creation Policies have strengthened our governance controls for Microsoft Fabric, allowing us to scale innovation across the organization by empowering users with the right capabilities while maintaining clear boundaries for platform management and compliance,” said Bernard Beeftink Lead Product Owner, BI, ABN AMRO. Centralizing governance in the OneLake catalog We're expanding the OneLake catalog Govern experience (Generally Available) with centralized governance capabilities that bring management of tenants, domains, capacities, workspaces, tags, and policies into a unified experience. Rich contextual signals, insights, and recommendations help administrators better understand their governance posture and take informed action across their data estate. We're also introducing Govern Skills as part of skills-for-fabric. Govern Skills provide AI-powered guidance across the health, security, and trustworthiness of your data. Govern Skills help administrators identify governance risks, monitor the health of their data estate, and take recommended actions to maintain a secure, trusted, and well-governed foundation for analytics and AI. Outbound access protection expansion (Generally Available and Preview) We've expanded outbound access protection to OneLake shortcuts (Generally Available), along with new coverage for maps in Fabric and operations agents (Preview). You can extend your outbound controls across these experiences while building on existing foundations such as Microsoft Entra, Private Link, customer-managed keys, and workspace IP firewall rules. FQDN allowlist for outbound protected workspaces (Preview) FQDN support for Spark simplifies secure connectivity for organizations using OAP-enforced Fabric workspaces, where Private Endpoints are often required to access dependent services. Instead of creating and managing Private Endpoints for every resource a Spark workload needs to reach, administrators can use domain-based network controls to securely enable connectivity through approved FQDNs. This reduces networking complexity, lowers operational overhead, and accelerates onboarding while maintaining enterprise security and compliance requirements. This capability will be available in the coming weeks. Fabric availability in Microsoft 365 Government Community Cloud High (GCC High) We are also expanding Microsoft Fabric to Microsoft 365 Government Community Cloud High (GCC High) customers. Support for GCC High extends Fabric to organizations that require U.S. sovereign cloud environments and compliance with frameworks such as DoD Impact Level 4, CJIS, DFARS, and NIST 800-171. Put the updates to work Start with the friction you encounter most: investigating failures, reproducing deployments, finding data, or managing demand and controls. Our updates connect those responsibilities without requiring every team to use the same workflow. Match adoption to your readiness requirements, then extend your approach as your data estate grows. In addition to the announcements above, we are also rolling out a broad set of innovation across Fabric. For a broad overview of all these announcements, read Arun Ulag’s hero blog “FabCon and SQLCon 2026 in Barcelona: Building the data foundation for Microsoft Copilot and Agents.” If you want a more detailed look, visit the Fabric September 2026 feature summary blog, the Power BI September 2026 feature summary blog, and the latest posts on the Fabric Updates channel and the Azure Data Tech Community blog channel.On-premises data gateway August 2026 release
The August 2026 release of the on-premises data gateway is version 3000.330. The new August 2026 release of the on-premises data gateway (version 3000.330) continues our commitment to delivering secure, reliable, and manageable connectivity between on-premises data sources and Microsoft Fabric services. This release includes improvements focused on gateway manageability, operational visibility, enterprise governance, and platform reliability, helping organizations manage their gateway environments with greater confidence. It also brings compatibility updates for the August 2026 release of Power BI Desktop, ensuring consistent query execution and a seamless experience between Power BI Desktop and cloud-based refresh scenarios. Additionally, this release includes enhancements across security, authentication, diagnostics, and overall platform quality. We have received a few questions from community members regarding CVEs identified in third-party components used by the on-premises data gateway. As part of our ongoing commitment to security and reliability, we continuously evaluate and update third-party dependencies. These updates are incorporated into gateway releases following comprehensive security reviews, compatibility validation, and product qualification testing to help ensure a secure, stable, and reliable experience for customers. Security and dependency updates are delivered through regular gateway releases. We recommend keeping your gateway deployment up to date to benefit from the latest security enhancements, dependency updates, performance improvements, and platform reliability fixes. Power BI Desktop compatibility This update brings the on-premises data gateway up to date with the August 2026 release of Power BI Desktop. Download on-premises data gateway (standard mode) Download on-premises data gateway (personal mode) This version of the gateway will ensure that the reports that you publish to the Power BI Service and refresh via the gateway will go through the same query execution logic/run-time as in the August version of Power BI Desktop. Next steps Upgrade to version 3000.330 to take advantage of the latest security, authentication, and diagnostics improvements. We encourage you to share feedback and feature requests through the Power BI Ideas forum to help shape future gateway investments.Find the SQL Team at SQLCon/FabCon Europe 2026
Twenty sessions. Four days. One short link! The Microsoft SQL product team is heading to Barcelona for SQLCon Europe 2026, September 28 to October 1, co-located with FabCon Europe. The people building SQL Server, Azure SQL, and SQL database in Fabric are presenting what's new and the roadmap, and then sticking around to answer your questions and discuss your ideas and problems-to-solve. Bookmark this or remember to URL to find it later: aka.ms/sqlsessions By the way, if you haven't registered yet and have decided you want to come, you can register online now! Find the SQL team Here's where we will be, broken down by day. SQLCon TV topics and guests are still being finalized. The times are included in the following schedule so you can save the slots and check back for details. Monday, 28 September Time Session Speakers ID 09:00-17:00 Modernizing Your SQL Estate: From SQL Server to Azure SQL and Fabric for AI-Ready Applications (full day workshop) Borko Novakovic, Dr. Dani Ljepava, Vladimir Ivanovic E Tuesday, 29 September Time Session Speakers ID 11:15-12:15 CORENOTE: The Roadmap for Microsoft SQL: Ground to Cloud to Fabric Priya Sathy, Bob Ward, Anna Hoffman T03 13:30-14:30 Database Hub in Fabric: A Control Plane for your Entire Database Estate Patrick LeBlanc, Charles Webb T14 14:45-15:45 SQL Database in Fabric: Real-World Scenarios and Solutions Pam Lahoud T28 16:15-17:15 How SQL Runs SQL: Using AI for SQL SDLC and live sites Vandana Mahtani, Kedar Dubhashi T46 17:00-17:20 SQLCon TV: Community leaders react to keynote announcements at SQLCon Anna Hoffman, Monica Moorehouse, Rob Sewell SQLCon TV Wednesday, 30 September Time Session Speakers ID 08:45-09:45 From Transactions to Impact: Activating SQL Data in Fabric Nikola Zagorac, Anna Hoffman W05 10:00-11:00 Running Mission-Critical Systems on Azure SQL Hyperscale- Enable AI, CoPilot, & Enterprise Features Mukesh Kumar, Priya Sathy W15 10:30-10:50 SQLCon TV: Shireesh Thota, Microsoft VP + Matt Aslett from ISG Shireesh Thota, Matt Aslett SQLCon TV 11:30-11:50 SQLCon TV: SQL VP, Priya and Bob talk winning with Azure SQL Database Hyperscale Priya Sathy, Bob Ward, Anna Hoffman SQLCon TV 11:30-12:30 Database Agents: A New Way to Manage Databases in Fabric Patrick LeBlanc, Derek Wilson W24 11:30-12:30 Data Productivity Tour: Query, Deploy, Optimize Erin Stellato W26 13:00-13:20 SQLCon TV: What happened: 10 years in 20 minutes Bob Ward, Patrick LeBlanc, Anna Hoffman SQLCon TV 14:00-14:20 SQLCon TV segment, details coming soon Jesse Sullivan SQLCon TV 15:00-16:00 Top 10 SQL Features for Developers you might have missed! Pooja Kamath W48 15:00-16:00 AI Threats, Stronger Security: New Data Security Innovations in Azure SQL Pieter Vanhove, Sravani Saluru W54 Thursday, 1 October Time Session Speakers ID 09:15-10:15 SQL Server & Azure SQL AMA TBA N/A 10:30-11:30 Mastering Performance for Microsoft SQL with AI Erin Stellato, Anna Hoffman TH02 12:00-13:00 Meet & Greet with the hosts of “Guy in a Cube” and “Data Exposed” Adam, Marthe, Patrick, and Anna CZ 12:00-13:00 Azure SQL Hyperscale: The Cloud Database for the era of AI Bob Ward, Borko Novakovic TH15 13:00-13:20 SQLCon TV x Data Exposed: A look back with SQL LT, what’s new across Microsoft SQL at SQLCon/FabCon Anna Hoffman, Priya Sathy, Charles Webb, Mukesh Kumar, Borko Novakovic SQLCon TV 15:30-16:30 Unlock SQL Server Migration and Modernization in the Era of AI Dr. Dani Ljepava, Vladimir Ivanovic TH39 Where to start Start with the corenote on Tuesday at 11:15. Priya Sathy, VP of Microsoft SQL, will join Bob and me to cover where SQL is going across SQL Server, Azure SQL, and Fabric SQL. Everything else on this schedule goes deeper. Between sessions Come find us at the Microsoft booth and in the Community zone. Bring the migration you’re stuck on, the query that won’t go faster, or the feature request you’ve been sitting on. The booth conversations are always the highlight of the trip for me, so please stop by. Room assignments are not published yet. The venue signage maps sessions with session IDs like T03 and W54, so note the ID rather than a room number, and check aka.ms/sqlsessions onsite. Explore the full conference details for the latest information: FabCon Europe & SQLCon Europe 2026 programme. See you in Barcelona.Upcoming changes to legacy Teams and Outlook activities in Fabric Data Factory pipelines
Beginning October 30, 2026, users will no longer be able to add new legacy Teams or legacy Outlook activities to pipelines. These legacy activities will no longer appear as options when users add new activities to a pipeline. Existing legacy activity instances can still be edited and used in existing pipelines. New notification scenarios should instead use the modern Microsoft Teams and Outlook 365 Email activities.
