Interpreting visuals without a clear legend to indicate logic behind specific styles can lead to confusion and decision-making errors. An idea to enhance clarity and transparency by ensuring legends and tooltips accurately display colors, patterns, and other visual components influenced by logics, would enable report consumers to easily understand the applied logic and make more effective decisions. ... View more

Currently, tooltips in Power BI reports are automatically triggered when users hover over visual elements. While tooltips provide valuable information, there are scenarios where users may want to temporarily disable them to improve navigation or data selection. I suggest adding an option to allow users to turn tooltips on or off for individual visuals, or to introduce a keyboard shortcut or mouse combination that temporarily disables tooltips. This would greatly enhance user experience, especially when interacting with complex reports or dashboards. ... View more

On the Fabric Roadmap release schedule, it would be very useful to be able to subscribe to a notification when an item on the release schedule becomes available on Preview and GA.  It is very cumbersome to have to periodically go look at the release schedule to see if interested items have changed status.   ... View more

In our multi-tenant solution we use partitions in Apache Kafka to separate data for each tenant. To process events from a specific partition (aka tenant) and stream them into a tenant specific destination (KQL database in this case), it would be nice if it is possible to subscribe to a specific partition when configuring an Apache Kafka datasource in an eventstream.   Today it is mandatory to do 'Event processing before ingestion' and use transformations to filter tenant specific events and route them to the tenant specific KQL database. When you can subscribe to a specific partition, it becomes possible to use 'Direct ingestion' instead. ... View more

Currently, there is no tenant-level control available in Power BI to completely disable the “Explore” (Explorer) feature across the environment. The feature’s availability is governed only through dataset-level permissions rather than a centralized administrative setting. Provide Tenant-Level Setting to Disable “Explore” (Explorer) Feature Globally in Power BI ... View more

Need an audit trail / diagnostic event that explains why a semantic model’s compatibility level was auto-upgraded and to track or identify which user or action triggered the use of specific features along with timestamp (such as DAX Query View Desktop or Web Modeling Edit) that led to the automatic conversion of the semantic model version and the option to disable the auto upgrade of version. ... View more

Today, Power BI semantic models (datasets/DAX) work well when Power BI is the only BI tool. However, many organizations use Databricks as their lakehouse and need consistent, governed metrics across multiple BI tools, ML pipelines, and APIs. When the semantic layer lives only in Power BI: Logic is duplicated across datasets and tools Governance/security (RLS/CLS, masking) is fragmented Schema changes in Databricks break reports ML/AI pipelines cannot reuse business logic from Power BI models Proposal: Enable native Power BI integration with Databricks Metric View ... View more

Ref this youtube-video: (350) How to Turn SQL Database changes into Real-Time Intelligence with Fabric Eventstreams | Data … I want to use Fabric SQL Server as a (CDC) source to Fabric Eventstream in the same manner as using Azure SQL Server (CDC) is outlined in the youtube-video. We have service principal based connection to our Fabric SQL Server and it would be a killer use case to be able to use this as source (CDC) in the setup of the Eventstream.   ... 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

The banner is always shown (by design) and reappears on every reload, impacting UI/UX in embedded apps and portals. Need a setting to hide or remove the sensitivity label banner in embedded Power BI reports. Related Idea: Option to hide the information protection banner (sensitivity label) ... View more

Customers are currently experiencing challenges when trying to connect Power BI or Microsoft Fabric to Snowflake Semantic Views created in Snowflake. At this time, the only available workaround is to use a custom connector, where possible, to access this semantic layer. While this workaround may help in some scenarios, it is not an ideal long-term solution because it adds complexity, increases maintenance effort, and may limit scalability for broader enterprise adoption. As more organizations are expected to move their analytical workloads toward Snowflake Semantic Views as a centralized semantic/modeling layer, having native connector support in Power BI / Fabric would be a significant improvement. A native connector would help: Simplify connectivity to Snowflake Semantic Views Reduce dependency on custom connectors and manual workarounds Improve usability, reliability, and supportability Enable smoother migration of workloads to Snowflake-based semantic models Provide a more seamless integration experience between Snowflake and Power BI / Fabric This enhancement would help address current connectivity limitations and better support customers who are adopting Snowflake Semantic Views as part of their modern analytics architecture. ... View more

When we build validator/conditional columns, we want to test all possible conditions to ensure that the code for said column works properly. Sometimes the live data does not have all the conditions we want to test. I propose (if it doesn't already exist) a data test mode that users can temporarily enable for directly changing data at the cell level. So if you need to test for blanks and your data has no blanks, you can enable test mode (name to be workshopped later) and convert one of your values to a blank. Once the test is done, you disable test mode, and your data goes back to normal. If possible, this could be used in both Power Query and in Table View. ... View more

The primary axis are outdated and require significant improvement when compared to Excel. This makes it difficult for report creators and often leads to problems when trying to manage and style them effectively. By offering more format settings, greater control over displayed data can be provided, especially if axis ticks, new gridlines, and separators are also included. ... View more

𝗠𝗶𝗰𝗿𝗼𝘀𝗼𝗳𝘁 𝗙𝗮𝗯𝗿𝗶𝗰 𝗖𝗼𝗽𝘆 𝗔𝗰𝘁𝗶𝘃𝗶𝘁𝘆 + 𝗗𝗲𝗹𝘁𝗮 𝗨𝗽𝘀𝗲𝗿𝘁 is honestly one of the most underrated features in Fabric for high-performance operational data loading.   We can now: • Read directly from sources such as SQL Server / SQL DB • Write directly into Lakehouse Delta Tables • Use native Upsert mode • Avoid Spark notebooks completely • Avoid Parquet staging/intermediate layers • Achieve very fast sync performance with only ONE Copy Activity   I’m currently using this approach to dynamically load and merge data from multiple SQL Server store databases into consolidated Delta tables in Microsoft Fabric Lakehouse. However, there is one very important feature still missing from Copy Activity Upsert.   𝗜 𝘄𝗼𝘂𝗹𝗱 𝗹𝗼𝘃𝗲 𝘁𝗼 𝘀𝗲𝗲 𝗻𝗮𝘁𝗶𝘃𝗲 𝘀𝘂𝗽𝗽𝗼𝗿𝘁 𝗳𝗼𝗿 𝗮𝘂𝘁𝗼-𝗺𝗮𝗻𝗮𝗴𝗲𝗱 𝗮𝘂𝗱𝗶𝘁 / 𝗗𝗪 𝗰𝗼𝗹𝘂𝗺𝗻𝘀 during Upsert operations. My requirement is: In the destination Delta table, I need these columns: • DW_DATE_INSERT → Datetime when a NEW record is inserted through Upsert • DW_DATE_UPDATE → Datetime when an EXISTING record is updated through Upsert • DW_LOAD_DATE → Maximum of DW_DATE_INSERT and DW_DATE_UPDATE (meaning the latest insert/update datetime)   Expected behavior: • If INSERT occurs: DW_DATE_INSERT should be populated DW_DATE_UPDATE should remain NULL • If UPDATE occurs: DW_DATE_UPDATE should be updated DW_DATE_INSERT should remain unchanged with its original value   Currently, adding these columns dynamically in the Source → Additional Columns section is NOT a solution. Why? Because these datetime values change every execution, the Upsert process detects every row as changed and re-updates all records again and again, even when business data has not changed.   Of course, I know this can be handled using Spark / Notebook MERGE logic. But the whole beauty of this approach is: 𝗡𝗼 𝗻𝗼𝘁𝗲𝗯𝗼𝗼𝗸𝘀. 𝗡𝗼 𝗦𝗽𝗮𝗿𝗸 𝘀𝘁𝗮𝗿𝘁𝘂𝗽 𝗹𝗮𝘁𝗲𝗻𝗰𝘆. 𝗡𝗼 𝗲𝘅𝘁𝗿𝗮 𝗺𝗲𝗿𝗴𝗲 𝗹𝗮𝘆𝗲𝗿. 𝗝𝘂𝘀𝘁 𝗼𝗻𝗲 𝗳𝗮𝘀𝘁 𝗖𝗼𝗽𝘆 𝗔𝗰𝘁𝗶𝘃𝗶𝘁𝘆.   It would be amazing if Microsoft could add native insert/update audit column handling directly inside Copy Activity Upsert for Delta Lakehouse tables. This would make Copy Activity even more powerful for very fast enterprise operational sync workloads. If you think this feature would be useful, please vote/support this idea so we can hopefully get it added to Fabric 🙌   #MicrosoftFabric #DataEngineering #DeltaLake #Lakehouse #ETL #ELT #OneLake #SQLServer #Fabric #Microsoft #AnalyticsEngineering ... View more

The ability to hide specific pages for a report based on the audience they belong too in a power bi app. ... View more

Customer wanted to know how they can get a notifications for upcoming Power BI preview features before they are pushed and enabled in the tenant settings. Not using the below options: Preview features are announced externally first (blogs, newsletters, events) Check Power BI updates blog (monthly drop) The most reliable proactive model is: Blog + Newsletter + Enablement sessions + RSS tracking     ... View more

Having the ability to run python code outside of the notebook environment (like we can for pyspark jobs) could be a real win for efficiency and modularity. It would allow users to package robust, unit-tested code and deploy it to the fabric environment where it could run as a cost-effective single-node job. Databricks has an implementation for this, and it would be really nice to see something similar come to Fabric. Notebooks are great for ad-hoc or exploratory stuff, but building something robust in them feels like shoving a peg into a wrong-shaped hole. They are (nearly) impossible to unit test, so you often end up creating libraries which allow you to package transformations in a way that can be tested, then your notebooks end up being essentially thin wrappers around a bunch of external code. I think the most obvious example for this is the number of Fabric DBT implementations that essentially involve installing DBT core into a notebook and running it there (I know there is DBT jobs coming, but this is beside the point). This is a symptom of a larger need for this type of hosting/execution of code within the environment. Yes, you could host the code on a vm external to Fabric but that goes against the ethos of a unified data platform. Offering something like this would be a great way to increase the flexibility and extensibility of the platform. The implementation can be fairly barebones and developer forward, aiming to provide maximum flexibility and extensibility. Basically a way to run python scripts/CLI tools on the Fabric capacity.    ... View more

Don't think this is currently available: Have default visual format settings:  eg: corner radius 6, border blue, font X, font colour Y etc etc so that everytime you add a visual, it has the same characteristics. We can create a template, but you still have to copy paste from one pbix to another or copy an exising visual and change it. It would be nice to have a place to set defaults so that all new visuals are created the same. ... View more

Currently, we understand that users can reference shared cloud connections within the Variable Library . However, connections created through On-Premises Data Gateway (OPDG) and VNet gateways are not supported in this experience.   We would like to request support for OPDG gateway connections to be available as selectable connection references in the Variable Library. This enhancement would significantly improve the overall user experience and align the Variable Library feature with broader connectivity scenarios commonly used by customers. ... View more