Currently, Power BI allows the option to “Show items with no data” for certain visuals, but this functionality is limited when using Line Charts with a Continuous axis type.  Allow line charts to display items with no data while keeping the axis type as Continuous. This would help maintain smooth scaling and date hierarchy formatting without forcing users to switch to categorical mode (which changes labels to raw date values). This enhancement would improve parity between visuals and provide better support for scenarios where users want continuous scaling and visibility of empty periods. ... View more

Paginated reports to automatically pick up the refreshed semantic model data without manual intervention. This feature would ensure consistency between semantic model refresh and paginated report output, improving user experience and reducing operational overhead. ... 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

Need to restore the feature that send refresh failure notifications to contacts for Dataflow Gen1. Currently, the notification is only sent to the Dataflow owner, and the option to add contacts in the refresh settings is missing. Previously, this feature allowed adding specific users to receive notifications when a dataflow refresh failed, which was very useful ... View more

I need to conditional format the row header, not just the values section.   Also I would like to be able to format the font in bold/italic and be able to define complete rows (values including row headers) to be underline/overline. ... View more

We would like to have a tenant setting that allows us to completely disable report sharing with other users. Currently, to block report sharing, we can disable the tenant setting for people within our organization. Similarly, we need a tenant setting that either blocks sharing with specific people or disables sharing entirely. ... View more

Power BI needs a way to move gateway connections between gateway servers without having to recreate on the new server each time. As a large enterprise running Power BI, we have many gateway clusters that are now being capped at the 1,000 connection limit, forcing our users to constantly shuffle connections around to other gateways. We need the ability to change the drop down for gateway cluster in the connection settings and relocate it easily without having users recreate the connection and delete the old one. ... View more

We would like to be able to modify a Power BI Connection authentication config via API.   For example, for BigQuery connections, we would like to update their Service Accout key-based authentication config programatically: this would eliminate toil for people with several connections and periodic mandatory key rotations.   References: Power BI REST APIs for embedded analytics and automation - Power BI REST API | Microsoft Learn Google BigQuery connector - Power Query | Microsoft Learn ... 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

When using a Copy Activity with a REST source in Microsoft Fabric, the current activity input and output only provide minimal metadata about the request and response. This makes troubleshooting difficult, especially when using dynamic URLs, query parameters, pagination, or REST APIs that rely on correlation IDs for traceability.   Today, the activity input shows basic request settings such as method, timeout, and configured headers, but it does not show the final resolved request URL or the details of the HTTP response returned by the server. Without this information, diagnosing issues like invalid query parameters, authentication failures, pagination errors, throttling, and server-side errors is significantly harder.   Problem / Pain Point: When a REST-based Copy Activity fails or behaves unexpectedly, users cannot see the actual request URL, including the evaluated query string. They cannot trace the request back to server logs because correlation IDs are not surfaced. They cannot inspect the HTTP status line, response headers, or the response body returned during an error. Pagination information such as Link headers is also missing. These fields are standard diagnostics for debugging REST calls, and without them, troubleshooting in Fabric becomes guesswork. Proposed Enhancement: Add the fully resolved request URL to the Activity Input. This should include the full URL with dynamically evaluated parameters and query string so developers can see exactly what Fabric sent to the server. Expand Activity Output to include detailed HTTP response metadata. The requested fields are: HTTP Status Line (for example: HTTP/1.1 404 Not Found) Response Headers, specifically: Correlation ID (such as X-Request-ID or X-Correlation-ID) Timestamp returned by the server Content-Type Content-Length Link header (RFC 5988) for pagination Response body when the server returns an error (HTTP 4xx or 5xx) Impact / Value: Adding this metadata would significantly improve troubleshooting for REST ingestion pipelines, allow correlation with server logs using correlation IDs, reduce debugging time for dynamic URL issues, improve visibility into pagination and throttling scenarios, and bring feature parity with tools like Azure Data Factory. This enhancement would make REST-based data ingestion in Fabric more reliable, debuggable, and aligned with enterprise observability practices. ... View more

When I create a hierarchy in a table in a semantic model (Fabric), I can't see the hierarchy in a pivot table in Excel. I used this feature frequently with semantic models in PowerBI, and really liked it. ... View more

We would like information on which characters are supported or valid for workspace names, in the documentation. There should also be a description that gives an overview of the valid characters for workspace names in the Power BI service when creating a workspace. ... View more

Problem: Currently, downstream consumers who need to query Eventhouse data via Lakehouse shortcuts must have read access to the primary Eventhouse tables. This creates two main challenges: Security / Governance: Users can access the primary Eventhouse, which may not be desirable. Operational Overhead: Teams must schedule incremental .export commands for each table to provide Lakehouse access, which is cumbersome and difficult to manage at scale.   Proposed Solution: Introduce a feature that allows Eventhouse to automatically export data to Lakehouse shortcuts without requiring users to have read access to the primary tables. Benefits: Downstream consumers can query Lakehouse shortcuts without impacting Eventhouse compute or hitting query limits. Eliminates the need to schedule per-table exports manually. Maintains strict security and governance by preventing direct access to the primary Eventhouse tables. Supports both full and incremental exports, keeping Lakehouse data fresh and up-to-date. ... View more

Power BI mobile app is great for viewing reports, but it’s missing two critical features: Export to PDF/Excel and Share / Print. Mobile users often need to share insights quickly during meetings or while traveling. Having these options directly in the app would: Boost productivity on the go Enable instant sharing Create consistency with the desktop experience Request: Please add Export to PDF/ Excel and Share / Print the report options to the Power BI mobile app. This would make the app far more powerful and user-friendly for business users everywhere. ... 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

Description: Currently, when replicating tables from a SQL database to the SQL Analytics endpoint in Microsoft Fabric, all tables are included by default. However, not all tables are needed in the analytics endpoint. This creates unnecessary overhead and, in some cases, leads to lock situations in the SQL database during replication for certain tables. Problem: Some tables are not required in the analytics endpoint. Replication of these tables can cause locking issues in the source SQL database. There is no built-in mechanism to exclude specific tables from replication. Proposed Solution: Introduce functionality to exclude specific tables from replication. This should include: Explicit Table Exclusion: Ability to define a list of tables to exclude. Pattern-Based Exclusion: Support for regex-based patterns to exclude tables dynamically. Example: Exclude all tables ending with __b. Regex equivalent: .*__b$ Benefits: Reduces unnecessary replication overhead. Prevents lock situations on source tables. Provides flexibility for administrators to manage replication scope efficiently. ... View more

Hi team,   I would be really helpful if we could have the explore mode in the Power BI desktop when connected to a semantic model in edit mode or even in connected mode   That would make the exploration of the data very accessible - the share and open in new tab buttons should of course not be there 🙂         ... View more

Users working with reports occasionally encounter the error “Query exceeded memory limit.” However, report creators have no way to determine which specific query caused the memory limit to be exceeded. It would be helpful to have a feature, such as in Fabric Capacity Metrics, to identify which queries caused the memory limit to be exceeded. ... View more

  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