When interacting with a line chart, if you click on an item in the legend, it highlights that legend item and also highlights the line in the chart represented by the selected legend item.    Unfortunately, this doesn't work the other way around. If you select a line, it will highlight the line, but it doesn't highlight the legend item matching the line selected. It would be great and valuable from a UX perspective to make the highlighting work both ways.  ... View more

Custom app color themes please? ... View more

The current report sent to us daily is a valuable reminder tool, to bill the patients BOOKED in schedule. I would find value in a report sent to us daily/weekly that contains 3rdparty eligible clients that HAVE NO upcoming appointment but are due for billing (WSIB, ODSP, VAC) ... 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

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

I used OneLake shortcut transformation in Microsoft Fabric to convert Excel files into Delta tables in a Lakehouse.   I confirmed that DESCRIBE DETAIL for the target tables shows format = delta, and that physical Parquet files also exist.   After that, I referenced these tables again from another Lakehouse using OneLake shortcuts, and then tried to create a Direct Lake semantic model from the downstream Lakehouse. However, when creating the Direct Lake semantic model, the following error occurred: We cannot refresh this semantic model because one or multiple source tables either do not exist or access was denied.   The target tables are displayed correctly in Lakehouse Explorer and are recognized as Delta tables. Also, in my previous experience, Direct Lake can be used with similar multi-hop shortcut architectures when the shortcut-transformed tables originate from CSV or JSON files.   Therefore, this behavior does not appear to be a general limitation of multi-hop shortcuts. Instead, it seems to be a product limitation or feature gap related to the following combination: ・Excel-originated shortcut-transformed tables ・Multi-hop shortcut lineage ・Direct Lake semantic model validation behavior   Excel files are widely used by business users. Therefore, it is very important to be able to easily convert Excel data into Delta tables in Fabric, reuse them across multiple Lakehouses, and analyze them efficiently with Direct Lake.   Currently, I am using a DirectQuery semantic model as a workaround. However, if a table is recognized as a Delta table, I believe it should be possible to create a Direct Lake semantic model from a downstream Lakehouse as well.   Request: Please support Direct Lake semantic model creation for Delta tables created by Excel shortcut transformation, even when they are referenced through multi-hop OneLake shortcuts. This improvement would make it easier to naturally combine business data usage starting from Excel, reuse across Lakehouses, and high-performance analytics with Direct Lake. ... View more

I've been looking into how I can add AI metadata to a semantic model programatically. This allows the push back of AI instruction metadata back to the users in a data ingestable process, notebook and pipeline, bypassing the Fabric 'Prep data for AI' user interface, which you may not want to give to users for iterating through instruction sets.   This works well for some metadata (like table and column descriptions), but does not allow for AI instructions to be written to the model progamatically. I can edit the culture tmdl file via GIT, but when updating back into Fabric from GIT, the AI instructions come back blank.   It would be great to have a REST API endpoint for writing Prep Data for AI configuration.   Cheers, Kev   ... 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

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

In fabric the visibility into users, app audiences and published reports in a particular workspace would be incredibly valuable, particularly from a governance point of view.    Senior management often require visibility into reports, audiences and audience members. If Microsoft are recommending to publish via app audiences, this data should be readily available to analyse and display.   ... 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

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, 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

We are trying to migrate from ADF to fabric and we have cosmos storage(Gen 1 )stored in ADLA in ADF and there is Gen 2 as well but to sync that as well it is asking for ADLA with service principal and client credential key...In ADF ,ADLA account is set using managed identity with no credential based access...When trying to migrate our ADF pipeline to Fabric ..We use Scope activity but connection infrastructure part is where we are unable to connect in fabric. ... View more

As a small and growing business, we have a Microsoft Partner - Partner Success Core Benefits package to support our business operation. We have Copilot functionality on all required business tools, except Power BI - this is due to our package not having F2 or higher Fabric capacity or Power BI Premium capacity P1 or higher - we currently have Microsoft Fabric (Free) and Power BI Premium Per User (PPU). To enable CoPilot functionality in Power BI, we would need to enhance our package at an additional cost, which we would not expect when the package is designed with our type of business in mind. We suggest the Partner Success Core Benefits package is enhanced for all, to enable Copilot functionality for Power BI.   ... 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

Summary I propose adding a built-in pane in Power BI Desktop where developers can manage report-related tasks and notes, with optional integration to tools like Jira, Azure DevOps, or similar platforms. Problem During development, it’s common to track tasks, issues, and notes for each report page. Today, this requires switching between Power BI and external tools, making it harder to keep context and stay efficient. Proposed Solution Introduce a “Tasks and Notes” pane that allows developers to: Add notes and tasks linked to specific report pages View tasks relevant to the current page Connect to Jira, Azure DevOps, or similar tools Link or create work items directly from Power BI Sync task status between Power BI and external systems Benefits Reduces context switching Keeps tasks tied to report structure Improves collaboration and transparency Aligns Power BI with modern development workflows Closing This would improve the development experience significantly, especially for teams already using structured work tracking tools. Would be interesting to hear if others see value in this type of integration. ... View more

I keep clicking create a ticket but keep getting directed to the home screen where I can suggest ideas, there appears to be nowhere that I can log that the system does not work and show our teams attendance figures, can this be resolved as this happened for weeks last period too, so we cannot view our teams office attendance ... View more

Currently, to allow business users to access Fabric Warehouse or Lakehouse data through Excel, we need to provide workspace-level access. This exposes additional artifacts and workspace items that users do not actually need or donot need to view or have access to. It would be great if Microsoft Fabric supported more granular access specifically for Excel connectivity, allowing users to: Access only Warehouse/Lakehouse SQL Endpoints Query authorized tables/views from Excel Avoid visibility into unrelated workspace artifacts, reports, notebooks, pipelines, etc.   Many business users still rely heavily on Excel for analytics, so enabling secure and limited Excel-based access would greatly improve governance while supporting real business workflows. This would help maintain the principle of least privilege while improving the overall user experience in Fabric and analytics. ... View more