The item soft-delete and recovery feature, currently in Preview, support several item types, as shown at https://learn.microsoft.com/en-us/fabric/admin/retention-recovery#supported-item-types. However, semantic models and reports are probably the most heavily used item types across Fabric estates. Yet they are notably absent from the list of supported item types.    The Fabric roadmap https://roadmap.fabric.microsoft.com/?product=administration%2Cgovernanceandsecurity#plan-d838b85d-e1b2-f011-bbd2-0022480a2ecf does not provide any information regarding if or when those item types will be added. ... View more

When we add two different columns to a single axis, such as X or Y, in a visual, we see drill up and drill down options. Is it possible to remove these options after applying this setup? ... 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

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

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

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

The ability to hide specific pages for a report based on the audience they belong too in a power bi app. ... 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

We are using a 4-level hierarchy in a Matrix visual: Level 1: Functional Area (e.g., Revenue, Selling & Marketing, Cost of Sales) Level 2: Subgroup 2 Level 3: Subgroup 1 Level 4: Partner Farea   Problem Description The hierarchy is ragged (uneven depth): Some Level 1 categories (e.g., Revenue) do not have child levels Others (e.g., Selling & Marketing) expand fully down to Level 4 When users expand the matrix hierarchy, Power BI expands all nodes to the deepest level (Level 4) As a result: Categories like Revenue show blank rows for Levels 2, 3, and 4 This creates unnecessary blank entries in the visual Expectation / Requirement We want to prevent blank rows from appearing when: A hierarchy branch does not extend to deeper levels (the plus icon should ideally not be present next to items that have no children or should not expand) (e.g., Revenue should remain at Level 1 and not expand into empty Levels 2–4) But currently due to product limitations, this is not possible. Suggestion -  1. Custom depth setting for each row in a matrix or option to stop any hierarchy at the last non blank value/category. 2. Currently we have a feature to select specific columns, a similar feature is needed to select specific rows. ... View more

It’s challenging and time-consuming for both new and experienced report creators to organize data when trying to split cards into categories. By introducing small multiples, it could be a familiar and easy way for report creators to intuitively categorize data, especially if they had more control over layout and formatting. ... 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, Hope you are doing well!   Now: Testing Row-Level Security today requires publishing to production first. There is no safe way to validate who sees what before going live. Misconfigured roles are only discovered after the fact, a direct governance and compliance risk.   GOAL : A native testing pane inside the Power BI Service where developers can simulate any role, impersonate a specific user by email, and immediately see which rows and tables are accessible, without touching the live environment. Three capabilities: role simulation without publishing, per-table access visibility, and an automated assertion suite that flags regressions whenever the data model changes.   Why ? Security incidents caused by misconfigured RLS are entirely preventable. This feature makes them so. It also reduces the time developers spend on manual validation cycles from hours to minutes, and provides compliance teams with a formal, exportable audit record of every validation session.   Thank you for considering this, I believe it would be a great addition to the Fabric and power bi experience ... View more

Need an audit trail / diagnostic event that explains why a semantic model’s compatibility level was auto-upgraded (e.g., 1569 → 1600) ... View more

Why you ask? Well, because: DevOps / CI/CD alignment Consistency with PBIR direction Reduced friction / errors Enterprise governance benefits   Organizations using Fabric Git integration require PBIP, but default Save creates PBIX — leading to accidental non‑compliant artifacts in repos. A tenant or user-level setting would align with CI/CD workflows, and reduce frustrations. Making this a desktop option to set the default wouldn't box anyone in, user could 1 time set it. ... 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

I would suggest to introduce "folders" to have new connections organized in a easier and segregated way. In a Enterprise environment, wheer all teh connecitons to resources are managed ina  centralized way, having the possibility of creating folders, as in the Workspaces, would allow better organized resources (e.g. Like in the Deployment pipelines). Thank you for the opportunity, Alfredo Lourido Santos ... View more

Users' scheduled refresh is stuck in cancellation and there is no way to terminate it or kill the request using the ID. Is there a way where either I can kill the abandoned process or change the default timeout. Atleast there should be a way to change the default timeout. I can always use API calls to trigger the refresh (which has an option for the default timeout). Any ideas here ? ... 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

To address the challenges of organizing and presenting data due to the limitations of column and row headers, a potential solution would be to implement a new matrix visual with customizable controls, allowing report creators to adjust the dimensions of columns and rows, group them hierarchically, apply diverse styles, and use conditional formatting. ... View more