When using overlay visuals (such as Cards aligned with Table/Matrix visuals), the vertical alignment appears correct on the design screen but shifts when viewed on different screen sizes or resolutions (e.g., laptop vs. large monitor). This creates inconsistent formatting and impacts the user experience. It would be helpful to have improved support to maintain consistent alignment and better control over visual sizing across devices. ... View more

The introduction of the new Date Picker is an amazing improvement for Power BI usability. However, the current Polish localization suffers from literal, context-free machine translations that make the interface look unprofessional and confusing for business end-users. The main issues lie within the Relative Date selection dropdowns, where time ranges and time units are mixed and translated incorrectly. Here is a breakdown of the current interface issues and the proposed replacements for analytical reports: 1. Relative Period Selection (Time Directions) Current translation for "This": To (Literal translation of the pronoun "this", sounds like "it" in this context). Proposed change: Bieżące (Meaning "Current", which perfectly fits periods like current month/year). Current translation for "Next": Dalej (Literal translation used commonly for a "Next" button in installation wizards). Proposed change: Następne  (Natural phrasing for "Next N months/days"). 2. Time Units Consistency The dropdown currently mixes highly abbreviated text with full words and chaotic casing, creating an untidy UI. Current mixed list: * Dni (Days) Tyg. (Abbreviation for Weeks) Tygodnie (kalendarz) (Full word for Calendar Weeks) Mies. (Abbreviation for Months) Miesiące (kalendarz) (Full word for Calendar Months) l. (Lowercase single-letter abbreviation for Years) Lata (kalendarz) (Full word for Calendar Years) Proposed standardized list: To ensure a clean, professional look, abbreviations should be replaced with full, well-formatted words: Dni Tygodnie Tygodnie (kalendarzowe) Miesiące Miesiące (kalendarzowe) Lata Lata (kalendarzowe)   ... View more

We are currently using Matrix and Chart visuals in Power BI reports with enabled Drill Through, Drill Down, and Drill Up functionality for end users.   However, when users right-click on a visual, Power BI displays a wide range of context menu options beyond the drill-related actions. This includes several additional options that are not relevant to our reporting scenarios. Current Behavior: Right-clicking on a visual displays multiple context menu options. Users are presented with actions that are not required for their use case. The large number of options can be overwhelming and confusing for business users. This impacts usability and reduces overall adoption of reports. Expected Behavior: We would like report developers to have more control over the right-click context menu. Specifically: Ability to customize which options are shown in the context menu. Option to restrict the menu to only essential drill-related actions: Drill Through Drill Down Drill Up Ability to hide or disable unnecessary options based on report design. Business Impact: Improves overall user experience and usability for business users. Reduces training efforts and user confusion. Simplifies report interaction and navigation. Enhances governance and control over report behavior. Encourages wider adoption of Power BI reports across the organization.   ... View more

It would be valuable for Fabric Eventhouse to provide a built-in, standard replication service for cross-region data redundancy and failover. Today, there is no native solution, and teams must rely on custom approaches.   A first-class, Fabric-native replication capability would simplify BCDR and improve reliability for production workloads. This includes built-in cross-region redundancy and failover for regional outages, as well as native data replication scenarios such as Azure Data Explorer (ADX/Kusto) to Fabric Eventhouse (KQL DB) and Fabric Eventhouse to Fabric Eventhouse across regions. ... View more

Currently fabric warehouse permission management is complicated. There are two sets of permission management, one is fabric workspace role, the other is sql syntax. Workspace Viewer implicitly grants ReadData on every warehouse in the workspace. Admins who want granular access must either (a) avoid Workspace Viewer entirely or (b) issue per-table DENY — which is the opposite of how SQL Server has worked for decades. Especially when we have hundreds of tables, users, views, roles, schemas, the permission management is complicated that we need to manually grant deny permission each time when new users or new tables are added. Also there is no integrated UI for object-level permission, Every GRANT / DENY / CREATE ROLE must be done in T-SQL. There is no view to see "who can access what" on the warehouse — admins must hand-query sys.database_permissions. Also both the configuration under "Manage Permission" and fabric workspace role will not be added to DMV.  Note: Fabric SQL Database already exposes "Manage SQL database-level roles" in the portal — maybe bring the same experience (and extend it to object-level) to Warehouse. With AI innovation, we were also wondering if it's possible to add AI-assisted permission editor: natural language → generated GRANT / DENY with preview, plus least-privilege suggestions.   Thank you for your insights ... View more

Suggestion: Stable Power BI App URL and Permanent Alias One challenge faced by enterprise users is the difficulty in maintaining a single, permanent URL for Power BI Apps and reports across updates, migrations, and content changes. While App URLs are generally stable, organizations often experience issues when sharing report-specific links, restructuring content, or migrating workspaces. I would recommend introducing a Permanent App Alias URL feature that allows administrators to define a custom, immutable URL for Power BI Apps (for example: /apps/loyalty-dashboard). This alias should remain unchanged regardless of report additions, removals, app updates, workspace migrations, or content restructuring. Additional enhancements could include: Automatic redirection from old report links to the latest published version. A centralized URL management page for App Administrators. Version-independent links that always point users to the most current report within an app. API support for managing aliases programmatically. This would significantly improve user adoption, reduce broken links in emails and documentation, simplify governance, and lower support overhead for enterprise BI teams. ... View more

I used Microsoft Fabric OneLake external data sharing to share OneLake data from Tenant A with Tenant B. OneLake diagnostics was enabled on the Tenant A side.   After that, a user in Tenant B accessed the shared data, and an access record was output to the OneLake diagnostics logs on the Tenant A side. At that time, the logs did not record the Tenant B user. Instead, the user who created the external data share in Tenant A was recorded in the executingUpn column.   I understand that this behavior may be by design, because the external tenant user information may not be directly displayed in the provider tenant, or because access through external data sharing may be recorded under the permission context of the user who configured the share in the provider tenant.   However, from an audit and security investigation perspective, it is difficult to determine from the logs alone whether the access was a direct access by an internal user in Tenant A or an access by a user in Tenant B through external data sharing. External data sharing is an important feature for securely sharing data across tenants.   Therefore, I would like OneLake diagnostics logs to clearly identify when access is made through external data sharing. For example, the following types of improvements would be helpful:   Example: ・accessContext = External data sharing ・accessType = External share access ・isExternalDataSharingAccess = true ・Or display additional information for executingUpn, such as: 　・External tenant user 　・Access via external data sharing   It is not necessary to show the actual UPN of the external tenant user. At a minimum, I would like the logs to make it possible to distinguish between direct access by an internal user in the provider tenant and access through external data sharing.   This would allow Fabric administrators and data owners to more accurately distinguish expected access through external data sharing from direct access by internal users when reviewing OneLake diagnostics logs.   In enterprise environments, auditability and traceability for cross-tenant data sharing are important. Therefore, I believe this improvement would be very useful for operating OneLake external data sharing. ... View more

The nice 'clean' way of handling this usually is to have a single table, then use views for your role playing dimensions. But due to the limitation of views in semantic models you generally don't want to do this as it results in directquery being used. So instead you are forced to duplicate your dimension tables into your semantic model which goes against normalisation principles. Users have suggested using USERELATIONSHIP instead, but this approach is insufficient as you can not use measures in certain scenarios. Ie as the rows in a matrix visual.   Other alternatives include flattening the source tables, but this is not ideal as then you have gaps in your data based on what is available in the source. ie if used in a date range you get awkward gaps in your visual based on the presence or lack of in your source data as opposed to a proper dimension table. ... View more

When I want to format multiple/all the columns in a table based off a condition in one of the columns, I have to add the conditional format to each column in my table individually. I think it'd be really cool if there was a feature where I can either copy/paste the conditional formatting to selected columns or if there was a way to format all the columns at once. ... View more

The current card visual forces users to overlap elements or waste copious amounts of time creating custom visuals. The new card feature should give users the ability to create multiple cards in a single container and provide a greater level of customization. ... View more

It would be beneficial to incorporate features from Pivot tables that allow for the expansion and collapse of columns and hierarchical column groups within tabular visuals. This would not only solve the current limitations of matrices but also provide report creators with the flexibility to hide and show rows and columns, saving these settings for future use, thus eliminating the need to scroll through irrelevant data. ... 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

Enabling customized calculations at the query level for subtotals and grand totals would offer greater flexibility in reporting and preserve performance. Efficient organization of control settings to modify the style of these totals separately will empower report creators to achieve their desired appearance, while addressing their need for more control and customization in reporting. ... View more

Right now there's no way to run a custom containerized job on Fabric. The execution has to happen on a remote endpoint you stand up and maintain yourself (Azure Function, ACI, etc.) that Fabric just calls out to. Notebooks and User Data Functions cover Python, but not "bring your own image." Would love a "container job" item, point it at an image in ACR, give it a command + env vars + resource limits, run it on Fabric-managed compute, trigger it on-demand or on a schedule, and have the logs/run history show up in the monitoring hub like any other Fabric job. Today I run things like dbt and custom data ingestion jobs in Azure Container Apps Jobs, orchestrated from ADF. I'd happily consolidate all of it into Fabric if I could run the containers natively instead of keeping a separate compute plane around just for the "run my image" cases that notebooks/Spark don't cover. Anyone else running into this? Is there a roadmap item I've missed? ... View more

I believe there are several updates needed to Power BI subscriptions: Gate subscription ability.  Right now, this is all-on/all-off feature.  I would like this feature to be gated for users/security groups like almost every other setting in MS Fabric (e.g. allow only certain users/groups to create subscriptions). Zero visibility.  Need to see subscriptions on monitor tab Need to know impact on CUs from these subscriptions Need to know everyone reports were sent to (E.g. if we have one subscription is sent to 5 people, we would need 5 records) Need to know when upcoming subscriptions are going to be run Purview labels are not respected in subscriptions.  If someone sets up a label for the data in a report, the subscription does not ensure that the user(s) on the subscription are allowed to actually see that data; and since we have not gating by security group (see first bullet), they cannot be controlled that way either No dynamic data for "standard" subscriptions.  It would be great to have the ability to have dynamic data input into the email subject or body.  Right now the only option is static text. No CC or BCC settings.  It would be great to have CC and BCC options. All emails get sent from PowerBI service.  It would be great if we could use another SMTP server (set at tenant and/or workspace level) All emails get sent with the same template.  It would be great if we could use a custom template (set at tenant and/or workspace level) Fabric semanitc model w/ all Fabric users/groups.  There should be a native Fabric semantic model that contains all of the objects (workspaces, reports, users, groups, etc...) that could be leveraged by all who select "Dynamic subscription". I have put these in my priority order   @DataZoe@DataZoeMS  ... View more

Imagine a world where report creators can automatically apply slicer and filter selections based on specific logic, revolutionizing data analysis and user experience. This innovative approach eliminates any need for complex workarounds, optimizes slicer functionality, and paves the way for more efficient and effective data reporting. ... View more

We would like to propose an enhancement to improve efficiency when working with SharePoint data sources. Currently, when connecting to a SharePoint site, all available files are loaded, and users must then apply filters to identify and work with the required files. This process can be time-consuming and resource-intensive, especially in environments with a large number of files. We are requesting the ability to directly select or specify the required files from the SharePoint site at the time of connection, without the need to load and filter the entire dataset. Benefits of this enhancement: Improved performance by reducing unnecessary data loading Enhanced user experience with more streamlined file selection Reduced resource consumption for large-scale SharePoint environments This capability would significantly improve usability and efficiency for enterprise scenarios leveraging SharePoint with Fabric/Power BI. ... View more

Currently, notifications are triggered only when the overall capacity utilization exceeds the specified limit. However, we would like to have notifications configured based on specific scenarios such as interactive throttling, request rejections, and background rejections when they reach a defined threshold.   In addition, we require certain modifications to the surge protection settings.     Currently, it is not explicitly mentioned that the policy is implemented based on a 24-hour smoothed window, as described in the documentation. https://learn.microsoft.com/en-us/fabric/enterprise/surge-protection#set-the-background-operation-rejection-and-recovery-thresholds  ... View more