Tenant-Wide OneLake Shortcut Lineage and Impact Analysis
This is grounded in a documented limitation: shortcut lineage is currently workspace-scoped, and Microsoft specifically says lineage for shortcuts to warehouses and semantic models isn't currently available. There are also community discussions describing the inability to trace table-level dependencies across workspaces.
Display Delta table and column descriptions in Fabric Lakehouse Explorer/ Fabric on Browser
Microsoft Fabric Lakehouse should provide a visible and editable description field for Delta tables and columns in Lakehouse Explorer. Delta table metadata, such as comments or custom description properties, can be stored through Spark, but this information is not clearly displayed to users browsing the Lakehouse. Please add support for: Displaying table descriptions in Lakehouse Explorer/ Fabric on Browser Displaying descriptions as tooltips or in a table details panel Displaying column descriptions in table previews and schema views Editing table and column descriptions directly from the Fabric interface Reading existing Delta comments and description properties Exposing descriptions consistently through the Lakehouse SQL analytics endpoint Making descriptions available to Microsoft Purview and Copilot This would improve data discovery, self-service analytics, governance, and semantic understanding without requiring users to maintain separate documentation. Data engineers can identify tables from technical names, but report developers, analysts, and business users need descriptions to understand their intended purpose. Keeping descriptions directly with the Lakehouse object reduces separate documentation, ambiguity, and incorrect table usage.
Allow report creators to download their Own PBIX even when Downloads are restricted at tenant level.
In the current Power BI permission model, PBIX downloads are controlled exclusively through tenant‑level export settings and workspace roles. This creates a significant limitation for multi‑agency or large enterprise environments: enabling PBIX downloads grants broad download access to any user with Contributor permissions in any workspace, regardless of whether that user originally authored the report. What’s missing: Power BI has no concept of “author-level” permissions for published reports. Although the service identifies report contacts and retains semantic model owners for refresh purposes, these fields are not tied to download rights. As a result, report creators cannot download their own PBIX files unless they are manually added to security groups or privileged roles — even when they are the sole developer and publisher of that content. Why this matters: Organizations with strict governance requirements need a middle-ground option that allows report creators to retrieve their own work without exposing underlying datasets broadly across their tenant. Today, the only choices are: Turn PBIX downloading off entirely, or Turn it on for specific security groups (which often include far more users than just the report authors). This limits flexibility, complicates content lifecycle management, and increases administrative overhead. Requested enhancement: Introduce an “owner-only PBIX download” permission that allows the original report creator (or designated report contact/semantic model owner) to download the PBIX file even when global download settings remain restricted. This would enable organizations to give creators access to their own work without expanding download rights for all Contributors. Benefits: Restores creator-level autonomy without compromising data security Reduces administrative overhead for tenants with many workspaces or agencies Provides the exact middle-ground scenario many customers need Aligns Power BI’s ownership model with user expectations in other Microsoft tools Optional implementation ideas: A per‑report toggle: “Allow report creator to download PBIX” A workspace setting: “Creators may download PBIX regardless of tenant-level restrictions” Linking download rights to the report contact field or semantic model owner
Workspace Sharing
In the past Power BI Admins had the ability to share a workspace as a whole with an external user to then initiate the invite email. After accessing their external account on our tenant, they could then access any residing report based on RLS security set on the external account. This functionality is no longer available for new Power BI workspaces, and can only be done on individual reports within the workspace. This is time consuming when RLS security is in place and protects against unwanted data access based on the report the external user is viewing. The ability to invite external users to newly created workspaces should be brought back to then help minimize the time spent having to invite external users to individual reports when RLS security is set and manages data viewing access.
Enhance Power BI/Fabric Audit Logs with Detailed Action Tracking and Change History
Power BI and Microsoft Fabric audit logs are essential for governance, compliance, security monitoring, and operational auditing. However, several important activities are currently logged with very limited detail, making it difficult to accurately assess user actions and configuration changes. 1. Copilot Audit Logs Today, interactions with Power BI Copilot are typically recorded under the generic RequestCopilot event. As a result, administrators cannot distinguish users who simply submitted prompts from those who performed actions on the generated results. For example, it is currently not possible to identify: Users who only viewed Copilot responses. Users who executed Copy Table. Users who copied generated content. Users who exported or downloaded results generated by Copilot. From a governance, compliance, and data protection perspective, these actions have very different risk profiles and should be tracked separately. Requested enhancement: Introduce dedicated audit events and/or action details for activities such as: CopyTable CopyResponse ExportResults DownloadGeneratedContent Other user actions performed against Copilot-generated outputs 2. Update App Audit Logs The current UpdateApp audit event also lacks sufficient detail for auditing purposes. When an app is updated, administrators cannot easily determine: Which reports were added or removed. Which audiences were modified. Which users or groups were impacted. Which permissions changed. What specific configuration changes were applied. This makes troubleshooting, change management, audit investigations, and compliance reviews significantly more difficult. Requested enhancement: Provide a detailed change log (delta) within the UpdateApp event, including: Added content Removed content Audience changes Permission changes User/group assignments added or removed Before/after configuration details Business Value More detailed audit logs would significantly improve: Security monitoring Data governance Regulatory compliance Internal and external audits Incident investigations Change management Risk management As organizations continue adopting Copilot and Fabric at enterprise scale, audit logs must evolve from activity indicators into true operational and security records that provide full traceability of user actions and configuration changes.Fabric Plan
Session Billing Control Currently, Planner sessions continue to be billed for the full 730-hour (30-day) duration even if the associated Plan item is deleted. Could we consider providing an option for admins to terminate active sessions early, or automatically end the session when the planning artifact is permanently deleted? This would help avoid unnecessary capacity consumption in test or evaluation scenarios. Tenant-Level Governance Setting Could we introduce a dedicated tenant setting to control Fabric Plan creation (similar to other Fabric experiences)? This would allow administrators to disable Fabric Plan for the entire organization or selected user groups when the feature is not required, helping prevent unintended adoption and associated costs.
Dashboard to see the Copilot Usage in Power BI
I would like to propose the development of a centralized dashboard within Microsoft Fabric that provides a comprehensive view of Microsoft Copilot usage across all users within a tenant. Currently, organizations often need to gather usage insights from multiple locations and reports, which can make monitoring adoption, engagement, and utilization more complex and time-consuming. A unified dashboard would simplify this process by consolidating all relevant Copilot usage metrics into a single, easy-to-navigate interface. Key Benefits: Centralized visibility of Copilot adoption and usage across the tenant. Improved user experience by eliminating the need to navigate multiple reporting sources. Easier tracking of user engagement and licensing utilization. Better support for customer discussions regarding Copilot value, adoption, and ROI. Consistent and aligned reporting for administrators, support teams, and stakeholders. Such a dashboard would help organizations quickly understand how Copilot is being used across their environment while providing a more efficient and streamlined reporting experience.
Enable Data Buy & Sell Across - Fabric, Non-Fabric, Tenants and Regions
Requested Enhancement: Enable Microsoft Fabric Marketplace capabilities that allow organizations to seamlessly buy, share, and sell data products across: - Fabric and non-Fabric environments - Different Microsoft Entra tenants (cross-tenant) - Different Azure regions (cross-region) The experience should provide a unified marketplace where organizations can discover, purchase, subscribe to, and consume data products regardless of whether the provider or consumer is using Fabric. Similarly, organizations should be able to publish and monetize data products for both Fabric and non-Fabric consumers without requiring complex data-sharing, integration, or onboarding processes. Key Requirements: - Support data product buying and selling between Fabric and non-Fabric platforms. - Enable seamless cross-tenant data commerce and sharing. - Enable cross-region data discovery, subscription, and consumption. - Provide a consistent marketplace experience for data providers and consumers. - Simplify onboarding, governance, billing, and access management for marketplace transactions. Business Value: - Creates a global data marketplace that extends beyond the Fabric ecosystem. - Unlocks new revenue opportunities by allowing organizations to monetize data assets across tenants, regions, and platforms. - Simplifies secure data sharing and collaboration between business partners, customers, and suppliers. - Reduces friction associated with cross-region and cross-tenant data exchange. - Positions Microsoft Fabric as a central hub for enterprise data commerce, enabling seamless buy-and-sell experiences across the broader data ecosystem.Improve Connection Discovery and Reuse Across Fabric Experiences
Description: Enhance the Fabric UI experience by displaying all available and accessible connections in a consistent drop-down list across Dataflow Gen2, Notebooks, and other Fabric workloads. This would allow users to easily discover and reuse existing connections instead of recreating them, resulting in a more intuitive and streamlined onboarding experience. Requested Enhancement: Enable Dataflow Gen2 and Notebooks to discover and reuse existing Fabric-managed Snowflake connections that a user owns or has permission to use, similar to the connection reuse experience available in other Fabric workloads. Current Challenges: Dataflow Gen2 - Existing Snowflake connections can only be reused when both the Snowflake server name and warehouse are entered exactly as defined in the connection. - This dependency is not intuitive and prevents users from easily discovering and selecting reusable connections. Notebooks - Snowflake connections are only available if the "Allow code-first artifacts such as Notebooks to access this connection" option was enabled during connection creation. - This setting cannot be modified for existing connections, requiring users to recreate connections solely to enable Notebook access. Benefits: Simplifies connection management and improves user experience. Reduces duplicate connection creation and accelerates onboarding to Fabric.
Power BI Subscriptions enhancements sorely needed
I believe there are several updates needed to Power BI subscriptions: Gate subscription ability. Right now, this is all-on/all-off feature. I would like this feature to be gated for users/security groups like almost every other setting in MS Fabric (e.g. allow only certain users/groups to create subscriptions). Zero visibility. Need to see subscriptions on monitor tab Need to know impact on CUs from these subscriptions Need to know everyone reports were sent to (E.g. if we have one subscription is sent to 5 people, we would need 5 records) Need to know when upcoming subscriptions are going to be run Purview labels are not respected in subscriptions. If someone sets up a label for the data in a report, the subscription does not ensure that the user(s) on the subscription are allowed to actually see that data; and since we have not gating by security group (see first bullet), they cannot be controlled that way either No dynamic data for "standard" subscriptions. It would be great to have the ability to have dynamic data input into the email subject or body. Right now the only option is static text. No CC or BCC settings. It would be great to have CC and BCC options. All emails get sent from PowerBI service. It would be great if we could use another SMTP server (set at tenant and/or workspace level) All emails get sent with the same template. It would be great if we could use a custom template (set at tenant and/or workspace level) Fabric semanitc model w/ all Fabric users/groups. There should be a native Fabric semantic model that contains all of the objects (workspaces, reports, users, groups, etc...) that could be leveraged by all who select "Dynamic subscription". I have put these in my priority order DataZoeDataZoeMS
