H ere is some confusion regarding the IDs displayed for Fabric Identities. Only the Object_ID is available in Fabric (whereas the name displayed is Service Principal ID). This column should be renamed and the Service Principal ID made accessible in Fabric. Here is the link providing more details : https://community.fabric.microsoft.com/t5/Fabric-platform/Fabric-identities-Confusion-between-Object-ID-and-Service/td-p/4919194 ... View more

It would be incredibly helpful if Power BI allowed users to share a specific filtered view of a report. Right now, I can open a report, adjust the filters to create the exact view someone needs, and save it as a personal bookmark—but that bookmark is only visible to me. I’d love the ability to save that filtered state as a shareable bookmark and send it to another user without having to engage power BI developers to save the bookmark state as a "global" selection. This would make collaboration faster and eliminate the back‑and‑forth of “which filters did you use?” ... View more

In Power BI Apps, section headers are organizational only, they can’t serve as a clickable destination. To create a “hub” page and still group child items, authors must duplicate the name: once as a section and again as a page/link inside that section. This leads to redundant labels, extra maintenance, and user confusion. Current navigation lets authors add sections, links, and (optionally) one overview page, and the first navigation item becomes the app’s landing experience, but there is no way to make a section header itself open content. ... View more

Current Pain Point Currently, when using Variable Libraries in Fabric pipelines, each variable must be manually added one-by-one to a pipeline before it can be referenced. This creates significant friction, especially when: Working with libraries containing dozens of variables Adding new variables to an existing library (requires updating every pipeline that needs them) Managing multiple environments with different configurations Proposed Solution Allow dynamic access to Variable Library variables without pre-registering them in each pipeline. Two implementation options: Option A: Link Entire Variable Library Add capability to link a full Variable Library to a pipeline All variables in that library become immediately accessible Option B: Dynamic Expression Function @GetVariable('VariableLibraryName', 'VariableName') Reference any variable from any Variable Library in the workspace dynamically No pre-registration required Enables truly parameterized, reusable pipelines Benefits Benefit Impact Maintainability Add variables once to the library, use everywhere instantly Reduced Errors No more forgetting to add variables to pipelines DRY Principle Single source of truth for configuration values CI/CD Friendly Easier to manage environment-specific configs across deployments Developer Experience Faster pipeline development, less repetitive clicking Use Case Example Imagine a data platform with 50+ pipelines all needing access to common configuration values (connection strings, retention days, environment flags). Today, adding one new variable means manually updating all 50 pipelines. With dynamic access, you update the library once and you're done. ... 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

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

Microsoft Fabric currently provides lineage at the item level (datasets, lakehouses, notebooks, pipelines), but does not expose column-level lineage within Fabric itself. For teams building transformations using: Fabric Lakehouse (Delta tables) SQL Analytics Endpoints Dataflows Gen2 Pipelines / Notebooks there is no way to see how individual columns flow, transform, or propagate between sources and downstream tables/views inside Fabric. Ask: Provide a column-level lineage view directly in Microsoft Fabric, showing: Source column -> target column mappings Transformation paths across notebooks, pipelines, SQL, and dataflows Cross-artifact lineage (Lakehouse -> SQL Endpoint -> Dataset, etc.) Limits: Fabric lineage graph only shows artifact-level relationships No visibility into column-level dependencies Purview does not currently provide complete or end-to-end column-level lineage for Fabric workloads. ... 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

Please introduce more granular permission controls that allow admins to determine which user groups can create specific Fabric artifacts. The current all-or-nothing model—where users can either create all artifacts or none—does not align with least‑privilege security principles used across the industry. Detail: At the moment, Fabric supports allowing any user to create all artifact types or restricting creation to an AAD group. While helpful, modern enterprise environments require more precise governance. Different teams operate with different responsibilities, and unrestricted artifact creation increases risk, introduces operational overhead, and can lead to unintended platform misuse. For example: Data Engineering teams should be able to create Data Factory pipelines, Dataflows, Lakehouses, and Notebooks Machine Learning teams may require access to Notebooks but should not necessarily create Pipelines or Dataflows Business teams may need access only to Semantic Models or Dashboards Platform teams must be able to enforce governance while keeping Fabric aligned with enterprise architectures Implementing a least‑privilege, role-based model is standard practice across cloud services (Azure, AWS, GCP) and is critical for organizations with compliance and security requirements. Request: Please enable admins to grant permissions per artifact type (ADF, Notebooks, Lakehouses, Pipelines, ML Models, etc.) to specific security groups. This would allow organizations to: Strengthen security and compliance Reduce accidental resource sprawl Ensure proper architecture and governance Empower teams with the exact tools they need—no more, no less Align Fabric with industry-standard RBAC and least‑privilege models This enhancement would bring Fabric closer to enterprise-grade governance expectations and unlock broader adoption. ... View more

Due to some external restrictions we had to configure the main PROD workspace the way that permissions are granted on report-level and not on workspace-level. Since there is no workspace-level visibility assigned this workspace is not visible in the list of Workspaces and can be reached only via OneLake Menu-> Search. It cannot be bookmarked neither. It creates a lot of confusion among users.   Proposal: Workspace is visible in the list of Workspaces if at least 1 report from this workspace is visible for the user.     ... View more

When datasets are created in BigQuery using the BigQuery API without explicitly specifying a location, the API defaults to the US multi‑region. This default behavior causes issues for users need a way to change the default setting ... View more

It would be beneficial if we could connect to the data sources directly from Excel Web. Although this might require the implementation of an on-premises data gateway. By enabling this connection, we can streamline the data work flows and ensure more efficient access to the necessary information. This change could enhance the productivity and allow users to leverage real-time data insights seamlessly. ... 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

The source control panel within a lakehouse lists all notebooks that are new or updated and its not easy to tell at a glance which one(s) you are looking for.  The only fields available are the Item name and Status, and the full name is not visible without hovering over each when there are several similarly named items.     They do not appear to be listed in any kind of date or name sequence, and it is not possible to widen the panel or scroll horizontally to see the full notebook name. Ideally it would be possible to make this panel configurable in size (full window width would be great), and provide extra meta data columns such as the timestamp and user for the last edit, the parent folder, and allow searching/filtering/sorting on these additional columns.  This would make it easy to find and process items when there are many outstanding changes. ... View more

Dear Microsoft Team, We are currently transitioning from Power BI Report Server (PBIRS) to Power BI Service to support hybrid reporting scenarios that combine on-premises and cloud data sources. While the Service offers great capabilities for composite models and cloud integration, we have encountered a major limitation regarding subscriptions for paginated reports (RDL). In PBIRS, we rely heavily on advanced SSRS-style subscription features such as: File share delivery Flexible scheduling Custom delivery extensions However, in Power BI Service, subscription options for RDL reports are restricted to basic email delivery or require Power Automate. This creates significant challenges for our end users, who are not familiar with Power Automate and expect a simple, native experience similar to PBIRS. Our Request Please consider: Adding full SSRS-style subscription capabilities for paginated reports in Power BI Service, including file share delivery and advanced scheduling. Providing a native solution that does not require Power Automate or Semantic model use (since we don't use it for RDL 80% of the time) for advanced subscriptions, to ensure ease of use for non-technical end users. In moder times analysts use combined solutions for datasorces on-prem+cloud often but with your PBIRS you are limiting there Power Bi and at the same time limiting PBI Srvice as well for RDL dynamic subccriptions.  Why This Matters We have many reports that combine on-prem and cloud data, making Power BI Service essential for hybrid scenarios. Limiting subscription options creates a major adoption barrier for enterprise customers transitioning from PBIRS. Our end users need a seamless experience without additional complexity or reliance on external tools. We believe enhancing subscription functionality in the Service will significantly improve enterprise adoption and align with the flexibility currently offered in PBIRS. Thank you for considering this request. Please let us know if there are any plans or timelines for improving subscription capabilities in Power BI Service.   Thank you!  Best, Maria Suncheleeva  ... View more

Fabric currently supports custom Environments for PySpark notebooks, but Python notebooks (preview) cannot use them. In Python notebooks, the only available kernels are Python 3.10 and 3.11, and the only way to install packages is via %pip install, which is session‑scoped, not reproducible, and not aligned with Fabric’s managed environment model. This creates a major gap for teams who want consistent dependency management across both PySpark and Python workflows. Request Please add support for: Custom Python environments (similar to virtual environments) Attaching those environments to Python notebooks Managing Python‑only dependencies through the Environment UI This would bring Python notebooks to parity with PySpark notebooks and enable reliable, repeatable development without %pip workarounds. Example In PySpark notebooks with an Environment, this works: python from faker import Fakerfake = Faker()fake.name() In Python notebooks, it only works after:   %pip install faker …and must be reinstalled every session. Enabling custom environments for Python notebooks would solve this cleanly and improve the overall Fabric development experience.   ... View more

Hi, I think that it could more useful to have a Set multi variables activity for pipelines in order to use only one activity to set multiple variables without implementing more Set variable activity in the same pipeline. Less development effort, more readability. Thanks   Work better to work less. ... View more

It's great to now be able to set a tooltip on a card, but in the new multicard I need to be able to set a tooltip on each card in the multicard. Can I fix this without making single multicards. ... View more