In Azure we give our resource a name using a standard naming convention. For Fabric one of our capacities is named something like xxx02prdxxxfab001 (xxx1 = our prefix, prd = production, xxx2 = solution abbrivation, fab = fabric resource, 001 = capacity number 1). We are using this naming convention, because properties of a resource can change and you don't want te get stuck with a resource name with a specific name, that might not be valid in the future.   But this name is now also the name of the capacity in Fabric, where, in Fabric, we actually want to rename it to a name more recognizable to it's properties, like "F64 production capacity". The option is already there in Fabric on the capacity settings, but you can't change the name after clicking the pencil button. We are using multiple capacities, so it would be usefull to have the ability the rename the capacities.   ... View more

PBIP Format is available since 2023 for Power BI Desktop regular version. Power BI Desktop for Report Server is missing this new Format, forcing developers still to use PBIX Format. Supporting PBIP for On-Prem Development would enable teams to use git for their development process. ... View more

We need insights into the storage consumption of active files and soft deleted files.   The Capacity Metrics App's Storage page should have the ability to show the storage size of soft deleted files and the storage size of active files. And the total.   Today, it is not possible to differentiate between storage size of soft deleted files and active files in the Capacity Metrics App. ... View more

Make it possible to see storage consumption at Item level in the Capacity Metrics App.   At the moment, we can only see storage consumption at Workspace level, and this makes it difficult to pinpoint exactly which items (lakehouses, warehouses) consume most storage in our workspace.   Displaying the storage size (gigabytes) at Item level would increase the usability of the Storage page in Capacity Metrics App. ... View more

Hello Team, This is to inform you that when we use the composite model and want to refresh it every 15 minutes, due to limitations, we can only refresh it every 30 minutes. However, in direct query mode, we can refresh the dataset every 15 minutes. We are requesting you to add the same feature in composite mode to refresh the dataset every 15 minutes. Thank you ... View more

Currently the server name for SQLDB (and DW) is a double GUID of {tenant-Id-workspace-id.}database.fabric.microsoft.com   This causes a lot of issues as 1. This is impossible to remember 2. We ahve no way to distinguish test from PRD   We request user frirnedly DNS Names like  Prodata-Sales-DEV.database.fabric.microsoft.com   This would help clearly label an worksapce as DEV or PRD and avoid confusion and make the platform easier to work with., ... View more

Popout windows for DAX Window, TMDL view, DAX query, Relationship diagram etc   Avoid having to jump between screens or using external tools, just to have context in a second window ... View more

When we restore a Fabric SQLDB it changes the database names which break the ETL and all customers connecting to it.  We then have to ge everyone globally to change the connection string, which means a restore has customer downtime of days.   Can you fix this so that a restore keeps the original database name and doesnt break the connection string ?   Ideally a restore shoudl restore "as was" unless we choose to restore to a different Artefact Name or workspace.     ... View more

When we connect to the DB we have to enter the Database Name  whgich is a GUID. Please make this database name equal to the same name as trhe SQL End Point and database name in Fabric. This imporves usability, and allows for the same 3 part TSQL to run on SQL DB v SQL End Point. At the moment we have different TSQL Statements if we query SQLDB v SQL End Point which is not optimum   ... View more

System tables on the data flow should be excluded when the user retrieves data. These system tables pertain to implementation details rather than the information itself. ... View more

Power BI's alerting feature can send notifications when a set condition is met, but it should be able to send notifications again when a condition changes from a set condition to a further set condition. ... View more

I would like to see a feature where it's possible to add a footnote to a visual. This would help to make certain filters in the filter pane or inside of measures more explicit to report consumers, or would allow for providing additional context on what is displayed in the visual, especially when these types of details might not be important or central enough to include in the Title or Subtitle of the visual. I would imagine that a footnote could look similar to a Title or Subtitle on a visual, so that a report developer could use either a string literal value as a footnote, or add a measure as a footnote to a visual. The report developer could then also choose the appropriate font, color alignment, etc. for their footnote. If possible, it would also be nice to have the ability to add a divider or some customizable space between the bottom of the visual and the footnote. ... 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

It would be really useful to have security settings to show or hide individual report pages. Currently, audiences control access only at the report level, not per page. ... 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

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

🔹 Problem: Power BI users often need to document transformation steps, DAX logic, and analysis notes, but there’s no built-in way to add comments or notes inside Power BI. This makes it difficult to track changes, collaborate effectively, and maintain reports efficiently. 🔹 Idea: Introduce a "Comment" or "Notes" panel to allow users to: ✔ Add personal notes on transformation logic in Power Query. ✔ Document key insights in data model relationships & measures. ✔ Attach questions & hypotheses for further analysis. 🔹 Impact: 💡 Enhances workflow tracking & report maintenance. 💡 Reduces reliance on external documentation. 💡 Improves team collaboration within Power BI. ... View more

There should be a secure way to pass secrets or keys when making an API call (e.g. web.contents) in Power Query M.   Suggestions:   A) Make it possible to enter and edit secrets in Power Query, similar to how we enter and edit data source credentials in Power Query. Make these secrets encrypted and redacted. The secrets should be available to use as variables in the M code. When entering a secret, we would give it a name, which we can reference as a variable in the M code. We would only see the name, but the value would not be visible (the value would be redacted).   B) Make an Azure Key Vault connector for Power Query, that will make it possible to fetch secrets from AKV and assign the secret to a variable in the M query. This variable can be passed as part of the header in an API call.   C) Make it possible to redact some variables in M, so that we can use secret variables without the value being visible in the Power Query user interface.    The main point is that we want a way to use secured and hidden secrets as part of API calls in Power Query. ... View more