Currently, colors are automatically assigned randomly.  It would be nice if your dev workspace was always blue, and your prod was always pink for example.  Then you'd have a good visual as to where you're working in. ... View more

I recently had a spike on my fabric capacity with no user tagged against the query activity. After discussing with support this was identified as due to the eviction and recalculation caused by changing the storage mode on the semantic model from small to large.   This possibility of this CU spike is currently not documented and the blank user in the capacity metrics app also creates confusion. Two suggested improvements.  1. Include this in the docs as a consideration for when changing the storage size, currently this is not documented. 2. Set the user to a useful value in the capacity metrics app, ideally something like storage mode conversion task but even Power BI Service as used for other internal operations would be better.  ... View more

Matrix visuals could significantly enhance the user experience by emulating Excel's intuitive sorting, searching, and filtering capabilities, even for hierarchical columns. This idea would the current limitation in Power BI's matrix visuals, which lack a comparable experience to Excel's established standard for data manipulation. ... View more

I am working on automating CI/CD for semantic models in Power BI / Fabric. I can successfully deploy semantic models and define RLS/OLS roles using TMDL, but I am unable to automate the assignment of users or Azure AD groups to those roles. At the moment, role membership must be added manually through the semantic model security UI. Is there any supported way to automate role membership for RLS/OLS, for example via: - Power BI REST API - XMLA endpoint / TOM - Fabric REST APIs My goal is a fully automated, repeatable deployment without manual post-deployment steps. ... View more

We need to be able to attach default and non default lakehouses to notebooks in bulk in deployment pipeline rules. It's not scalable to have to select each and every single notebook in a workspace to make the deployment rule, which is the case today. We should be able to select multiple notebooks and make the deployment rule or something similar. Currently we have to run a script after a deployment from dev to tst to prd, in order to change the attached lakehouses. This isn't ideal to say the least. ... View more

It was nice to see Microsoft add an out of the box mirror solution for the SAP Datasphere replication flow output. However, there are some limitations and issue I have found. Each entity that is replicated from SAP Datasphere to Azure Gen2 Storage produces a Top Fold matching the table name and sub-folders of initial and delta. In the initial folder, SAP generates a _SUCCESS file indicating that the initial load is completed and all parquet files are now ready for consumption. The time-stamp on the file will not change unless the entitie's replication is restarted in SAP Datasphere. The mirror db solution needs to keep track of this file and automaticaly reset the individual entity if the _SUCCESS file is modified or recreated. This should trigger the mirror db to "restart" replication on the entity. The restart process shoud delete all records in the target delta lake table and reload everything again. This bring up another point in that their is no way to restart replication on a single entity within the mirror database management interface. Their are times where I need to restart just one entity and not all of them. ... View more

While installing the gateway, we ask users to select the home tenant so that the installation works correctly and we can view the gateway connection in the service. However, we noticed that one user changed their region and tried to log in to Fabric, which resulted in the error message: "can't be used outside your default environment." As per the document,we then requested the user to choose the default region, after which both the gateway and Fabric functioned properly, and the gateway connection appeared in the service. The user’s question is: if we need to use the default region, why is there an option to change it during gateway setup? If this option is useful, where is the relevant documentation?     ... View more

Many people use the Power BI Subscription service as part of a data pipeline (monitoring email inbox, automatically downloading them image, then using that image for things).   You recently changed the subject line of the email to begin with "Power BI report subscription delivery" without any warning, breaking several of our pipelines and resulting in confusion.   Please, before you roll out changes like this, notify people.   Thank you! ... View more

Currently, Microsoft Fabric does not allow naming schedules associated with Fabric items such as pipelines or notebooks. Schedules are system-generated and cannot be given a meaningful, user-defined name. In Azure Data Factory, this capability exists through Trigger Names, which makes identification, monitoring, and governance much easier. Having user-defined schedule names is important for us as we are building dashboards that display running schedules, allowing teams to easily identify, track, and monitor scheduled executions across multiple pipelines or notebooks in a clear and readable way.   We are requesting that Microsoft Fabric add a feature to allow user-defined schedule names similar to Azure Data Factory. ... View more

Enable workspace members with the appropriate permissions (e.g., Admin / Member / Contributor) to edit or modify tables in semantic models even if they are not the semantic model owner, as long as they have write permissions on the dataset and Lakehouse. ... View more

When datasets are created in BigQuery using the BigQuery API without explicitly specifying a location, the API defaults to the US multi‑region. This default behavior causes issues for users need a way to change the default setting ... View more

It would be helpful to add dynamic context to visuals using a measure within this field:     ... View more

Secondary axes are automatically managed by the system in some cases, making it problematic for report creators with no control over intervals, ticks, and other crucial components, limiting effectiveness of various types of analysis. It would be great if the secondary axis included comprehensive format settings so that greater control over displayed data is provided. ... View more

Enable Incremental Refresh for Power BI Pro users, not just Premium. ... View more

Our team would like join to our security mapping table in the rule and call the employee that is querying's username and filter by it. It would look like: select * from my_table inner join security_table on security_table.projectID = my_table.projectID where security_table.username = username() This would allow us to dynamically set our RLS on the table. ... View more

Fabric’s SQL endpoint currently fails when the feature.v2Checkpoint flag is present in Delta log history. This flag is automatically set when tables are written with v2 checkpoints, which is the default when adopting Databricks‑recommended practices like liquid clustering. This creates a critical gap: Databricks promotes v2 checkpoints and liquid clustering as best practices, yet Fabric’s SQL endpoint does not support them. The result is brittle workarounds that block enterprise‑scale adoption. Ask: Enable support for v2 checkpoint policy in Delta table shortcuts so Fabric can align with Databricks standards, eliminate fragile workarounds, and unlock enterprise readiness. ... View more

Paginated reports - please make it available in Pro as well as Premium .. thank you ... View more

Currently, the Workspace Info – Get Scan Result API is available only as an admin-level API and requires either a Fabric/Tenant Administrator role or a service principal explicitly granted access to tenant-level admin APIs. Workspace Admin permissions alone are not sufficient. In many organizations, developers and workspace owners are not allowed to hold Fabric or Tenant Administrator roles due to governance and security policies. As a result, workspace administrators are unable to programmatically retrieve metadata such as Created By, Last Modified By, or item inventory details for the workspaces they manage. At present, there is no supported alternative API that allows workspace administrators to scan or retrieve governance metadata scoped only to their own workspace, which limits self-service governance, auditing, and automation scenarios. Proposed Enhancement Introduce workspace-scoped metadata scan APIs that: Can be executed by Workspace Admins Allow retrieval of item-level metadata such as ownership, last modified details Do not require tenant-level or Fabric Administrator permissions Business Impact Enables self-service governance and auditing at the workspace level Avoids over-privileging users with tenant-wide admin roles Aligns with enterprise security and least-privilege policies Reduces dependency on centralized admin teams for basic metadata needs This enhancement would significantly improve governance capabilities while maintaining strict security boundaries. ... View more

If it was possible to offer a robust and customizable style management system for the matrix, it could be the key to enhancing the professional appearance of tables and matrices. Further, giving report creators the ability to adjust gridlines, color, style, and the addition of custom icons, bars, sparklines, and other elements, along with a variety of pre-designed styles, would significantly improve style management options for tabular elements. ... View more