Currently, OneLake Security Roles must be configured individually within each Lakehouse. For organizations managing multiple Lakehouses based on data domains, this results in significant manual effort and duplication. Additionally, maintaining both Active Directory (AD) groups and separate OneLake Security Roles adds complexity and increases the risk of misalignment. ... 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

Currently, Azure Key Vault references in Microsoft Fabric support only OAuth2.0 authentication. It should support other authentication methods like  identity, service principal. ... View more

For years, we have been requesting a new line item be added to the Related Content listing called “Next Refresh.” The current listing already displays “Last Refresh,” and adding “Next Refresh” would greatly improve how we use and monitor our Power BI reports. See the screenshot below.   Thanks,     ... View more

Currently, Microsoft Fabric does not provide an option to copy an existing semantic model. This limitation makes it difficult for developers to reuse or customize models without impacting the original. With Direct Lake models becoming common, organizations often maintain large, centralized semantic models that serve multiple teams. Developers frequently need to: Experiment with new measures or calculations Create tenant-specific variations Build prototypes without risking changes to the shared model Proposed Enhancement: Add a “Copy Semantic Model” capability that: Allows users to duplicate an existing semantic model into their own workspace. Preserves relationships, measures, and metadata. Does not require edit access to the original model, ensuring governance and security. Benefits: Improves developer productivity and flexibility. Reduces risk of accidental changes to shared models. Supports scalable development for multi-team environments. ... View more

I would like to request the addition of a Kintone connector for Power BI. Kintone Official Website (US) Kintone Official Website (Japan)   By enabling seamless integration, we expect to unlock greator value from both platforms - leveraging Kintone's data capabilities and Power BI's powerful analytics and visualization features. In response to customer requests, we developed and provided a custom connector for Kintone. https://cybozu.dev/ja/id/90125c111898e77ad9a26618/ (Japanese only) ... View more

Introducing branching in the deployment pipeline allows releases from acceptance to multiple production regions (APAC, EMEA, NORA) instead of strictly sequentially. This prevents one blocked deployment from halting all others. Faster, independent regional releases With branches per production region (or parallel deployment stages), each region can be released independently from the same acceptance-approved artifact. APAC, EMEA and NORA can be deployed at the same time or in a chosen order, without having to wait for the previous region’s deployment to complete or recover. Reduced blast radius and better resilience If a deployment to one region fails or is paused (e.g. APAC), the other regional branches/stages (EMEA, NORA) can still continue to release. This avoids the current situation where a single failing deployment blocks the entire global rollout, improving overall reliability and keeping unaffected regions up to date. Clearer control and governance Branches or parallel stages per region make it explicit which version is running where, while still promoting from the same acceptance baseline. Change approvals and rollback decisions can be made per region, supporting time‑zone specific windows and local compliance needs, without duplicating pipelines or diverging code. ... View more

Due to the way that Power BI functions, I'm not sure if that's possible, but I'll shoot my shot. I'd like to hide and unhide visuals based on what's selected in a slicer, and I'd like to configure that with a measure. Basically, if 'x' it's selected then 1, if 'y' then 0 etc., and use that to hide/unhide a viz. There are workarounds, but in my opinion are quite limited and not ideal, for example using bookmarks or overlapping two vizuals and use conditional formatting on the colours. ... View more

Smoothing currently balances the CUs required to complete background tasks across 24 hours.  This often means that overnight we are under-utilising our capacity and offsetting some of the load to our peak usage period during the day.  Since the peak period also includes many interactive processes, smoothing is actually creating usage peaks right when we are using the processes which are most impacted by those peaks.   We should be able to control smoothing by setting a percentage of capacity that can be utilised by background processes.  If background usage is below this figure the spare capacity should then be used to speed up background processing.   Example:  Consider a 6 CUhr background operation starting at midnight.  Currently, it would consume 0.25 CUhr per hour for 24 hours.  Running an F2 Sku, I set my Background Processing Limit to 50% between 00.00 and 06.00.  Now the operation consumes 1 CUhr per hour for 6 hours and no consumption for the remaining 18 hours. ... View more

We need support for Service Principal authentication when creating Lakehouse connections.   Right now, Lakehouse connections can only be created using a user account. As a result, Dataflow Gen2, Pipeline copy activity, and Copy Job cannot use a Service Principal (SPN) when connecting to a Fabric Lakehouse as a source or destination.   This is an issue for us. We want to avoid user-based connections because: We need environment-specific identities (dev/test/prod) to prevent accidental cross-environment writes (e.g., dev pushing data to prod). Tying connections to personal user accounts creates fragility - things break when someone leaves the project or the organization. Service Principal support for Lakehouse connections is required to ensure secure, reliable, and environment-isolated authentication.   The screenshot shows that only user authentication is available, not service principal authentication. ... View more

Introduce an “Export Visual Data as Rendered” option that guarantees the exported dataset matches the visual exactly, including all applied filters, measures, and formatting. ... View more

Enable conditional formatting on row headers and column headers in Matrix and Table visuals. This would allow users to visually highlight headers based on rules (e.g., values, measures, or hierarchy levels), just like we currently do with data cells. ... View more

I would like if the Power BI Monitor Tab allowed users to create multiple custom filtered views and save them so that we can toggle back and forth or clear the filters without having to recreate them the next time. I am an admin for 18 workspaces (not all production), and need to check different combinations, and statuses (sometimes I want to see only the failures, other times I want to see what is in progres, etc), or I might want different combinations of columns visible/hidden. This tab is severerely under-utilized by me because of this.  ... View more

Want a metrics to show the consumption of artifacts when refreshed using Gateway. It should be shown in terms of how much of memroy is artifacts consuming for gateway not in cloud. ... View more

Metadata refresh failure in the Lakehouse SQL catalog due to Error "exceeding the database request limit". This resulted in SQL query failures linked to the DataflowsStagingLakehouse SQL Endpoint, which is not visible in the Fabric UI.     Customer is looking for Lakehouse SQL Endpoint to be visible in Power BI service UI.        ... View more

When adding columns to a Matrix I always want the headings to align above the numbers ( i.e. to the right ).    This should be the default in my view Per bottom visual of screenshot   ... 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

Improve image quality in the snapshot option. Currently, when switching from live preview mode to snapshot mode, the image quality deteriorates significantly. At the moment, the public snapshot does not look very professional, which makes it difficult to recommend or use in presentations. ... View more

Hi there,   as a developer I want to have the option in the GraphQL item to choose if changes in the underlying tables are populated automatically or need manual update.  Automatic helps to bring more reliablility and automation in the whole lifecycle.  Manual options lets the user only populate validated changes to the API.  Currently as of 24.11.2025 the GraphQL API item does NOT automatically populate schema changes of underlying tables to the item. The tables needs to be reloaded either by "reload schema" or even deletion and new selection of tables.  Thanks and best regards! ... View more