Summary Currently, Microsoft Fabric Lakehouses store data in OneLake, logically centralized by region and capacity. However, there is no Microsoft-supported mechanism to transfer or migrate Lakehouse data across tenants, even when both tenants are owned or controlled by the same organization. This idea proposes a Microsoft-managed, support-driven cross-tenant transfer capability, where access to both tenants can be validated and a secure migration can be performed. Problem Statement Many organizations operate multiple Microsoft Entra tenants due to: Mergers and acquisitions Regional or regulatory separation Divestments or tenant consolidations Managed services and partner-led implementations Today, moving Fabric Lakehouses or OneLake data between tenants requires manual, unsupported, or fragile workarounds, such as: Exporting and re-ingesting data Custom pipelines with duplicated storage costs Breaking lineage and governance metadata Additionally: Governance objects (lineage, shortcuts, permissions) are lost Support cannot officially validate or assist with cross-tenant migrations Large datasets make re-ingestion slow, risky, and expensive Proposed Solution Enable a Microsoft-supported cross-tenant OneLake transfer process, initiated via a support ticket or controlled workflow, with the following characteristics: Validation of administrative access to both source and target tenants Same-region or approved cross-region transfers Secure, audited data movement at the OneLake level Optional inclusion of: Lakehouse metadata Directory structure Table definitions Shortcuts and references (where applicable) This could be implemented as: A Microsoft Support-assisted operation A Fabric Admin or Tenant-level migration workflow Or a future Fabric-managed migration service Business Value Reduces risk and cost for tenant consolidation projects Enables cleaner M&A and divestment scenarios Preserves governance, lineage, and Fabric-native structures Avoids data duplication and unnecessary storage costs Aligns with OneLake’s vision as a unified, logical data lake Who Would Benefit Enterprises with multiple Entra tenants Partners and MSPs managing Fabric for multiple customers Organizations with M&A activity Regulated industries needing structured tenant separation Additional Notes This feature would not need to be self-service initially. A controlled, support-driven process would already deliver significant value while maintaining security, auditing, and governance guarantees. ... View more

Currently, Power BI/Fabric supports email notifications only for refresh failures, but there is no capability to alert users when refresh operations run for an extended duration or get stuck in progress, which can delay issue detection and impact business reporting. This lack of proactive visibility creates challenges in monitoring large-scale workloads, especially in scenarios involving Dataflow Gen2, pipelines, or semantic models where refreshes may remain locked or inactive for long periods without failure notification.    Proposed Feature: We request the introduction of proactive email notifications for long-running or stuck refresh operations based on configurable duration thresholds, along with the ability to define custom timeout limits at dataset/dataflow/pipeline level. This enhancement would enable early detection, improved operational monitoring, and the option to take automated actions such as alerting, retrying, or canceling refreshes, thereby improving reliability and capacity management ... View more

- When connecting to a Fabric Lakehouse SQL endpoint using SSMS 22, tables are not visible and queries return misleading "permission denied" or "database not available" errors. - The same connection and queries work correctly in SSMS 20. - This appears to be a TDS protocol or metadata compatibility issue between SSMS 22 and Fabric's SQL endpoint. - Request: Update SSMS 22 or Fabric's SQL endpoint for full compatibility. ... View more

Description Hi community, I’d like to raise a feature request related to governance and connection management in Microsoft Fabric, specifically for Email (Office 365 Outlook) and Microsoft Teams connectors used in Data Factory pipelines. Scenario In enterprise environments, it is common to require: Centralized management of connections (e.g., Email / Teams) Reuse of the same connection across multiple workspaces (Dev/Test/Prod, or multiple domains) Consistent governance, including credential lifecycle management and auditing However, when working with Fabric pipelines that use Outlook or Teams activities, we observed the following behavior: When deploying a pipeline to another workspace, the activity becomes inactive A new user authentication connection must be created in the target workspace If the connection is not recreated, deployment fails or the activity cannot run This behavior is documented here: Outlook activity → Microsoft Learn Teams activity → Microsoft Learn Current Behavior (Documented Limitation) As per official documentation: Outlook / Teams connections are tied to user authentication When moving pipelines across workspaces: “The activity will be inactive in the target workspace until you create a new user authentication connection there” [learn.microsoft.com] Same behavior applies to Teams activity [learn.microsoft.com] This effectively means: Connections are scoped to the workspace Connections are not reusable across workspaces Each workspace requires manual reconfiguration Expected Behavior From an enterprise governance perspective, we would expect: Ability to define centralized, reusable connections Secure sharing of those connections across multiple workspaces Support for CI/CD scenarios without manual re-authentication Reduced duplication of connections and credentials Why this matters Other connection types in Fabric (e.g., cloud connections) are moving toward shared and governed models, but Email and Teams connectors still require per-workspace authentication. This creates an inconsistency in the platform’s governance model, especially for enterprise adoption. Feature Request We would like to request support for: Secure, reusable Email and Teams connections Cross-workspace connection sharing Centralized management (similar to cloud connections / gateways) CI/CD-friendly connection lifecycle ... View more

In a Matrix Visual, the property "+/- icons" can be disabled. However, when publishing the report, the "+/- icons" property stays enabled.  It needs to be disabled from web experience to persist this setting. ... View more

Currently, sending email subscriptions to external recipients is supported only when the workspace is backed by a paid Premium capacity, and not in trial or non‑Premium environments [Email subs...soft Learn | Learn.Microsoft.com] This limits customers from validating external reporting and collaboration scenarios during trials.   Allow external email subscriptions in: Trial environments Non‑Premium (Pro/PPU) workspaces (with controlled limits) Impact Enables proper feature evaluation during trial Improves adoption for external collaboration scenarios ... View more

Suggeting an improvment in richness and behaviour for the right hand side tab inside the notebook UI. For example, when Table of Contents is active, it intermittently disappears when Ctrl + F to search/replace.   There are alot of inconsistencies in behaviour for toggling Search, Keyboard Shortcuts, Code Snippet Library, and Table of Contents.  ... View more

Fabric does NOT provide There is currently no: “Initial snapshot completed” status Boolean flag or milestone UI badge changing from Initializing → Completed Event surfaced in the Mirrored Database UI Metadata column showing snapshot phase Once mirroring starts, everything is simply “Running” forever. This is by design in the current Fabric Mirroring implementation.   There is no system table, DMV, or metadata table inside the mirrored database that exposes replication status, snapshot completion date, or replication phase.   This is a current limitation of Microsoft Fabric Mirroring.   Request you to resolve at the earliest. ... View more

Today, Microsoft Fabric Data Pipelines primarily support time‑based scheduling (hourly, daily, etc.) and manual triggers. However, many real‑world data integration scenarios are event‑driven, especially when source data resides in SharePoint Online, OneDrive, or Microsoft 365 storage. A common enterprise scenario is: An Excel file is uploaded or modified in a SharePoint document library Downstream data pipelines should immediately process the updated data Currently, achieving this requires: External orchestration tools (Power Automate, Logic Apps) REST API calls with Entra ID admin consent Custom governance approvals and additional operational complexity This introduces friction, especially for organizations that want to keep all orchestration natively inside Microsoft Fabric. Proposed Feature / Enhancement Introduce native event‑based triggers for Microsoft Fabric Data Pipelines, similar to Azure Data Factory and other event‑driven platforms. Example Trigger Types File Created File Modified File Deleted Example Event Sources SharePoint Online document libraries OneDrive for Business Fabric OneLake (Files / Lakehouse folders) Future extensibility: Azure Blob Storage, ADLS Gen2 Example Use Case When an Excel file is modified or replaced in a SharePoint folder, automatically trigger a Fabric pipeline to ingest, validate, and transform the data. Flow User updates Excel file in SharePoint Fabric detects file modification event Pipeline is triggered automatically Data is ingested into Lakehouse / Warehouse Downstream notebooks or semantic model refreshes run No external automation, REST calls, or Power Automate flows required. Suggested UX / Configuration Add “Event Trigger” as a pipeline trigger type (alongside Schedule & Manual) Allow users to: Select source (SharePoint, OneLake, etc.) Provide folder path and file pattern (e.g., *.xlsx) Choose event type (Created / Modified) Support basic debounce logic (e.g., ignore multiple changes within X minutes) Optionally expose file metadata as pipeline parameters (file name, modified time, user) ... View more

I ran into an issue with scheduled refresh on a dataset that uses Personal Cloud Connections with SharePoint files. In Power BI Desktop, all queries refreshed fine. I then published to the Service and set up scheduled refresh. In app.powerbi.com, the dataset showed errors like “scheduled refresh is disabled because at least one data source is missing credentials,” even though all my SharePoint cloud connections and credentials were valid. After a lot of troubleshooting I discovered the real root cause: in Power Query I had added one new table whose Source step still pointed to a local desktop path (C:\…) instead of a SharePoint URL. Every other query used SharePoint URLs and Personal Cloud Connect, but this one local file prevented the entire dataset from refreshing. The Service error message never indicated that the problem was a local file path mixed in with cloud sources, so I had to manually inspect each query’s Source step to find it. Feature request: When a dataset contains a mixture of cloud‑connected sources (e.g. SharePoint/OneDrive) and unsupported/local sources (e.g. local file paths without a gateway), please show a specific, actionable error message. For example: “One or more of your data sources is not cloud‑connected (for example, a local file path). Go back to your Power BI Desktop model and check the Source step for each query.” Ideally, the message would either list the offending queries or at least clearly call out that a local/not‑cloud‑reachable source exists. This would save a lot of time versus the current generic credential/gateway error, especially for models that mostly use cloud sources with Personal Cloud Connections. ... View more

Today, when creating an Activator rule from a Power BI visual, we can set the evaluation frequency (for example, 1 evaluation per hour), but we cannot control when those evaluations happen during the day or week. Two related gaps:   No time window control. Alerts run 24/7 at the chosen frequency. There is no way to scope evaluations to specific days or hours of the day. No start time control. The evaluation cycle appears to anchor to the Activator creation time, so the rhythm of the schedule depends on when the rule was saved rather than a business-meaningful anchor the user picks.   Proposal Extend the frequency configuration to also support: Time windows: pick the days of the week and the hour range during which the alert should evaluate (for example, Mon to Fri, 09:00 to 18:00). Custom start time: let users set an explicit start time for the evaluation cycle instead of defaulting to the creation timestamp.   Example scenarios A retail operations team only needs inventory alerts during store hours. A support team wants SLA breach alerts only during staffed shifts, not overnight. A finance team wants market-hours-only evaluations for trading dashboards.   Why it matters Cuts noise from off-hours alerts that no one is around to act on. Reduces unnecessary evaluation volume and the capacity it consumes. Aligns Activator's behavior with how teams actually operate. ... View more

This is one of the more basic features that isn't in Power BI, but is available in competitor software (e.g., Alteryx, etc.). Power BI Table visualizations currently can't conditionally format row font sizes. We should add to the font formatting to include font size. Font weight, styles, etc., would be nice too, but I think font size should be prioritized. ... View more

Very similar to what was avaiable in Azure Analytics Service.  I am look for real-time user login activity and what model are being used, how much memeory and CPU is being consumed.  This will also allow me better understand if my current F-SKU is meeting our business needs and when to scale to next SKU before I actually get the 90% warning messages. ... View more

💓 Yes please to custom access messaging - upvote the socks off this post! 💓 We stilll have a gap in the access messages feature in Power BI in 2026 - lets see if we can muster enough upvotes to change it! Semantic models can have a unique access message on them, however workbooks cannot have a unique access message on them. If you host hundreds of Power BI reports, the administration on the dreaded default "I would like access" message is no fun. Users today have their own sharepoints, documents, why cant we have the functionality on customization of that dreaded access message?     Yes you can use the app to change it in a workspace, but the issue with that is only one app per workspace is allowed. Why should users opt to add more workspaces making topologies more complex when they need not have to be that way. Org apps is introduced 2026 which allows multiple apps per workspace - but only one access message is allowed. This should be a standard in apps if were moving that way, each app should be capable of having a customized message per app. We get user complaints all the time on this subject, from the many posts even this one as solved so do others.   Two things i would like this idea to change which would give a gain to anyone who administers a workspace. 1. Workbook access message customization for those who dont want to use the app as standard in 2026. 2. Org apps to include custom message per app as standard in 2026.   What do we need to facilitate change? Upvotes, encourage all your users to upvote this proposal and add some comments, lets see in 2026 if we can fix this issue! 💪 ... View more

Hi team, I would like to propose a feature enhancement around Fabric Data Agents and their integration with Power BI.   Problem Statement Currently, Fabric Data Agents are primarily accessible through the Copilot interface. While this works well for exploratory analysis, it introduces limitations for production-grade and embedded analytics scenarios where UX control is critical. In real-world deployments (especially client-facing dashboards), relying on the Copilot pane: restricts customization of the user experience limits integration with report visuals makes it difficult to embed conversational analytics seamlessly within applications Proposed Enhancement Enable native integration of Fabric Data Agents directly within Power BI reports/dashboards, without requiring the Copilot interface. This could include: A dedicated “AI Visual” or component that can be placed on the report canvas Ability to bind a Data Agent to a semantic model used in the report(Currently, we have in Copilot, but adding a data agent directly would be a plus) Support for interactive querying directly within the dashboard (e.g., chat or prompt-based input) Mechanisms for agent responses to interact with visuals, such as: dynamically filtering visuals generating insights tied to selected data context augmenting dashboards with narrative explanations Why this matters There is a growing demand for conversational + visual analytics in a unified experience. Many enterprise use cases (e.g., customer segmentation, profitability analysis, behavioral insights) require: structured dashboards for KPIs and an AI layer for ad-hoc reasoning Currently, developers are forced to build custom hybrid architectures (Power BI Embedded + external AI layer) to achieve this, which increases complexity and reduces adoption of Fabric-native capabilities.   Suggested Capabilities / API Considerations Programmatic access to Data Agents (REST / SDK) Event hooks between report interactions and agent context Embedding support for agent interaction in Power BI Embedded scenarios Ability to pass filter context from report → agent and vice versa Impact This would: significantly enhance Power BI as an AI-first BI platform reduce the need for external custom implementations unlock new enterprise use cases for embedded analytics and intelligent dashboards I believe this feature would be a major step toward making Fabric a truly unified platform for data, AI, and business intelligence. Would love to hear if anything like this is on the roadmap or being considered. Thank you. ... View more

Description   Power BI currently does not provide native support for advanced statistical visuals such as violin plots and box plots, and while histograms can be approximated using binning or custom visuals, they are not available as fully integrated, out-of-the-box visualizations. Users often depend on external tools such as Python, R, or marketplace visuals, which introduces additional complexity, performance considerations, and usability limitations. Power BI provides strong standard visuals such as bar charts, line charts, and pie charts, which are effective for basic comparison and trend analysis. However, for deeper analytical scenarios involving data distribution, variability, and anomaly detection, advanced statistical visualizations are essential. I propose introducing built-in support for advanced statistical visuals directly within the visualization pane. These visuals should be fully integrated with the data model, support slicers, cross-filtering, drill-through, and interact seamlessly with other visuals in the report. Additionally, they should include intelligent defaults such as automatic binning, outlier detection, and distribution estimation. Key Visuals and Their Importance   Violin Plot A violin plot combines the features of a box plot with a density curve, providing both summary statistics and the full distribution shape of the data. Usefulness Helps identify data distribution patterns Reveals multimodal distributions Supports deeper comparison across categories Box Plot A box plot summarizes data using quartiles, median, and outliers, making it a fundamental tool for statistical analysis. Usefulness Clearly identifies spread and variability Detects outliers effectively Enables comparison across multiple groups Histogram A histogram represents the frequency distribution of a continuous variable and is a foundational tool for exploratory data analysis. Usefulness Helps understand overall data distribution Identifies skewness and normality Supports statistical modeling and validation Advanced Use Cases Salary distribution analysis in HR analytics dashboards Customer spending pattern analysis and segmentation Product performance variability across regions or categories Detection of anomalies in financial or operational datasets Understanding data distribution before applying predictive or machine learning models Benefits Enables deeper statistical analysis directly within Power BI Reduces dependency on external tools such as Python or R Improves performance by eliminating reliance on custom visuals Provides a consistent and standardized visualization experience Makes advanced analytics accessible to business and non-technical users Enhances decision-making through better understanding of data behavior Why This Is Important Modern analytics requires more than simple aggregation and trend visualization. Understanding distribution, variability, and outliers is critical for accurate and reliable decision-making. Without native support for these statistical visuals, important insights remain hidden or require additional effort to uncover. Providing these capabilities as native, fully integrated visuals would significantly strengthen the analytical depth of Microsoft Power BI and position it as a more complete solution for both business intelligence and advanced data analysis. ... View more

Idea   Please add a selective sync feature to OneLake File Explorer so users can choose exactly which Fabric items are synchronised to their local machine.   Today, OneLake File Explorer surfaces and reacts to many workspace items that do not make sense in a desktop file sync experience, such as Pipelines, notebooks, Lakehouse table internals, Delta log folders, and other system-generated artefacts. For most users, the practical need is to work with actual files, not every technical item exposed in a Fabric workspace.   What I’m asking for Let users choose which workspace items are synced locally. For Lakehouses, provide an option to sync only the Files folder. Exclude technical and system-managed paths by default, or make them opt-in only. Give admins and users a simple UI to manage sync scope per workspace or per item.   Why this matters Reduces unnecessary CPU, memory, disk, and network usage on client machines. Prevents OneLake File Explorer from processing technical artefacts that are not useful in Windows File Explorer. Makes the product easier to understand for business users and data teams who only want file access. Improves performance and reliability, especially in workspaces with active Lakehouses, Pipelines, and other Fabric items. Aligns the File Explorer experience with real user intent: browse and work with files, not internal Fabric metadata. Preferred behaviour for Lakehouses   When a user connects a Lakehouse in OneLake File Explorer, the default sync option should be: Files only   Advanced users could optionally enable additional paths, but technical folders such as table storage and Delta metadata should not be included by default in the normal desktop sync experience.   Example use case   A user wants to upload and manage CSV, Excel, JSON, and Parquet files in a Lakehouse through Windows File Explorer. They do not want to see or synchronise Pipelines, notebooks, _delta_log, checkpoint files, table metadata, or other internal Fabric-generated content.   This feature would make OneLake File Explorer much more practical, efficient, and user-friendly for real-world Fabric deployments. ... View more

Hi Fabric Capacity Team,   I would like to bring to your attention an enhancement opportunity within the Microsoft Fabric Capacity Metrics app that can significantly improve our monitoring, governance, and cost optimization capabilities. Current Limitation: At present, the Capacity Metrics app provides insights at the workspace and workload level. However, it lacks visibility into item-level capacity consumption, making it difficult to identify which specific artifacts such as reports, semantic models, pipelines, or notebooks are driving resource utilization.   Key Challenges: Limited ability to perform root cause analysis for capacity spikes Difficulty in identifying top resource-consuming items Constraints in optimizing capacity usage and associated costs Reduced effectiveness in governance and performance monitoring Proposed Enhancement: We propose introducing granular, item-level capacity insights with the following capabilities: Detailed consumption breakdown by individual items (reports, datasets, pipelines, notebooks, etc.) Time-based granularity, such as hourly or near real-time tracking Top-N analysis to identify high-consuming items within a selected timeframe (e.g., top 5 items in the last hour) Advanced filtering by workspace, item type, and capacity Data export and API access for extended analysis and integration Expected Benefits: Improved cost optimization through better visibility of high-usage items Faster and more accurate troubleshooting of capacity-related issues Enhanced governance and monitoring across workspaces Data-driven decision-making for capacity planning and performance tuning Considering Fabric’s internal mechanisms such as smoothing and bursting, having granular visibility will further help in understanding actual consumption patterns and enable more effective optimization strategies. I recommend that we formally submit this enhancement request through the Fabric Ideas portal to ensure it is considered in future roadmap discussions. Please let me know your thoughts or if you would like to discuss this further.   Regards, Jayasudha Mudaliar   ... View more

In some cases, we may want to show multiple columns but freeze the first couple of columns - without using metrix form. Would be good to have that feature - the way we can do it in excel. ... View more