How to authenticate to log analytics using workspace identity in Fabric notebook or pipeline instead of SPN+Cert or SPN+Secret ... 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

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

In Power BI Apps, section headers are organizational only, they can’t serve as a clickable destination. To create a “hub” page and still group child items, authors must duplicate the name: once as a section and again as a page/link inside that section. This leads to redundant labels, extra maintenance, and user confusion. Current navigation lets authors add sections, links, and (optionally) one overview page, and the first navigation item becomes the app’s landing experience, but there is no way to make a section header itself open content. ... View more

It would be incredibly helpful if Power BI allowed users to share a specific filtered view of a report. Right now, I can open a report, adjust the filters to create the exact view someone needs, and save it as a personal bookmark—but that bookmark is only visible to me. I’d love the ability to save that filtered state as a shareable bookmark and send it to another user without having to engage power BI developers to save the bookmark state as a "global" selection. This would make collaboration faster and eliminate the back‑and‑forth of “which filters did you use?” ... View more

Many people use the Power BI Subscription service as part of a data pipeline (monitoring email inbox, automatically downloading them image, then using that image for things).   You recently changed the subject line of the email to begin with "Power BI report subscription delivery" without any warning, breaking several of our pipelines and resulting in confusion.   Please, before you roll out changes like this, notify people.   Thank you! ... View more

Currently, when embedding a Power BI report in SharePoint Online using the Power BI web part, URL filter parameters (such as &filter=) are ignored.   The same filter parameters work correctly when: Opening the report directly in Power BI Service Using reportEmbed URLs Embedding via iframe / SharePoint Embed web part   However, when the report is added using the native Power BI web part, the URL filters are not applied, even though the filter may appear in the filter pane. This leads to inconsistent behavior across embedding methods.   This creates a major limitation for enterprise scenarios where: One report is reused across multiple SharePoint sites Each site requires a different default filter (for example Market, Region, Business Unit) Default slicer selection needs to be controlled via URL Because the Power BI web part is the recommended and native SharePoint integration method, it should support the same URL filter capabilities as other Power BI embedding approaches.   Current workarounds require: Duplicating reports per context, or Using iframe embedding instead of the Power BI web part Both increase maintenance and reduce scalability.   Requested enhancement: Please add full support for URL filter parameters (such as &filter=) in the SharePoint Power BI web part to enable default filter and slicer state via URL.   This would significantly improve multi-site SharePoint + Power BI deployment patterns in enterprise environments. ... View more

Fabric customers rely on a shared metadata contract across ingestion, modeling, analytics, and AI. Descriptions for tables and fields exist across multiple Fabric engines, including Delta, SQL Warehouse, Semantic Models, and KQL, but today these descriptions are typically defined after ingestion and do not consistently propagate downstream.   This idea proposes enabling table and column descriptions to be authored in Dataflows during the ELT process and automatically propagated into Delta table and column comments, Fabric SQL and Warehouse metadata, Semantic Model field descriptions, and the OneLake Catalog. By setting descriptions at ingestion time, Fabric can establish a single authoritative metadata foundation that travels with the data across all Fabric experiences.   This ensures consistent discovery, understanding, and trustworthy AI-assisted analytics, while creating a durable metadata layer that benefits governance, self-service BI, Copilot experiences, and AI workflows without requiring duplication or post hoc documentation.   Delta and OneLake (Foundational Layer) Delta supports native table and column comments, making it a natural system of record for metadata.   Example concepts: Table-level comments describing dataset purpose and scope Column-level comments describing business meaning and usage Ask in this idea: Allow Dataflows to set Delta table and column comments during write operations so metadata is stored with the Delta files. --- Fabric SQL Engine (Lakehouse SQL Endpoint) Fabric SQL can read metadata from Delta and expose it through SQL metadata views and extended properties. Supported concepts Table descriptions Column descriptions These descriptions are visible in SQL tooling and data exploration experiences and can be surfaced to Copilot. Ask in this idea: Inherit Delta comments authored by Dataflows and prevent metadata loss unless explicitly edited.   Fabric Data Warehouse Fabric Data Warehouse supports first-class metadata similar to SQL Server and Synapse. Supported concepts Table descriptions Column descriptions Schema descriptions Ask in this idea: When Dataflows write to Warehouse-backed tables, descriptions should flow automatically and not require re-authoring.   Semantic Models (Power BI) Semantic Models rely heavily on field descriptions for usability and Copilot effectiveness. Table descriptions Column descriptions Measure descriptions These descriptions are shown in field wells and are critical for self-service users. Ask in this idea: Auto-populate and keep Semantic Model descriptions in sync with OneLake metadata unless intentionally overridden.   KQL Database in Fabric KQL supports documentation at both the table and column level. Table-level documentation Column-level documentation This metadata improves query autocomplete, exploration experiences, and AI-assisted querying. Ask in this idea: When Dataflows land data into Eventhouse or KQL databases, apply descriptions automatically and treat them as part of schema evolution.   OneLake Catalog OneLake Catalog should treat table and column descriptions as first-class metadata. Surface descriptions consistently across Lakehouse Surface descriptions across SQL and Warehouse Surface descriptions across Semantic Models Surface descriptions across KQL Key ask: Dataflow-authored descriptions should flow into OneLake once and become the canonical metadata source that downstream tools consume. ... 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

Dear Microsoft Team, We are currently transitioning from Power BI Report Server (PBIRS) to Power BI Service to support hybrid reporting scenarios that combine on-premises and cloud data sources. While the Service offers great capabilities for composite models and cloud integration, we have encountered a major limitation regarding subscriptions for paginated reports (RDL). In PBIRS, we rely heavily on advanced SSRS-style subscription features such as: File share delivery Flexible scheduling Custom delivery extensions However, in Power BI Service, subscription options for RDL reports are restricted to basic email delivery or require Power Automate. This creates significant challenges for our end users, who are not familiar with Power Automate and expect a simple, native experience similar to PBIRS. Our Request Please consider: Adding full SSRS-style subscription capabilities for paginated reports in Power BI Service, including file share delivery and advanced scheduling. Providing a native solution that does not require Power Automate or Semantic model use (since we don't use it for RDL 80% of the time) for advanced subscriptions, to ensure ease of use for non-technical end users. In moder times analysts use combined solutions for datasorces on-prem+cloud often but with your PBIRS you are limiting there Power Bi and at the same time limiting PBI Srvice as well for RDL dynamic subccriptions.  Why This Matters We have many reports that combine on-prem and cloud data, making Power BI Service essential for hybrid scenarios. Limiting subscription options creates a major adoption barrier for enterprise customers transitioning from PBIRS. Our end users need a seamless experience without additional complexity or reliance on external tools. We believe enhancing subscription functionality in the Service will significantly improve enterprise adoption and align with the flexibility currently offered in PBIRS. Thank you for considering this request. Please let us know if there are any plans or timelines for improving subscription capabilities in Power BI Service.   Thank you!  Best, Maria Suncheleeva  ... View more

To address the challenges of organizing and presenting data due to the limitations of column and row headers, a potential solution would be to implement a new matrix visual with customizable controls, allowing report creators to adjust the dimensions of columns and rows, group them hierarchically, apply diverse styles, and use conditional formatting. ... 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

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

It is possible to dynamically control and even disable a button action that triggers page navigation, but this is not possible with bookmark actions. It would be very helpful, for example, to disable such actions based on RLS or specific contexts selected by the user. ... 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

Fabric currently supports custom Environments for PySpark notebooks, but Python notebooks (preview) cannot use them. In Python notebooks, the only available kernels are Python 3.10 and 3.11, and the only way to install packages is via %pip install, which is session‑scoped, not reproducible, and not aligned with Fabric’s managed environment model. This creates a major gap for teams who want consistent dependency management across both PySpark and Python workflows. Request Please add support for: Custom Python environments (similar to virtual environments) Attaching those environments to Python notebooks Managing Python‑only dependencies through the Environment UI This would bring Python notebooks to parity with PySpark notebooks and enable reliable, repeatable development without %pip workarounds. Example In PySpark notebooks with an Environment, this works: python from faker import Fakerfake = Faker()fake.name() In Python notebooks, it only works after:   %pip install faker …and must be reinstalled every session. Enabling custom environments for Python notebooks would solve this cleanly and improve the overall Fabric development experience.   ... 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

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

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