Currently, On-Object Interaction is only available in Power BI Desktop and is not supported in the Fabric web report editor. This forces users who work primarily in Fabric to fall back to the old Visualizations pane, which is less intuitive and slows down the report authoring workflow. Please bring On-Object Interaction to the Fabric web editor so that users can enjoy the same modern authoring experience regardless of whether they are working in Desktop or in the browser. This would significantly improve productivity for teams that use Fabric as their primary authoring environment. ... View more

hello everyone i am facing issue many time when  i load data from on premise sql server to fabric via on premise gateway. if anyone have solution please tell me ... View more

Idea Request a single AI-powered chatbot within Microsoft Fabric that acts as a unified interface across all data services (similar to Databricks). What it should do Query data using natural language (auto SQL/DAX generation) Work across Lakehouse, Warehouse, Power BI, and Streaming Auto-create pipelines, notebooks, and reports Integrate with Purview for governance & lineage Help troubleshoot pipelines, queries, and capacity issues Why this matters Currently, users must switch tools and know where data resides. A unified chatbot will: Simplify user experience Enable true self-service analytics Reduce dependency on technical teams Accelerate time-to-insight Goal Make Fabric a truly AI-first unified data platform with a conversational interface for all personas (business, analyst, engineer, admin). ... View more

I want to deploy a dataflow gen 2 CICD and semantic model via a Fabric deployment pipeline from my dev workspace to my test workspace.  I can configure the dataflow destination and source with a variable library.  But I can't use the variable library to configure my semantic model source,  I have to use a deployment rule instead.  Having to use two different mechanisms (variable libraries and deployment rules) to deploy between workspaces is clunky.  I can set a parameter for my semantic model source, so if I could reference a variable library item in the parameter, that would make it slightly easier. Thanks! ... View more

I have selected 8 table in copy job but only seeing 2 at a time. I feel there must be an option for maximize and minimize fabrics items window ... View more

This is insane...  How can Microsoft suggest to use Dataverse for the enterprise while not even supporting such storage for dataflow gen 2.  Highly disapointing. Please support ASAP. ... View more

Dynamic Column Filtering for OneLake Security CLS in Lakehouse SQL Endpoints We would like to propose an idea regarding the current behavior of Column-Level Security (CLS) in Microsoft Fabric OneLake Security when accessing data through Lakehouse SQL Endpoints.   During troubleshooting and validation sessions with Microsoft Support, we confirmed that CLS is functioning as currently designed. However, we observed a limitation in how CLS behaves during schema validation and query execution from SQL Endpoints and Power BI semantic models.   Current Behavior After creating a OneLake Security role with CLS restrictions: Restricted columns are still exposed within the Lakehouse SQL Endpoint schema metadata. The SQL Endpoint appears to scan or validate the complete table schema before executing the query. If restricted columns exist in the semantic model, query definition, or metadata discovery process, queries fail with permission errors such as: “SELECT permission was denied on the column…” This happens even when users only intend to access permitted columns. Because of this behavior: Power BI semantic models may fail during refresh or schema discovery. Developers must manually exclude restricted columns. Separate materialized lake views must be created for different security personas. Additional maintenance and governance overhead is introduced. Example Scenario Table: EmployeeID EmployeeName Salary SSN CLS Restriction: Salary SSN Expected Experience: Users should automatically see only: EmployeeID EmployeeName Current Experience: Restricted columns remain discoverable through schema validation, and queries may fail instead of dynamically filtering unauthorized columns. Proposed Idea We propose that the Lakehouse SQL Endpoint dynamically recognize the authenticated user principal and automatically apply CLS filtering during schema discovery and query execution. In this approach: Restricted columns would automatically be hidden from the schema presented to the user. Only authorized columns would appear during Power BI schema discovery, SSMS access, and SQL query execution. Queries and semantic models would execute successfully without requiring developers to redesign datasets or manually remove restricted columns. Benefits This approach would: Simplify Power BI and SQL development. Reduce dependency on materialized lake views. Improve enterprise scalability for self-service BI. Reduce maintenance overhead. Provide a more intuitive CLS experience for Lakehouse SQL Endpoints. Currently, the materialized lake view workaround is functional, but it introduces operational complexity for enterprise environments managing multiple datasets, users, and security roles. We believe dynamic CLS-aware schema filtering would significantly improve the usability and enterprise adoption of OneLake Security in Microsoft Fabric Lakehouses and SQL Endpoints. Thank you for considering this idea. ... View more

There needs to be a way to view user names stored with connections under Manage Connections and Gateways or through some other means.  As an enterprise with lots of connections using various service accounts, in which we need to do password re-sets on a regular basis, we need a way to know which connections are using which accounts.  The On-Prem Power BI Report Server provides this level of granularity, there is no reason Power BI Service can't provide the same.  Without this, managing these connections is almost impossible. See below comparison. ... View more

Currently, Activator rules only sends email notifications to individual internal email addresses. It would be very beneficial to allow Activator rules to send emails directly to Microsoft Exchange Distribution List as well.   This will make notification management easy for developers. Instead of updating recipients individually within each Activator rule whenever team members join or leave, administrators could manage membership directly through the Exchange Distribution List.   This will reduce effort require for maintenace and help ensure notifications always reach the correct audience.   This enhancement will be useful for teams, support groups, and large organizations where notification recipients change frequently.  ... View more

The current method of changing line colors on a line graph is tedious and clunky.   The previous versions showed a dropdown for each line that was represented on the graph, and right next to it was the color of the line. This made it very quick to identify and change the colors of certain series on the graph.   However, in the current version, you have to click the dropdown for [Apply Settings to: "Series"], select which series you want, then scroll down and change the color.   This takes a substantial amount of time and is a total pain in the rear, especially for certain reports I have where I need to show a bulk trend that matches with my report theme, so I don't need 50 different colors, I just need one single color for all of my lines     ... View more

users are working with Microsoft Fabric deployment pipelines in  environments where Dev → Test → Prod promotion is required. Limitations  Lakehouse deployment fails when shortcuts exist Pipelines do not support deployment of Lakehouses with active shortcuts Requires manual removal and recreation Connections are not environment-aware After deployment, connections still point to source (Dev) No native parameterisation support Cross-workspace data sharing limitations Unable to directly create shortcuts on Warehouse tables across workspaces impact with workarounds : Manual effort increases significantly post-deployment Time-consuming and error-prone for large-scale deployments High risk of configuration drift across environments   It would be highly beneficial if these limitations could be addressed in the product, or if a more robust and scalable alternative approach could be provided to support enterprise deployments. ... View more

Currently, Excel allows connection to Power BI semantic models primarily through PivotTables. While limited editing is technically possible, it requires the use of DAX queries, which is not user-friendly for most business users. Unlike SQL Server or other sources, there is no simple way to: Edit existing connections Filter columns or rows Shape data using Power Query This creates a usability gap, especially for users who rely on Excel for flexible data preparation.   Suggestion Provide the ability to edit Power BI semantic model connections using Power Query instead of DAX, enabling: Easy editing of existing connections via Power Query Editor Column selection and filtering through UI (no DAX required) Standard transformations (filter, merge, append, reshape) Save and refresh refined queries ... View more

So if you open a dataflow from within a pipeline the tab pops open and then in the case where I am not the owner tells me I don't have access. So I try to close the tab it opened ("getting things ready") and it says: Close dataflow Please close the dataflow before navigating away. But I can't there's no close or [x] available, no cancelling out of this. I can't go back one page, same message. I can't choose another tab, another workspace, or anything else on this page now, same message. I'm left with no option but to close the browser tab entirely, this may include losing pipeline modifications on another Fabric tab - not great. Idea: if I'm not the owner, then open the data model instead, where I can take over ownership. ... View more

On the Standardised Work FAU FAI Dashboard you have to select the plant & the Operation but they are the same thing. CY05 is SRM. Please remove the whole Operation box   ... View more

Can we please get a week drop down box added to the  FAU & FAI Leadership Opportunity power BI.  Like the one attached thankyou   ... View more

Can we please get a total for the approvals dashboard aswell as the average days. The current state makes us tally it upfrom the chart. Can we also please get a work week calender to select from like the attached photo so we just select the week instead of having to open the two calenders and it defaulting to 2018.    ... View more

For a failed pipeline run, when I select "Rerun from failed activity", the pipeline sets all activities BEFORE the failed activity to "Skipped" status except this doesn't happen immediately for the wait activities. The wait activities run the full wait time and then are set to "Skipped" status AFTER running. Can the functionality be changed to skip the wait activities immediately? There is no need to wait for processes to cool down when all other activities have been skipped.    ... View more

Microsoft Fabric operates in UTC internally, which is reasonable and understandable for a global cloud platform. [community....rosoft.com] However, enforcing UTC even at the UI level (e.g., Admin portal, Monitor, logs, and BI/reporting layers) introduces usability and operational challenges. From a user perspective, timestamps are not abstract values—they are interpreted within a specific local time context. When all timestamps are displayed only in UTC, users must constantly perform mental or manual conversions, which leads to: Increased cognitive load Misinterpretation of events (especially in monitoring and incident analysis) Inconsistency across different Fabric experiences This is particularly problematic in: Fabric Monitor and workspace monitoring logs Admin portal diagnostics and activity tracking Power BI / reporting scenarios where business users consume time-based information Although workarounds exist (e.g., manual conversion using DAX, Power Query, or query logic), these are fragmented and shift responsibility to each implementation. [bing.com], [thebricks.com] Proposal The platform should provide: Configurable timezone for UI display At user level and/or workspace level Explicit visualization of applied timezone Clearly indicate whether timestamps are UTC or converted Consistent behavior across all Fabric components Monitor Logs Admin portal BI / reporting Expected Benefit Improved usability and reduced operational friction Accurate interpretation of logs and monitoring data Better alignment with real-world business time contexts ... View more

I suggest enhancing the available actions in the Image visual by allowing users to apply custom filters based on selected fields and values. Ideally, these filters should support dynamic expressions (fx) rather than being limited to static values. This would significantly increase flexibility and enable more interactive and context-aware report navigation. Adding this capability would align the Image visual with more advanced interaction scenarios already available in other visuals and improve the overall user experience when designing dashboards. ... View more