Fabric Ideas

Changing the data source connection to a different server on Power BI Desktop, performing an update to restore the connection, and then publishing to the Power BI service will reset the on-premises data gateway settings. We would like to be able to change the connection destination for data sources located on different servers by changing the parameters of the Power BI service. ... View more

I migrated the DataFlow environment from a different environment. When using Dataflow Gen 2 activities, an error occurred in the pipeline. However, I confirmed that the DataFlow is functioning normally. Upon checking, I found that the option to allow parameter overwriting in subsequent executions was turned off, which caused the error when the pipeline was executed with specified parameters. The error message at that time was:"Dataflow refresh job failed with status: Failed. Failure reason: ~" This message does not clarify the cause of the error.I would like the error message to output a message indicating that parameters cannot be specified. Alternatively, I would like a feature added that automatically references the parameters specified on the DataFlow side. ... View more

Currently, when a report has a large number of subscribers, any edits made to its email subscription such as adding or removing recipients do not appear in the audit logs. This is due to a backend design limitation where the audit log file size must remain under 4KB. This limitation poses a challenge for users who lack premium capacity and cannot manage subscriptions via security groups. Without proper logging, it's difficult to track who made changes to the subscription settings, which impacts transparency ... View more

Hi all, Community!  I tried to find if someone already posted any idea related to it. I just found help tickets.  So, In my opinion it's vital and a game change for Microsoft to make available Multiple APPs in the same WorkSpace Premium. Today as far as I know we have this basic limitation (just one APP per WorkSpace) and this must be removed ASAP. Please MS Team, release this globally!  ... View more

I am using a Service Principle to Deploy Power BI Reports and Semantic Models in Fabric. After deploying the reports and semantic models, I have a need to refresh the data of data model automatically. The Model pulls data from a Dataverse URL environment. Currently, it errors out stating the credentials need to be reset before querying Dataverse. After doing some research, Power BI Service does not currently support service principal authentication directly for Dataverse connections in the same way it does for SQL endpoints or Lakehouses. Please allow for Service Principles to Edit Credentials and Oath2 Connections to a Dataverse URL in Fabric to allow for a Refresh of the Semantic Model data. ... View more

I want to restrict the purchase of custom visuals for Power BI regardless of certification. ... View more

After clicking on "Update All" button in "Updates" tab in "Source Control" pane - a dialog pops up indicating failure because the action would cause duplication in the workspace of an item name and type.   Customer would like to request a feature that after the Git update in the source control syncs the artifacts with existing artifacts if they have the same name. ... View more

There is a lineage view issue when a manually created Mashup query is used to build a semantic model that connects to a dataflow. The document mentioned that lineage between semantic models and dataflows is not guaranteed if a manually created Mashup query is used to connect to the dataflow. Lineage in Fabric - Microsoft Fabric | Microsoft Learn When connecting to the dataflow on the desktop and using the Power Query advanced editor, I tried entering the dataflow name and workspace name instead of the dataflow ID and workspace ID before publishing. However, they were unable to see the dataflow in the lineage view.   The customer requested a feature that allows the mashup query, which includes the dataflow name and workspace name and publishing it to display the lineage view correctly.     ... View more

We want to build a scalable, API-driven framework to manage data access in Power BI without manual steps. Our goal is to programmatically access: “Who has access to confidential data?” While the Scanner API helps retrieve workspace metadata, it currently does not include apps or audience-level access, which are critical for understanding report distribution. This gap limits our ability to audit and govern access effectively. Suggestions: Extend Scanner API to include apps and audience metadata Provide API access to user–report–audience mappings Align access metadata with sensitivity labels and endorsements This would enable automated governance and support compliance needs across large organizations. ... View more

PLEASE ... View more

Please allow changing the connector type—not just the data source—in an already published report, such as from ODBC to the Snowflake connector. ... 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

With the retirement of Power BI Data Marts, Microsoft is removing one of its most accessible, self-service data modeling, transformation, and querying - all in a single, user-friendly environment for PPU Users. Why This Matters For many users - especially those on Power BI Premium Per User (PPU) - Data Marts have been a foundational solution enabling them to: Perform light / heavy ETL  Build and manage curated data tables Run T-SQL queries directly in the service Serve up models and datasets seamlessly into Power BI In short, Data Marts allowed individuals and small teams to bridge the gap between BI and data engineering - without needing Fabric, Synapse, or deep Azure expertise. Now that Data Marts are being retired, Microsoft is forcing users to move to Fabric - a so called promising evolution of the analytics stack. But here’s the issue: There is no equivalent Per User license for Fabric. If PPU users lose Data Marts and cannot access Fabric without purchasing full-capacity SKUs, they are effectively being left behind - with no viable replacement. The Proposal: Introduce a Fabric Per User License Tier We’re not asking for a full-capacity solution. PPU users have never been burdened by the kind of capacity and cost constraints and throttling issues that are common with Fabric Capacity. Their experience has always been streamlined, reserved and self-contained without the fear of hitting capacity crunches and that’s exactly what a Fabric Per User license should preserve. Grants access to core Fabric workloads (Lakehouse, Pipelines, Dataflows, Warehouse, Databases, Notebooks) Enables low-code ETL - in the same spirit as Data Marts Allows users to experiment, learn, and build without enterprise-level investment Retains the ease of SQL endpoint access and dataset creation If Data Marts are being removed, users need an affordable, flexible entry point into the unified Fabric ecosystem - not one hidden behind £4,000+/month pricing. The Bigger Picture Microsoft Fabric is a powerful platform. But power only matters if it’s accessible and scaleable. By retiring Data Marts, Microsoft is removing a tool that empowered analysts, lean BI teams, and small scale businesses to build impactful data solutions. Without a Fabric Per User license to take its place, you risk alienating the very audience Fabric was meant to uplift. The Ask We’re not asking for more - We’re asking for a fair replacement. If you’re taking Data Marts away, give us Fabric Per User. It’s the right move - For Microsoft. For customers. For the future of analytics. If you share these concerns, I urge you to vote for this idea. It's time Microsoft hears the voices of users like us - those who are being forced to either leave the platform or spend thousands on Fabric Capacity just to retain the functionality we once had. Your vote can help drive real change and ensure Microsoft delivers a fair, accessible alternative for individuals and small teams. Thank you for standing up and taking the time to support this critical need.   ... 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

Interpreting visuals without a clear legend to indicate logic behind specific styles can lead to confusion and decision-making errors. An idea to enhance clarity and transparency by ensuring legends and tooltips accurately display colors, patterns, and other visual components influenced by logics, would enable report consumers to easily understand the applied logic and make more effective decisions. ... View more

Fabric/power BI users have requested a capability to programmatically update the gateway cloud connection associated with data sources used in Power BI semantic reports, via a REST API. Currently, changing or managing gateway cloud connections for data sources within semantic models (datasets) often requires manual updates through the Power BI Service interface or Power BI Admin Portal. This can become time-consuming and error-prone. Proposed Capability: Kindly introduce a Power BI REST API that allows users to update the gateway or cloud connection bound to a semantic model's data source. This feature would enable improved automation, governance, and scalability for enterprise BI teams using Power BI as a part of modern DevOps workflows. ... View more

Please allow setting defaule size of visuals and page dimentions in customer theme json for Organizational themes. However it is not working as expected . ... View more