Hello, I would like to request an enhancement to the Page Navigator visual so that it offers the same layout options available in the Button Segmentation Slicer.                                 Layout options: Orientation: horizontal / vertical / grid Style: blocks / full screen Number of columns Automatic grid Spacing (gap) between buttons Overflow style: paginated / continuous scrolling (scroll)           These same options are not available in the Page Navigator, which limits the use of this visual in reports that rely on button-based navigation. I request the evaluation of this feature, allowing the Page Navigator to offer the same layout configuration options as the Button Segmentation Slicer. This enhancement is relevant in scenarios with a large number of pages, where navigation needs to be intuitive, reducing the need for alternative solutions and manual customizations. ... View more

Hi We have F256 capacity and we have recently purchased 64 SKUs. Unfortunately, there is no way for us to upgrade the capacity by 64 SKUs, but rather can only jump to the next available one, in your case is F512. This is not feasible option. Provide an option to upgrade the capacity with multiples of 64 SKUs. ... View more

When I read a Key Vault secret using the Web Activity in Fabric Pipelines, the secret value appears in the task’s Output panel after execution. This exposes sensitive information to anyone with Monitor access, which is not acceptable for our security requirements. In contrast, reading secrets from a Notebook automatically redacts the value. We want to use connections, which is why we rely on the Web Activity rather than a Notebook. This allows us to share credentials without granting every Workspace Contributor (and above) direct visibility into the Key Vault. ... View more

Currently, there is a known limitation where the Download option is greyed out or unavailable when a report or dataset is part of a deployment pipeline and has been deployed from one stage to another. We would like this functionality to be supported, as it would allow us to download the report from a specific pipeline stage and deploy it to other workspaces as needed. ... View more

The UI for using variables in a shortcut could also be enhanced by adding the "Value set name" below the value when shown in the "Manage Shortcut" slide out.   This would indicate which set the value came from to verify it is as desired if you don't recognize the guid (don't we all have every guid in our tenant memorized already? who needs workspace names, I know all the guids!!!)     ... View more

When using a variable library to actively set shortcut path information (workspace, item, path) if a selected variable value(s) result in a non-existent location, the intentional assignment of the variable value should be forced into the shortcut, which shall cause a shortcut error that would be visible in the left hand lakehouse explorer/navigation (red X or similar error symbol).     The current default keeps the old or default value, which could erroneously have some shortcuts pointing to the new value while others in the same lakehouse point to an old value.  For example, this could expose DEV tables in a TEST lakehouse when the intended selection of the TEST variable value set is to only show valid shortcuts to underlying TEST location. Other than the error at the time of updating variables on the lakehouse, there is no perminent indication for users in the future that some of the shortcuts are not pointing at the desired location. Similar to @frithjof_v  idea disabling the default value when a variable library is deployed across workspaces and a selection is not made, but differs by forcing an error when a selection is actively made that doesn't resolve to a valid path.  The other speaks to avoiding the default if no selection is made. ... View more

Buenas tardes a todos, me gustaria tener un reporte de uso modificacion y creacion de algun archivo de BI ... View more

One of the most annoying behavior of report designers is to rename fields in visuals in cryptic way without standards and you won't understand at a first sight which field from which table had been used.     AFAIK (without using any external tool or power bi project - just staying in PBI Desktop), the only thing you can do is to hover fields with the mouse and look at the tooltip that shows you the original field/measure home table and name. for further anlaysis you need to move to the data pane and search it manually. Wouldn't it be nice to have a "Go to definition" that points the referenced field/measure in the data pane that you can activate directly in the context-menu right-clicking the field?     ... 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

It would be super helpful to get a connection string in SSMS with the workspace name instead of the very cryptic string you get today : Imagine being able to see: server name : WorkspaceNameDev server name : WorkspaceNamePrd That would greatly improve this experience. I know that you can manually rename them in SSMS, but that is not really good in a larger team setting and makes onboarding of new developers a pain. ... 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

Microsoft Fabric currently provides the “List Item Connections” REST API, which returns the connections used by a specified Fabric item. However, there is no REST API or UI capability to identify the list of Fabric items that are using a specific connection. This missing reverse lookup makes it difficult to perform impact analysis, governance, and dependency tracking for shared connections.   Users cannot easily determine which items will be affected when modifying or deleting a connection. As a result, managing connections in large workspaces requires manual and error-prone processes. Introducing a workspace-scoped API or UI view to list items associated with a connection would greatly improve discoverability, governance, and operational efficiency. ... View more

Adding Page-Level Conditional Formatting Rules in Power BI, a feature that allows users to define one rule and have it automatically applied across all visuals on the page. Ideally, it should also support applying the rule across all fields in a row for consistent, row-level highlighting. I’m suggesting this idea because I’ve personally struggled with managing conditional formatting efficiently in my reports. When I need consistent highlighting across a dashboard, for example, marking negative values or high-risk records, I have to repeat the same formatting steps visual by visual and column by column. This becomes time-consuming and hard to maintain. This feature would also help address another limitation: Power BI currently doesn’t support row-level conditional formatting. Page-level rules would be a practical solution that simplifies the process, ensures consistency, and reduces repetitive work for report developers like me. ... 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

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

Power BI / Fabric deployment pipelines currently do not support semantic models that include native queries, as documented here: https://learn.microsoft.com/en-us/fabric/cicd/deployment-pipelines/understand-the-deployment-process?tabs=new-ui#semantic-model-limitations This limitation has a significant impact on enterprise BI architectures, especially when working with large cloud data warehouses such as Snowflake, Synapse, or BigQuery.   Why this is a real problem Native queries are often mandatory, not optional, to: Preserve query folding when Power BI parameters break folding in M Push filters and logic down to the warehouse for performance and cost control Build parameterized semantic models (environment, scope, tenant, time windows) Avoid large in-memory transformations in Power BI Removing native queries in these scenarios is not a viable solution without serious performance degradation.   Impact on CI/CD adoption Because of this limitation: Semantic models cannot be deployed via pipelines Teams must exclude datasets from pipelines or deploy them manually CI/CD becomes partial, fragile, and inconsistent Advanced, well-designed models are penalized, while simpler ones work This strongly limits the adoption of deployment pipelines in mature BI teams. Why this should evolve Deployment pipelines are presented as the standard CI/CD mechanism for Power BI and Fabric. To be enterprise-ready, they need to support semantic models that rely on native queries, or at least provide an explicit and safe opt-in mechanism.   Call to action If you rely on: Large datasets Cloud data warehouses Parameterized or performance-critical semantic models Proper CI/CD practices   👉 Please vote for this idea. This evolution would greatly improve enterprise adoption of Fabric deployment pipelines. ... View more

Hello Power BI Team, I would like to suggest a new feature for the Date Slicer. Today, when a report is refreshed, the date slicer keeps the last selected value instead of automatically updating to the latest date available in the data model. This creates a problem for dashboards that are updated daily, because the slicer continues to show an outdated date unless the user manually resets it. Requested Enhancement: Add an option in the Date Slicer properties allowing the user to set the slicer to automatically default to the most recent date present in the related table. For example: “Auto-select latest date in data” = On/Off When enabled, after every refresh, the slicer should automatically adjust itself to filter the report by the latest date loaded into the dataset. This behavior would be extremely helpful for operational dashboards that are updated every day and always need to reflect the newest data without user interaction. Why this feature is important: It improves usability and avoids outdated information being shown when a user opens the report. It eliminates the need for complex DAX workarounds or visual-level filtering tricks. It supports real-time and daily operational dashboards where the “latest available date” is always the default expected view. This feature would make the Date Slicer more intuitive and aligned with business scenarios where the newest data must always be displayed automatically. Thank you for considering this improvement! ... View more

Consider a test user who has been assigned Lakehouse  Write permission to a specific folder in a Fabric Lakehouse using one lake security roles. This permission reflects correctly in Azure Storage Explorer, and the user can access the folder as expected. However, the permission does not appear correctly in OneLake Explorer. Specifically, the Lakehouse does not appear under 'My Workspace' in OneLake Explorer for that specific user. Seems like a limitation with the one lake explorer as it is still in preview. Would be of great help if this is fixed. ... View more

There is a limit of up to 25 audience groups that can be created in a Power BI app. Publish an app in Power BI - Power BI | Microsoft Learn We need to increase the number of audience groups that can be created in a Power BI app. ... View more