I want to restrict the purchase of custom visuals for Power BI regardless of certification. ... 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

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

When exporting to PDF, the default setting is to select only the current value, but it should be possible to change this for each report. For example, this is useful when you want to export all pages for Report A, but only the current page for Report B. ... 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

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

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

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

In Power BI Service (cloud), Paginated Reports do not have zoom controls, unlike in on-prem SSRS, where users could zoom in/out.   This feature is missing for paginated reports, causing usability concerns during migration to the cloud. ... View more

When making changes to Power BI content, there are cases where unnecessary parts are modified unintentionally. These changes may go undetected during review and can lead to issues later on. As a feature improvement, we propose adding a function that allows users to compare differences before and after modifications in Power BI. ... 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

I'd like to propose the addition of a "Close, Apply, and Refresh All" option within the Transform Data panel in Power BI Desktop.   As part of our ongoing cost-efficiency initiative, we’ve transitioned our enterprise cube into Power BI data models, leveraging native queries and query folding to optimize performance. With incremental refresh enabled, we must update the RangeStart and RangeEnd parameters and refresh all data prior to publishing. This step is critical—if skipped, the web-based Power BI service initiates a full refresh post-publish, resulting in a 30–60 minute lag where visuals may appear blank or error-prone, disrupting the user experience.   Currently, after updating the parameters and selecting Close & Apply, only the tables with incremental refresh configured are updated. To fully synchronize the model, we must then manually trigger a second refresh for the remaining tables—effectively doubling the wait time.   Introducing a "Close, Apply, and Refresh All" option would streamline this workflow by consolidating both steps into one. This enhancement would: Reduce total refresh time and manual intervention. Improve publishing efficiency. Minimize front-end disruption for report consumers.   This small UX improvement could yield significant time savings and operational consistency for teams working with complex, parameter-driven models. ... View more

Bookmarks are currently not supported in PowerBI org apps. Could this feature please be added? ... View more

Hi,    We have numerous clients running Quantios Core, which is Dynamics 365 Business Central with an extension from Quantios to include new tables and functionality within Business Central for the product QCore.   We want to do our reporting, analysis, and merging other data sets in Fabric but having issues getting data into Fabric.   Would it be possible to get mirroring up and running so that we can have the source system data within Fabric managed by Microsoft so that we can get busy with analytics, modelling and reporting for our clients.   Thank ... View more

In each report page settings, there should be an option to write a 'Page description' (much like the Page synonyms option).  I have mocked up the appearance of this section above.  Then, if we use the 'Page Navigator' visual, we should be able to enable the tooltips.  When hovering over each button/menu item, tooltips would display the description of that page, as it was specified in the 'Page description' section.  Please refer to the mockups above which I created.  I believe it is crucial for accessibility purposes, and is a frequent request of my customers, which I currently cannot fulfill.  This seems like a relatively simple addition for Microsoft to develop.  Thank you in advance.   ... View more

The primary axis are outdated and require significant improvement when compared to Excel. This makes it difficult for report creators and often leads to problems when trying to manage and style them effectively. By offering more format settings, greater control over displayed data can be provided, especially if axis ticks, new gridlines, and separators are also included. ... View more