New idea exchange ideas in Microsoft Fabric Community

Table Visual — Rounded Corners and Pill-Style Cell Backgrounds

urawizardharry — Fri, 04 Sep 2026 14:59:09 GMT

Add the option to display cell background colors as rounded rectangles or pill-shaped labels within the native Table visual.

Currently, applying a background color fills the entire cell with a solid rectangle. I would like the ability to adjust the corner radius and padding, creating a colored background around the value with space between the background and the cell edges.

Suggested formatting options:

Corner radius: Adjust from square corners to fully rounded pills.
Padding: Control the spacing around the value and inside the cell.
Background width: Fit the background to the text or use a consistent width across the column.
Conditional formatting support: Apply background colors dynamically using existing rules or measures.

This would be particularly useful for status values such as On Track, At Risk, and Behind, making them appear as clear, compact badges. It would improve readability and provide a more polished appearance without requiring custom visuals or SVG workarounds.

Add Global Alignment Controls for Power BI Matrix Values and Headers

AaronReasoner — Fri, 04 Sep 2026 14:08:26 GMT

Please add a global alignment setting for Matrix visuals that allows users to apply the same alignment, left, center, or right, to all measure columns at once.

This should apply to column headers, data values, subtotals, and grand totals.

Currently, value alignment often has to be configured individually under Specific column, which is very time consuming for matrices with many measures or field parameters.

A global alignment option would make matrix formatting much faster, more consistent, and easier to maintain.

Governed & Regulation for Publish to Web feature

Jaswanth_UNHCR — Fri, 04 Sep 2026 13:39:47 GMT

Notifying certain group of individuals if there is any enhancements performed on the semantic model which already hold an active Publish to Web code in place. This ensure in having more security and avoid sensitive/Org confidential data exposed to external audiences.
Log analytics to identifying the IP address/location/count of views for the PBI report that was hosted public using Publish to Web.
Sensitive labels for Publish to Web generated reports that will restrict even the contributor or above workspace role individuals in changing the data/visuals in the report except for the desired allowed IDs (who can modify like privilege access).
If the above points are not feasible, then at-least restricting the external audiences who are consuming the report via Publish to Web URL to only visualize the data projected in the visuals rather having any sort of data exposed that is present in the semantic model.

Allow to use service principal for VNet data gateway connection to SQL Server

Andrei-Sokalau — Fri, 04 Sep 2026 09:18:58 GMT

Service principal authentication is not supported for Azure SQL server connections when using an on-premises data gateway or a virtual network (VNet) data gateway. As a result we have to fallback to using less secure basic authentication with SQL user when we switch from Cloud connection to VNet gateway one. We would like to be able to continue to be using more secured access approach with service principal when we tighten the security by restricting access to DB. It would be also beneficial if Workspace identity mechanism is also supported (currently it is only available for Cloud connections).

Provide a Read-Only / Source-Safe Mode for Schema Shortcuts in Lakehouse

Junghyoen — Fri, 04 Sep 2026 06:37:13 GMT

Schema Shortcuts provide a much better management experience than individual Table Shortcuts because they preserve the source schema structure and allow multiple tables to be onboarded at once. However, users who need to protect source data are often forced to use individual Table Shortcuts instead, so please consider adding a read-only or source-safe mode for Schema Shortcuts that prevents accidental modification or deletion of source objects.

Current Behavior

In Fabric Lakehouse, Table Shortcuts and Schema Shortcuts behave differently when deleting objects.

- Deleting a Table Shortcut removes only the shortcut reference and does not affect the source table.

- Deleting a table under a Schema Shortcut can delete the source table if the user has write permissions on the target.

This behavior is currently expected by design.

User Pain Point

Schema Shortcuts provide significant operational advantages:

- Preserve the source schema structure.

- Allow onboarding multiple tables at once.

- Simplify management when a schema contains many tables.

- Reduce administrative overhead compared to creating and maintaining individual Table Shortcuts.

However, users who want to protect source data are often forced to avoid Schema Shortcuts and instead create individual Table Shortcuts for every table.

This creates a tradeoff between:

- Easier management (Schema Shortcut)

- Better source-data protection (Table Shortcut)

Feature Request

Please consider adding a Read-Only or Source-Safe mode for Schema Shortcuts.

Possible options:

- Read-only Schema Shortcuts

- Prevent deletion of source tables through Schema Shortcut references

- Allow removing a table reference from a Schema Shortcut without deleting the source table

- Additional governance controls for Schema Shortcut operations

Business Value

Users would be able to benefit from the manageability of Schema Shortcuts while reducing the risk of accidentally impacting source data.

This would be especially valuable for large Lakehouse environments containing many schemas and tables, where maintaining individual Table Shortcuts is operationally difficult.

Enhance Fabric Pipeline Monitoring with Parent-Child Pipeline Lineage and Parameter Visibility

dwramreddy — Thu, 03 Sep 2026 19:13:25 GMT

Currently, Microsoft Fabric Pipeline monitoring lacks several capabilities that are available in Azure Data Factory, making troubleshooting and operational support challenging in enterprise environments.

Problem:

When multiple parent pipelines invoke the same child pipeline through an Execute Pipeline activity, it is difficult or impossible to determine:

Which parent pipeline triggered the child pipeline run
Parent Pipeline Name
Parent Run ID
Trigger source information
Input parameter values passed to the child pipeline
End-to-end execution lineage across parent and child pipelines

In many cases, the Upstream Run column remains blank, and monitoring views do not expose sufficient execution details to identify the originating pipeline.

Expected Capability:

For every child pipeline execution, provide monitoring details such as:

Parent Pipeline Name
Parent Run ID
Child Run ID
Execute Pipeline Activity Name
Trigger Type (Manual, Schedule, Event, API)
Input Parameter Values
Pipeline Execution Hierarchy
Clickable navigation between parent and child runs

Business Impact:

Faster troubleshooting and root cause analysis
Improved operational monitoring
Better auditability and governance
Easier migration from Azure Data Factory to Microsoft Fabric
Reduced effort for support and production teams

This enhancement would bring Fabric Pipeline monitoring closer to the mature monitoring experience available in Azure Data Factory and would be highly valuable for enterprise-scale implementations.

Support Fabric SQL Database with workspace-level inbound Private Link

WorkFull22 — Thu, 03 Sep 2026 10:15:39 GMT

Fabric SQL Database supports tenant-level Private Link but not workspace-level Private Link. Securing a small number of databases therefore requires enabling Private Link across the entire tenant, introducing unnecessary operational constraints for unrelated workspaces, Power BI workloads and on-premises data gateways.

Improve Relationship UI Wording to Better Reflect Filter Propagation Direction

v-varunvv — Thu, 03 Sep 2026 09:39:56 GMT

The current relationship dialog can be confusing because the UI labels "From" and "To" do not always align with users' linguistic expectations regarding filter propagation. As per document : Relationships object (TMSL) | Microsoft Learn , the rows selected in the "To" end of the relationship will automatically filter scans of the table in the "From" end of the relationship.

It would be benififcial if the wording in the Power BI UI could be changed so that it accurately reflects the intended linguistic meaning.

Slicer option to show no data when no value is selected

740754 — Thu, 03 Sep 2026 05:57:45 GMT

Hello Power BI Team,

Description:

Currently, when the "Select All" option is enabled in a slicer, selecting it displays all related values as expected. However, when "Select All" is de-selected and no value remains selected, the visual continues to display the full data set instead of showing no data.

We require an option to treat an empty slicer selection as "no selection," so that dependent visuals return no data until the user explicitly selects a value. At present, Power BI cannot distinguish between "nothing selected" and "everything selected," as both apply no filter to the underlying data.

This behaviour is supported natively in other reporting tools, where clearing a filter results in an empty view rather than the complete data set. Providing this option in Power BI would remove the need for workaround measures and would significantly ease migration from those platforms, allowing existing report behaviour to be reproduced without redesign.

[This is a feature request]

Thanks,

Parameterize Dataflow Gen2 data source connection

frithjof_v — Thu, 03 Sep 2026 04:25:51 GMT

Allow the Dataflow Gen2 data source connection GUID to be parameterized and stored in a Variable Library.

This would allow the same Dataflow to use different connections depending on the workspace/environment, without modifying the Dataflow itself.

Hypothetical example:

Variable Library:

SourceConnectionGuid = 01234567-89ab-cdef-0123-456789abcdef

The Dataflow references this variable for its data source connection.

In another workspace, the same Dataflow could use:

Variable Library:

SourceConnectionGuid = fedcba98-7654-3210-fedc-ba9876543210

This would make it much easier to use the same Dataflow across personal feature workspaces, test, and production while keeping the appropriate connection for each environment.

Automatically match PowerBI chart background color to Powerpoint slide background color

jim_chan — Wed, 02 Sep 2026 23:51:04 GMT

Export PowerBI to PowerPoint slide - Can we define the PowerBI export background color to automatically match the PowerPoint slide background color ? By Default, the PowerBI background color is White. My corporation uses a non-white background (matching corporate branding). Is it possible to export PowerBI chart that matches the PowerPoint slide background color.

New Card Visual - Alignment of Reference Label Values

nk685f — Wed, 02 Sep 2026 23:08:37 GMT

The latest Power BI Desktop version I'm allowed to use at work currently is Version 2.154.1260.0 (May 2026), so if this request has already been implemented in later versions, please disregard. Otherwise, please add the ability to separately align reference label titles and values, as well as to provide variable space between the reference label titles and values. Thank you.

Show all model view layouts

reiffaul — Wed, 02 Sep 2026 19:05:34 GMT

Allow users connecting to a PowerBI Semantic model via PowerBI Desktop to view all of the custom layouts provided. This will allow self service users to view smaller sections of the model as laid out by the model developers, making the relationships easier to understand.

A bonus option would be to be able to selectively hide layouts to users, similar to report pages.

Support QR codes in the barcode scanner in the Power BI app

Jaap_O_RFH — Wed, 02 Sep 2026 15:01:10 GMT

I was surprised to find that the barcode scanner inside of a Power BI report in the mobile app only supports scanning barcodes, not QR codes. Our warehouse uses QR codes everywhere, so I cannot use this feature.

I understand that QR codes in the powerBI app are used for something else (to go to a report), but it feels like it should be possible to accept QR codes as well when a user taps on the barcode button inside of a report in the app.

Allow enabling Lakehouse Schemas on an existing Lakehouse

AlessioAndriulo — Wed, 02 Sep 2026 14:48:55 GMT

Right now Lakehouse Schemas can only be turned on when you first create a Lakehouse. If you already have one running in production and later decide you need schemas, there is no way to enabled them on it. The only option is to create new Lakehouse with schemas turned on.

It would really help to have a supported way to enable schemas directly on an existing Lakehouse, without having to recreate it from scratch. Either a toggle that converts it in place, or an official migration path that keeps the same Lakehouse identity and just adds schema support, so all the existing references keep working.

Allow enabling Lakehouse Schemas on an existing Lakehouse, without recreating it

AlessioAndriulo — Wed, 02 Sep 2026 14:29:29 GMT

Today, Lakehouse Schemas can only be turned on when a Lakehouse is first created. There is no supported way to enable schema support on a Lakehouse that already exists — the only workaround is creating a brand-new schema-enabled Lakehouse and manually migrating every table into it.

This is a real blocker for teams running Lakehouses already in production. Schema support gates several features that matter for day-to-day engineering — Materialized Lake Views, schema-level access control (row/column security), cross-workspace four-part-name queries, and schema shortcuts. Adopting any of them on an established Lakehouse currently means:

Creating a net-new Lakehouse just to get the schema flag
Re-pointing every downstream notebook, pipeline, dataflow, and Power BI semantic model to the new item
Manually copying every table (losing Delta history unless you deep-clone)
A cutover with no natural rollback

Concrete example: wanting to use Materialized Lake Views on an existing medallion pipeline requires abandoning the current Lakehouse entirely, even though the transformation logic has nothing to do with the migration itself.

Ask: provide a supported, non-disruptive way to enable schemas in place on an existing Lakehouse — either a portal/REST toggle that converts it directly, or an official migration tool that moves the data while preserving the Lakehouse's identity (same ID, same downstream references), instead of forcing a net-new item every time.

Workspace Folder & Subfolder Inventory View for Power BI Reports and Apps

rijesh — Wed, 02 Sep 2026 14:29:05 GMT

Problem:

Many organisations use Power BI workspace folders and nested subfolders to organise reports by department, business area, project, or function. While this structure helps keep content organised, it becomes difficult to quickly identify:

How many reports exist within a workspace

Which folders and subfolders contain reports

Where a specific report is located

Which reports are included in a published App

Which reports are no longer used or duplicated

Currently, users must manually navigate through each folder and subfolder to locate reports. In large workspaces containing dozens or hundreds of reports, this process is time-consuming and inefficient.

Proposed Solution:

Introduce a Workspace Content Explorer or Folder Inventory View that provides a consolidated view of all workspace content, including:

Folder hierarchy and subfolder structure

Report count per folder

Complete list of reports with folder paths

Search and filter capabilities

App publication status

Ability to export the inventory to Excel/CSV

Option to view reports in a tree structure or flat list

Movable Header Icons for Visuals

AaronReasoner — Wed, 02 Sep 2026 14:25:49 GMT

Add ability in Power BI to reposition Visual Header Icons. Locking them to the top right forces unnecessary horizontal scrolling across wide or zoomed in visuals just to access essential controls like drill down or hierarchy level changes which slows down user analysis.

Support JSONL files in the lakehouse preview

Tom_Fosterbi — Wed, 02 Sep 2026 11:30:28 GMT

Currently JSONL files cannot be previewed within a lakehouse, supporting this would improve any workflow with these files

Copy results as markdown from data grid

Tom_Fosterbi — Wed, 02 Sep 2026 08:45:51 GMT

When copying results from a query on the SQL Endpoint or Data Warehouse I often have to convert from the tab delimited table to markdown for sharing the results via services like teams or github.

It would make sharing data much easier if I could just click a "copy results as markdown table" button in addition to the existing options.