Hello. Power BI edit/change to the report (change in report sheet “measure x” from Hidden to Visible), doesn’t show as ‘Different’ in deployment pipeline comparison results. January 2026, this has been shown as ‘different’ in pipeline, now,  since beginning of February no change visibility. We created a support ticket to MS and got answer that,  "PG confirmed that the behavior you observed is expected in the current design and the previous behavior was actually unintended, so what you are seeing now reflects the intended functionality moving forward. Report-level changes are not included in the comparison results. Newer builds focus primarily on Model Schema and structural changes, while updates made at the visual/report layer are treated as report artifact updates rather than structural differences." Since lots of our Power BI changes are on report-level the previous behavior observed was better. From our perspective this was not an improvement. Hopefully the report level changes can be shown in deployment pipelines comparison results. ... View more

Allow adding custom named colors to the theme file, in addition to the built-in structural colors. These custom colors should be accessible: In Power BI Desktop UI to pick the colors In DAX expressions by referencing the defined color name ... View more

Enable defining multiple named color palettes within a single theme file. Additionally, allow assigning a specific palette to individual visuals, so different visuals in the same report can use different predefined color pallete. ... View more

The theme JSON file allows defining color palettes with more than 8 colors. However, Power BI Desktop UI only supports up to 8 colors when creating and selecting theme colors. Please extend the Desktop UI to support longer palettes, including: Creating and editing palettes with more than 8 colors More importantly picking from the full palette when choosing individual color ... View more

One major pain point for Power BI developers is the current workflow when working with live enterprise data via the Service. Currently, if the data resides on-premises and is only accessible through a gateway, developers have to: Build a report locally in Power BI Desktop Publish it to the Power BI Service Connect it to the customer’s gateway for live data Make query or transformation changes in the Service Download the updated report back to continue development This back-and-forth is cumbersome, time-consuming, and breaks the natural local development workflow. Proposal: Allow Power BI Desktop to directly leverage the On-Premises Data Gateway. Developers could work locally against live data, edit queries and transformations, and test reports without constant uploads and downloads, while still maintaining enterprise security. This small change would greatly streamline development, improve efficiency, and make working with live enterprise data much more intuitive. ... View more

Manage data source connections in a folder hierarchy. This improves governance for data sources and prevents connections that should be shared across projects or data teams from being listed together with personal connections in the same flat list. Use folders for data source connections to manage permissions for multiple connections at once. This avoids the pain of having to manage users and access separately for each individual connection when there are many connections. ... View more

We propose adding the capability to configure filters in the Fabric Monitor via URL parameters. This feature would enable users to quickly switch between and monitor different environments independently, simply by clicking a predefined link. Such functionality would streamline workflows, reduce manual configuration time, and improve monitoring efficiency across multiple environments. Thank you in advance ... View more

Please enable on the web version being able to Copy format and paste it in any other chart. It's very basic but so time saving since I use the web version only  ... View more

Description Microsoft Fabric strongly promotes concepts such as “Zero-ETL”, OneLake Shortcuts, Mirroring, and Direct Lake to reduce traditional ETL complexity. However, in real-world enterprise environments—especially hybrid architectures with on‑premises systems—ETL is often unavoidable, and this is where a critical gap appears. The Core Problem When Microsoft Fabric accesses on‑premises data through the On‑Premises Data Gateway (ODG): ODG can consume a large portion of on‑premises → cloud network bandwidth Neither Fabric nor ODG provides: Bandwidth throttling Rate limiting QoS or prioritization There is no first‑class observability for: Which pipelines or copy activities are responsible How much data they transfer When and how they saturate network links By contrast, Power BI semantic model refreshes are well covered by: Capacity Metrics Refresh history CU consumption visibility But Fabric Pipelines / Copy activities / Dataflows Gen2, which are often the largest network consumers, are not covered with comparable visibility. Why This Matters In enterprise networks: On‑premises bandwidth is shared with mission‑critical systems Uncontrolled ETL traffic can: Degrade core business systems Trigger operational incidents Block adoption of Fabric regardless of its analytical strengths Currently, customers are forced to: Infer ETL impact indirectly Manually correlate timestamps across multiple systems Treat ODG as a “black box” despite it being the critical choke point This is not a tooling inconvenience but a platform‑level design gap. Comparison with Other Platforms Other cloud data platforms explicitly address this concern: Databricks Provides pipeline‑level observability Supports rate limiting (e.g. maxBytesPerTrigger) Exposes network and throughput metrics as first‑class signals Snowflake Treats ingestion as a managed “entry point” Provides clear ingestion metrics and accountability per channel Microsoft Fabric, in contrast, effectively says: “Reduce ETL wherever possible,” but provides no adequate answers for unavoidable ETL. What This Idea Requests At minimum, Fabric should provide one or more of the following: Pipeline‑level observability for ODG traffic Data volume transferred Execution time Gateway‑level saturation indicators Correlation between Fabric Pipelines and ODG execution Even coarse, time‑window‑based correlation would help Optional throttling or rate‑limiting controls Per gateway Per pipeline or activity An official, supported monitoring story Instead of forcing customers to rely on log scraping or community workarounds Closing Thought “Zero‑ETL” is a valuable direction. But until ETL is truly eliminated, Microsoft Fabric must treat ETL traffic—especially via ODG—as a first‑class operational concern, not as something “outside the platform boundary.” Without this, Fabric adoption in serious hybrid enterprises will remain unnecessarily fragile. ... View more

Hello,   I have been exploring options in Power BI for creating reports with GIS data for plotting markers as well as shapes, both representing different features from a table. Something like this:     1. Shape maps: I could not find an option for markers in Shape Maps even though it let me add a custom map using a TopoJSON file.   2. Azure maps: Allowed either markers or boundaries at a time. There is a Reference Layer field under Format visual tab, which has Polygons and Points sections, but I did not find an option to display both of them together on my custom GeoJSON. Also, the legend parameter, which decides which feature gets different shades, allows only one feature at a time.   3. I have also tried the trial version of ArcGIS Online (Organizational Account) but could not find options for displaying differently shaded points and polygons, simultaneously on a custom GeoJSON. I have tried the join layer as well.   If articles for this already exist, please point me to them! I have come across a similar question in Power BI Forums so maybe it would be worth implementing? ... View more

Microsoft Fabric is increasingly being adopted as a corporate, shared, and mission‑critical analytics platform in enterprise environments. In many organizations, operational monitoring and alerting are centralized in enterprise observability tools (such as Dynatrace, Datadog, Splunk, etc.), and operational teams are not expected to rely on product portals or UI‑based monitoring for day‑to‑day incident detection. Today, Microsoft Fabric provides valuable capacity health and consumption signals (including throttling proximity indicators) through Real‑Time Hub and Capacity Overview Events. However: There is no native API or webhook to expose Fabric capacity health and consumption metrics directly to external systems. Integrating Fabric with enterprise observability platforms currently requires building custom solutions using Real‑Time Intelligence (Eventstream, Eventhouse, or custom endpoints). While Real‑Time Intelligence is powerful, it introduces additional architectural complexity for what is a very common enterprise requirement: basic health, consumption, and alerting integration. Requested capability We propose that Microsoft Fabric provides native, supported interfaces to expose capacity telemetry, such as: Capacity health status Capacity utilization / consumption Throttling risk or proximity indicators Capacity state changes These interfaces could be exposed via one or more of the following: REST APIs Webhooks Standard event endpoints designed for third‑party integrations Why this matters Providing direct APIs or webhooks would: Enable seamless integration with enterprise observability platforms Reduce the need for custom Real‑Time Intelligence implementations Improve operational maturity, governance, and compliance Align Microsoft Fabric with enterprise operational standards, where monitoring is centralized and automated This capability would significantly improve the operational readiness of Microsoft Fabric for large organizations running Fabric as a shared, business‑critical service. ... View more

Currently, ownership assignment is not supported while creating new goals via Rest API. This can only be done by editing the newly created scorecard from the Power BI UI and then assigning user/users. We require a feature where we would be able to assign an owner to the goal while creating the same via REST API. ... View more

@power BI  I would like the option to save to a single file someplace the default options for visuals I use often.   I prefer the dropdown for slicer. If I can have my preferred settings saved (with the file imported on opening PBI) it would save me opening an older report (or template) and fishing for that tweaked visual that worked so well. Recreating when you can't remember where that example is can be time wasting.   Something as simple as my default numeric display format is 0,0.00;(0,0.00)  and I would always like decimal numbers in my matrixes to default to this. One saved option per visual, ability to assign to the profile open kind of thing.   Or take an example from the older Delphi methodology and allow me to save a visual with current settings to a personal list (as another tab on the Build panel) with a name associated, such as a Matrix saved as AcctMatrix. (All those stored in a single file I can tuck away somewhere that can be shared among users who feel the same or want to use the same options. Clear text edited XML or something would be bonus.) ... View more

I need to be able to isolate AMD server vs Intel bookings and billings per week. Currently, I can get the server data inside of the Supplier Manager Operational Metric Dashboard. I would like to be able to see the AMD vs Intel. Thank you!  ... View more

The Azure Map visual in Power BI currently supports only a single data series for plotting geographic data points, requiring users to consolidate all location data into a single table before it can be visualised on the map. Enable the Azure Map visual to support multiple independent data series, allowing users to plot geographic data from different datasets simultaneously ,without the need to merge or reshape them into a unified table. Users should be able to add multiple map layers, each bound to its own data source, with support for the following geometry types: Points : e.g. asset locations, sensors, sampling sites Lines: e.g. pipelines, routes, networks Areas / Polygons : e.g. boundaries, zones, catchment areas In engineering workflows, it is common practice to overlay multiple spatial datasets to communicate complex relationships and spatial context effectively. For example, an engineer may need to simultaneously display infrastructure assets (points), pipeline routes (lines), and operational zones (polygons)  on a single map. Currently, achieving this requires significant data transformation effort upstream, which adds friction and reduces the agility of the reporting process. This feature would bring the Azure Map visual in line with industry-standard GIS tools, significantly improving its utility for engineering, infrastructure, and asset management use cases within Power BI. ... View more

I want to be able to copy/paste an Excel column with values so that the Text (Input) slicer understands them as separate entries. ... View more

Rename "Domain Admin" to "Domain Owner" in the Fabric interface. It should match Purview Terminology (Governance Domain Owner) and avoid confusion with "Domain Admin" used in Active Directory. Domain Owner is just a nicer, business-friendly term for non-technical staff ... View more

When importing a file from an Azure Storage Account, by default it can be processed in several formats. XML, a fairly common format, is not currently supported and therefore cannot be parsed. It would be good to have this option.   https://blog.fabric.microsoft.com/en-us/blog/continuous-ingestion-from-azure-storage-to-eventhouse-preview?ft=All  ... View more

Currently in Microsoft Fabric/PowerBI dashboards, it is only possible to lock all objects at once. This can be limiting when working with complex dashboards that contain multiple overlapping or closely aligned elements. I would like to suggest the ability to lock individual objects (e.g., tiles, visuals, text boxes, images) instead of only providing a global “lock position of all objects” option. This feature would provide the following benefits: Prevent accidental movement of specific visuals while editing other elements Avoid unintentionally selecting objects that are layered behind others Improve precision when designing complex dashboards Increase overall usability and efficiency during dashboard editing A per-object lock option (for example via right-click menu or properties pane toggle) would significantly enhance the editing experience and reduce frustration caused by accidental changes. ... View more