Auto-propagate Lakehouse (Direct Lake) permissions to users assigned to a Power BI App audience
Problem When a Power BI report uses a Live Connection to a Direct Lake Semantic Model, end users must have explicit ReadAll / ReadData permissions on the underlying Lakehouse (or its SQL analytics endpoint) — because Direct Lake reads the Delta files from OneLake at query time. However, assigning users to an App audience that includes such a report does not automatically grant them the required Lakehouse permissions. As a result, users added to the audience open the report and see "You don't have permission to view the content of the Direct Lake table", even though they have been explicitly granted access to the content through the App. This is especially painful with B2B guest users, and when permissions are managed through Microsoft 365 groups, whose membership does not reliably resolve for OneLake/Direct Lake permission evaluation. Today the only robust workaround is to assign each user individually at the Lakehouse level — which does not scale and defeats the purpose of App-based distribution. Proposed idea When a report backed by a Direct Lake Semantic Model is published in an App, and a user (or group) is assigned to an audience that has access to that report, the required Lakehouse permissions (Read / ReadData / ReadAll) should be propagated automatically at navigation time — scoped to the datasets/tables the report actually consumes. In other words: if content is distributed through the App and a user is granted access to it, it should be implied that the user is allowed to read the data behind it, without the administrator having to separately manage Lakehouse permissions. Why this matters The current design creates a contradiction between two Fabric optimizations: Capacity optimization (Direct Lake avoids importing/refreshing data and reduces capacity resource usage) — a clear improvement. Content distribution (App audiences are meant to be the simple, governed way to share content) — which is degraded, because App assignment alone is no longer sufficient to actually view the report. What is solved on one side (resource efficiency) is worsened on the other (distribution and access management). Aligning permission propagation with App audience assignment would remove this friction and make Direct Lake a viable choice for broadly-distributed reports without per-user manual permission management. Impact Eliminates the "You don't have permission to view the content of the Direct Lake table" error for users legitimately granted access via App. Removes the non-scalable per-user manual Lakehouse assignment workaround. Fixes the broken experience for B2B guest users and Microsoft 365 group-based sharing. Makes App-based distribution consistent between Import and Direct Lake storage modes.
Enable SharePoint File Support in Fabric Copy Jobs
Idea description Microsoft Fabric Copy Jobs currently do not support reading from or writing files directly to SharePoint sites. This limitation makes it difficult to implement straightforward and reusable data integration workflows involving documents and files stored in SharePoint. We would like to see native SharePoint file support added to Fabric Copy Jobs, enabling users to copy files between SharePoint and Fabric storage destinations, without requiring additional workarounds or custom implementation. This capability would simplify data ingestion
AI-Powered Unified Data Hub for Easy Data Discovery and Governance
Add an AI-powered Data Hub in Microsoft Fabric that provides one unified view of datasets, reports, pipelines, and real-time data. It should offer smart search, data lineage, freshness indicators, ownership, quality insights, and permission-aware recommendations, helping users quickly discover trusted data and reduce duplication.
Enhancement Request: Enable Full-Text Search Across Health & Safety Documents
Current State The Health & Safety Document Portal search functionality appears to search document titles and metadata only. (metadata, the information about a document rather than the information inside the document itself.) As a result, users must already know the exact title or key wording used in a document to successfully locate relevant policies, procedures, standards, guidance documents, templates, or learning resources. Opportunity Enhance the portal search engine to perform full-text searches across all document content, not just document titles and metadata. This would allow users to search for specific topics, hazards, controls, equipment, regulatory requirements, or process terms and return all relevant documents containing those terms. Business Benefit A full-text search capability would: Improve the ability to quickly locate the correct policy, procedure, standard, or guidance document. Reduce time spent manually opening and reviewing multiple documents. Increase worker efficiency and productivity. Improve compliance by making applicable requirements easier to find. Improve accessibility of organizational knowledge and lessons learned. Increase the value of the existing Health & Safety document repository. Reduce the risk of users relying on outdated or incorrect documents because they could not locate the most relevant source material. Example Today, a user searching for terms such as: torque verification confined space DROPS oxygen deficiency management of change contractor management may not locate all applicable documents unless those exact terms appear in the document title. With full-text indexing, the search would return all documents where those terms appear within the document body, creating a much more effective and user-friendly experience. Recommendation Implement SharePoint full-text indexing/search functionality (or equivalent) to allow searching across the contents of all documents within the Health & Safety Document Portal. Search results should prioritize document content, titles, keywords, and metadata to help users quickly identify the most relevant information. Expected Outcome Users can find the right information faster, improve compliance with Health & Safety requirements, and leverage the full value of the organization's document library without needing to know the exact document title in advance. This enhancement would significantly improve the usability and effectiveness of the Health & Safety Document Portal as a knowledge management and compliance tool.Allow selective control of individual action bar icons in Power BI Embedded (show only Copilot)
Currently, Power BI Embedded only allows the action bar (toolbar) to be toggled on or off as a whole via embed settings. There is no supported way to selectively show or hide individual icons within the action bar (e.g., Export, Bookmarks, Comments, Copilot, etc.). For embedded scenarios where we want to expose only specific functionality to end users — for example, showing only the Copilot icon while hiding all other toolbar commands — there is currently no supported configuration to achieve this. Requested capability: Provide a granular embed configuration option (e.g., an extension of the existing `settings` object in the embed config, similar to how `panes` controls individual panes) that allows developers to selectively enable/disable specific action bar icons, including Copilot, independently of the rest of the toolbar. Use case: We embed Power BI reports into our own application for external/internal users and want to surface only the Copilot assistant icon as an entry point, without exposing other report actions (export, comments, bookmarks, etc.) through the toolbar, to keep the embedded experience focused and controlled. Business impact: Without this, we are forced to either show the full action bar (exposing unwanted actions) or hide it entirely (losing the Copilot entry point), neither of which meets our embedding requirements. We'd appreciate this being considered for a future release, and are happy to provide further details if the product team needs more context.
IF Condition Scheduled Refreshes
I have many pipelines built within fabric. Now I have had IF conditions within these in order to control when the refresh actually activates. e.g. If the hour is greater that 22 but lower than 7 then fail and do not refresh. Otherwise refresh data. In lamen terms. Only refresh in the day. Recently this logic has failed and the IF condition just get's stuck in a loop of itself. A simple option would be similar to the power bi dataset schedule refresh but add some options for us similar to the logic above?Segregation of data models based on Tags
Team, it would be great if we can have a feature of grouping or filtering of all the workspace data models based on the applied Tags. Because, currently we do have an option of applying Tags to models but such criteria where can filter or group them by based on applied Tags adn this makes non sense in that case. Thank you. Prasad.
Enable Microsoft Apps in Canada Region
I would love to test the new Fabric Apps in Canada Central region. We've been looking for a potential solution to replace some dashboards built on Figma and I believe this new preview product has the potential to help us with that, but I can not test it if it is not enabled in Canada CentralRebuild Objects Metadata including Semantic Model Extract
When using shortcuts that reference Materialized Lake Views, if I need to drop and recreate the MLV (to add a field for example), then the SQL Analytics endpoint metadata gets out of sync and files can then be missing. I created a support case (2605260030001505 for any MS Internal folks looking at this idea) as there appears to be no way to force the metadata to resync other than to drop and recreate the shortcut. I worried about this due to the issues we have found with the same in Semantic Model extracts where the underlying object seemingly gets dropped and recreated and even models that were on extract then have corrupted objects which cannot be found. Any easy way to rebuild the metadata would be great and when a semantic model is on extract, the files should not be deleted referencing an object that may be dropped to ensure extracts continue to work until the next build.Monitoring Hub - Add ability to filter all 30 days of data reliably
Currently you can only filter the last 100 items when using filters which in a large environment makes the monitoring hub nearly useless as you cannot actually find some runs even from the past 24 hours when you have enough objects and the filtering is unreliable, sometimes load more returns 2 objects, sometimes 0 with the same exact conditions. This is a basic capability on other platforms, it should work in Fabric too already.