Paginated Reports with PowerQuery - Cloud connections for Snowflake connector
Current situation: Power BI report builder used to build a report using Power Query dataset. Report builder picked the right cloud snowflake DB connection (created in Power BI service portal - app.powerbi.com) However, once we deployed / published the report into power bi service portal (workspace), we are not able to see the connection it uses in the background. We only see the disabled connection settings. Refer the screenshot. It would be great if we display the cloud connection information just like how we display for semantic models. Otherwise, we have to download the rdl file from the portal and check the connection ID from the report file and fetch the connection detail from the "Manage Connections and Gateways" page from the portal settings.
Fabric Apps
Currently, Microsoft Fabric App is not available in several regions, and this limitation is significantly impacting our ability to move forward with key initiatives. We have an urgent business requirement to have Fabric App support enabled in the UK regions, as it would allow us to leverage its capabilities and accelerate the development of several high-value features and solutions. Enabling Fabric App availability in the UK regions would greatly benefit. What is Fabric Apps (Preview)? - Microsoft Fabric | Microsoft Learn
New Monitoring Hub
Enjoying the new monitoring hub and the insights it brings. However, I have a few suggestions Display Start Time and Current Duration When clicking on Workspace, take me to the Workspace - like the Legacy Hub Remove the Pagination, we have a very busy capacity that we need to monitor Alerts for any running job that exceeds a time threshold, eg send email to admins where any refresh is taking longer than 60 minutes
More Granular Workspace Permissions (RBAC)
Allow Workspace Admins to assign more granular permissions and create custom roles based on atomic permissions, following the principle of least privilege. Examples of possible atomic permissions: Read workspace settings Manage workspace settings Read workspace role assignments Manage workspace role assignments Read OneLake security access role assignments Read workspace activity logs Read data Write data Share read data permissions Share write data permissions Create and edit workspace items Delete workspace items Share create and edit workspace items Share delete workspace items etc. This would enable Workspace Admins to automate auditing and governance, delegate specific responsibilities, and follow least-privilege principles without granting unnecessarily broad workspace roles.
Rule to force only HC Sessions while working with interactive notebooks
As a Fabric Platform Admin, I would like to force users of specific workspaces to only be allowed to spin-up and use High Concurrency (HQ) Sessions while working interactively with notebooks. This can help with best capacity utilization and faster notebook startups.Enable Direct Addition of Fabric Data Agents to Microsoft 365 Copilot
Please enable users to add and invoke a Fabric Data Agent directly as a specialized agent in a Microsoft 365 Copilot multi-agent solution. In our current setup, we can’t add a Fabric Data Agent directly to M365 Copilot, so we connect to it through Fabric IQ Data MCP. This approach raises a concern that we need to separately verify whether requests are routed to and handled by the intended Fabric Data Agent. That additional validation makes configuring and testing the multi-agent solution more complex. We request the ability to select and add a Fabric Data Agent directly as a subagent in the M365 Copilot multi-agent configuration, allowing the parent agent to delegate tasks to it directly. This would reduce the additional validation required for the intermediate MCP connection and make the multi-agent setup simpler and more transparent. This request is not a report of a defect in Fabric IQ Data MCP; it is a request for direct Fabric Data Agent integration in M365 Copilot. We also request that the Fabric Data Agent’s existing authentication, data-access permissions, and security policies continue to be enforced when using this direct integration. References: Consume a data agent in Microsoft Copilot Studio (preview) Consume a Fabric data agent as a tool in Microsoft Copilot Studio
Disable App Sharing Notification to Audience
Can we have the option to turn off the notification when we add people to an audience in Power BI Apps? Sometimes, I want to share an app with a wider group of people, but I don't want to notify all of them. I just want to make sure they can access the app when they need to. We've been trying to get viewers in our organization out of workspaces, but we've been having to give viewer access to workspaces as a workaround when we are sharing with a large group.User Interface customization - HomePage & Help and support
Hi, 1st idea: It would be great if administrators could customize the Fabric/Power BI Home page. Today, users can choose between three predefined layouts (Copilot, Simplified, and Expanded). Allowing administrators to create and publish a custom layout for all users, with embedded report pages, visuals, quick-access buttons, and other tailored content, could significantly improve the user experience and adoption of the platform. 2nd idea: It would be great if administrators could customize the Help & Support menu by adding their own entries, renaming existing ones, and changing their order. This would make it easier to promote organization-specific documentation, support contacts, training resources, and other important links directly within the Fabric/Power BI experience.
Managing Purview Access in a OneLake Security-Enabled Fabric Environment
As OneLake Security is now enabled by default for supported Lakehouse items, Purview scanning appears to work differently for Lakehouses created before and after this change. We are therefore looking for a centralized solution for managing Purview access across Fabric Lakehouses. Assigning the Contributor role to the Purview Service Principal, as recommended, is unfortunately not an option for us due to our security and governance requirements. We are looking for a solution that follows the principle of least privilege while minimizing operational overhead. Ideally, Purview should be able to access all relevant Lakehouses without requiring manual role assignments for each existing and newly created Lakehouse. Could the Product Group please advise whether a centralized approach is planned, for example: A tenant- or Fabric-level Default Reader, that can be assigned once and automatically applies to all Lakehouses. Automatic inheritance of OneLake Security permissions for new Lakehouses; Or another centrally managed mechanism that avoids per-Lakehouse configuration while maintaining read-only access? Disable OneLake Security for specific Fabric
