There appears to be no method to format column vertical lines; i would love to be able to format the top level of a column hierarchy - to have a alternating colour background on the that level of text, also to have thicker vertical lines It also seems mad that we don't appear to have a method to sort the column order These issues are made worse if you need to switch the measure to rows (which is rather common) ... View more

Hi, Currently Fabric's data copy only support Salesforce's API version 58.0 . Newer API version expose newer objects, which are not accessible to Fabric at the moment.    Salesforce API v 58.0 was released on Summer 23. The latest version released is 65.0 (Winter 26)   ... View more

The docs say:   "There's a semantic model-level setting to automatically update Direct Lake tables. It's enabled by default. It ensures that data changes in OneLake are automatically reflected in the Direct Lake semantic model. You should disable automatic updates when you want to control data changes by framing (...)"   https://learn.microsoft.com/en-us/fabric/fundamentals/direct-lake-overview#automatic-updates   Currently, this disabling needs to be done manually on each semantic model in each workspace.   However, best practice is to not do manual adjustments in Test and Prod workspaces.   Please make it possible to control this behavior via Git instead. This setting could be a part of the definition of the semantic model item.   Please also make it possible to use Deployment Rules or Variable Library to control this behavior in Test and Prod when we're using Fabric Deployment Pipelines. ... View more

We a scenario that we have a dev workspace which is used to build the reports pointing to dev dataset and than using CI/CD we deploy it to many target workspace, after the deployment we rebind all the reports in target workspace with dataset present in that workspace, this will fix the connection between the target report and target dataset, but if i try to download a report using live connection and open it via Power BI desktop, it will still point to old dev workspace, since the rebind will only change some connections in metadata(RemoteArtifact) of a report.   We need an ability to also change this connection(PbiModalDatabaseName). Below is an example of the report metadata {   "Version": 2,   "Connections": [     {       "Name": "EntityDataSource",       "ConnectionString": "*****"       "ConnectionType": "pbiServiceLive",       "PbiServiceModelId": ******,       "PbiModelVirtualServerName": "******",       "PbiModelDatabaseName": "d*******3"     }   ],   "RemoteArtifacts": [     {       "DatasetId": "f*******c",       "ReportId": "1********6"     }   ],   "OriginalWorkspaceObjectId": "9**********7" }   ... View more

Currently you can't move items either to the front or bottom once created. This makes grouping difficult. It is possible to be thinking along such lines where after creating a variable you be in the position to move it either to the top, bottom or to any position you wish to group them nicely?  And Possibly to activate or Deactivate the variable without necessarly deleting it.   ... View more

Currently, Power BI Desktop keeps the report canvas, ribbon, and side panes locked in a single window. For users working with multiple monitors or doing detailed design work, this layout limits flexibility and screen space. Proposed Feature: Enable the report page (canvas) to be detached into its own window, independent of the ribbon and side panes. This would allow: Full‑screen editing on one monitor while keeping fields, visualisations, and filters on another. Easier design for complex dashboards without constant pane toggling. Improved productivity for users who need to present and edit simultaneously. Benefits: Better multi‑monitor experience. Faster layout adjustments and visual alignment. More efficient workspace for advanced modelling and report building. Optional Enhancements: Ability to dock/undock panes (Visualisations, Filters, Fields) as floating windows. Snap windows side‑by‑side for custom layouts. ... View more

Power BI in Microsoft Fabric is an integrated business intelligence and data visualization solution that operates within Microsoft’s unified data and analytics platform. It enables users to connect, model, analyze, and visualize data from OneLake and other Fabric workloads (Data Engineering, Data Factory, Data Warehouse, Real-Time Analytics). Within Microsoft Fabric, Power BI is not a standalone tool—it is deeply integrated with the entire data lifecycle. Users can build semantic models directly on Fabric data sources, create interactive dashboards and reports, and share insights securely across the organization with real-time collaboration and governance. This subject covers Power BI fundamentals, Fabric integration, semantic modeling, DAX basics, performance optimization, and enterprise-level analytics using OneLake. ... View more

I think enabling OneLake availability directly from a follower Eventhouse would be a valuable feature. This idea builds on another proposal I shared earlier that currently appears to be stuck in “Needs clarification.”   In our architecture, we treat the primary Eventhouse strictly as ingestion-only, while the follower Eventhouse is used exclusively for downstream consumption.   Ideally, business users should have access only to the follower Eventhouse, never the primary. However, today when we enable OneLake availability and create a shortcut to a Lakehouse, users must be granted access to the primary Eventhouse in order to see the table. This breaks our intended segregation model and introduces a risk, since business users can now directly query the primary Eventhouse—something we explicitly want to avoid.   While the follower Eventhouse is read-only, it is already the surface area exposed to downstream consumers. Allowing OneLake availability to be enabled from the follower Eventhouse would preserve this separation of concerns and eliminate the need to grant any access to the primary.   This would also empower downstream users to enable OneLake availability and create their own shortcuts, rather than requiring the development team to configure it on the primary Eventhouse and manage narrowly scoped access to individual primary tables. Overall, this change would better support secure, ingestion-vs-consumption–aligned architectures and reduce unnecessary operational overhead. ... View more

It shouldn't take adding in a new query, that will just be deleted, or wiping out the permissions for the current direct query to be able to get to the edit screen.  Just because it's direct query doesn't mean that there aren't things that can be adjusted in the edit screen as limited as those options may be. ... View more

Problem Statement Currently in Power BI, when a Dataflow or other artifacts (e.g., datasets, reports) are deleted, they cannot be restored. This can cause significant issues for customers if the deletion was accidental or triggered during operational activities.   Customers want an option to restore deleted Dataflows or artifacts, with a retention period would help customers quickly recover deleted content, reduce operational impact, and align Power BI with common data‑platform usability standards. ... View more

Conserver le paramètre « Ne pas autoriser l’enregistrement des filtres persistants » après modification dans Power BI Service : Description : Actuellement, lorsque l’on désactive l’option « Ne pas autoriser l’enregistrement des filtres utilisateurs » dans Power BI Service, ce paramètre se réinitialise dès qu’on modifie et enregistre le rapport dans le Service. Cela oblige à le décocher manuellement à chaque modification, ce qui est chronophage et source d’erreurs. Proposition : Permettre de verrouiller ce paramètre de manière permanente au niveau du rapport, même après des modifications dans Power BI Service, afin de garantir la cohérence et éviter les oublis. Bénéfices : Gain de temps pour les créateurs de rapports Réduction des erreurs et meilleure expérience utilisateur Alignement avec les besoins des organisations qui souhaitent un état par défaut constant ... View more

In this example, I'm using an Azure DevOps - Source Control connection configured with Service Principal authentication as shown on the image below      Using this connection, I'm invoking a interface Git - Connect - REST API (Core) | Microsoft Learn , following the example provided in Connect a workspace to Azure DevOps using configured connection example  and implemented using PowerShell script, in the image below you can see how the call is correct, but I'm getting an error "{"requestId":"xxxxxxxx-xxxx-xxxx-xxxxxxxxxx","errorCode":"GitProviderResourceNotFound","message":"The requested operation can't be completed because the Git provider resource could not be found using the provided Git connection details."}"        After a LONG INVESTIGATION following what the error suggested the problem was (e.g. ID of the connection incorrect, lack of permissions, etc)  and ruling-out many alternatives, I concluded that it wasn't none of this but the issue was that, on the target branch reference in the example shown "workspace/ws_test-auto-deploy_dev" did not contain "directoryName": "/fabric"    This is why the return error message GitProviderResourceNotFound is very misleading and should be more granular, it would have same me a lot of time something different like "BranchMissingDirectory" instead.  ... View more

I would like to suggest adding built-in usage analytics for OneLake, such as storage growth trends, dataset access frequency, and cost-impact insights. This would help data engineers and admins better manage storage, optimize performance, and control costs across workspaces. ... View more

Feature request: OneLake shortcuts to support connections to ADLS Gen2 storage accounts using managed private endpoints   Currently OneLake shortcuts only support connections to storage accounts that are publicly accessible or accessible with storage networking rules in place. Shortcuts via Managed Private endpoints are not supported yet. Our organization requires all connections to go via Private Endpoints. Furthermore, networking rules are not possible in our situation, since our Fabric instance is deployed in a different Azure Tenant.   OneLake shortcuts are a great way to save compute, as we would be able to query directly on our Delta and Parquet tables in our Storage Accounts, instead of requiring compute to serve this data. Once OneLake Shortcuts via Private Endpoints are supported, I am also hoping that Databricks mirrored catalog would be working via the Managed Private Endpoint connections.   Therefore my feature request is OneLake shortcuts to support connections to ADLS Gen2 storage accounts using managed private endpoints. ... View more

I successfully separate Selection State(Selected) from Selection State(Unselected) with transparency option. However, If the user does not make any selection(means selects all) the display of the button is same as Selection State(Unselected). It must be same as Selection State(Selected). Technically, none selected means All selected(same as any selection) ... View more

Hi, to order an array into a pipeline it could be very useful to have an appropriate feature, e.g. a sort activity or a sort regex function, without using any notebook codes. F.e. an array could contain the name of files read by a get metadata activity against an on-premise folder and before copying the related files into a lakehouse it could necessary to order this array to perform a right copy following a temporal order. Thanks ... View more

Here's the link to the post - from which this originated. Currently, Microsoft Fabric does not expose source or connection metadata for Azure Databricks (Unity Catalog) mirrored items through any public REST API. Although these artifacts appear in /v1/workspaces/{workspaceId}/items as MirroredAzureDatabricksCatalog, they are modeled as a different artifact type than database mirrors and therefore do not appear in /mirroredDatabases. The getDefinition endpoint also does not return any definition parts for this item type, even after the long running operation completes successfully.   Proposal - fro effective Governance provide an api through which we atleast can read metdata information like catalog name. This can be very helpful for the admins. ... View more

Hello Power BI Team, I’m writing this as a long-time Power BI user who builds operational dashboards daily—not demos, not samples, not screenshots, but dashboards that people actually work in for hours. Over the last few updates, several basic but extremely practical formatting options have been quietly removed or hidden, particularly in the Table and Matrix visuals. The most painful example is the removal of alternating row backgrounds in Tables, which was a simple, effective readability feature used widely in real-world reporting. What’s frustrating is not just the limitation itself, but the direction it reflects: Useful controls removed without clear alternatives “Style presets” that look fine in marketing examples but perform poorly in dense, real dashboards More time spent fighting the tool than focusing on insights Presets are not a substitute for control. Most serious Power BI users I know turn them off immediately and manually format visuals anyway—because clarity, contrast, and readability matter far more than opinionated color choices. I’m sharing this feedback because Power BI is otherwise a very capable platform, and regressions like this genuinely reduce productivity for experienced users. Please consider reintroducing: Alternating row formatting for Tables Clear, granular control over visual styling Fewer opinionated defaults, more user choice This feedback comes from someone who wants the product to be better—not from a place of resistance to change, but from daily hands-on use. ... View more

Dear Microsoft Support / Power BI Development Team, I am writing to report a persistent limitation regarding the use of Python scripts as a data source in Power BI Service, specifically for web scraping tasks. Currently, when publishing a report that uses Python scripts, the service returns the following error during scheduled refresh: Extension{"extensionDataSourceKind":"Python","extensionDataSourcePath":"Python"}. The only known workaround is using the On-premises Data Gateway (Personal Mode). However, this is not a viable solution for enterprise-level environments for the following reasons: Dependency on local hardware: It requires a specific user's computer to be powered on and connected. Scalability: It lacks the robustness and centralized management of the Standard (Enterprise) Gateway. Security and Maintenance: Maintaining individual Python environments on local machines is inefficient. As of 2025, Python has become a fundamental tool for data engineering and scraping. I kindly request that Microsoft considers: Enabling Python execution support within the Standard (Enterprise) Gateway. Providing a native cloud environment for Python script execution within the Power BI Service/Fabric capacity. Improving this integration would significantly enhance the flexibility and reliability of the Power BI platform. I look forward to hearing about any planned updates regarding this feature. ... View more