Something like gorgeous Snowflake & Bigquery query plan graphical VIEVERS   - Explain main steps - With metrics each time ( rows & volumetry scanned - returned rows & volumetry)  - Techno used to reduce computing ( cache OR clustering key etc ..) - Give TSQL advises how to reduce computing   Current SET SHOWPLAN_XML is an example of SQL SERVER "old" techno badly recycled on MS Fabric   ... View more

https://docs.snowflake.com/en/sql-reference/sql/create-dynamic-table ... View more

Please enable CI/CD support (Git, Deployment Pipelines) for the Notebook resource folder:  https://learn.microsoft.com/en-us/fabric/data-engineering/how-to-use-notebook#notebook-resources   Reason: We need a way to integrate and deploy .py files containing our self-made python functions.   Scope: The need is both for Spark notebooks and plain Python notebooks.   Thanks  ... View more

I would like to be able to schedule a data refresh of the Auto Attendant & Call Queue historical reports to the PowerBi service I publish reports to the PowerBi service so managers can view data on their call queues and auto attendants. This feature was available in previous version of this report. Version 3.2.3 no longer allows you to schedule a refresh of the report due to a data source query error. ... View more

Description: When running multiple cells in a Fabric notebook (via "Run All" or "Run All Above"), the UI should automatically scroll to follow the currently executing cell and display its output in real-time. Currently, users must manually scroll to watch execution progress, and output sometimes doesn't render until the entire run completes. This makes it difficult to monitor long-running notebooks or catch errors early. Requested behavior: Automatically scroll the notebook view to the active cell as execution progresses Stream cell output in real-time as each cell runs Provide an option to toggle auto-scroll on/off for user preference This would bring the Fabric notebook experience in line with Databricks, where real-time output streaming during "Run All" is the default behavior. It improves productivity by allowing users to monitor progress, spot issues immediately, and better understand execution flow without manual intervention. ... View more

I have a report with multiple visuals, many of which can be hidden and activated via bookmarks, and others can be overlapping. When enabling edit interactions, it can be impossible to click on the interaction icons to move the visuals around. I would prefer to see a seperate window/pane where interactions can be edited effectively, similar to the ones used for syncing slicers or editing relationships. I understand that it should be a bit more complex, since interactions exist for every pair or visuals. There must be a more efficient way however.  ... View more

Offer also connection alias also for Warehouse TSQL scripts ( scripts , stored proc ) Copy into() / Bulk insert() / Openrowset() will appreciate to connect a CONNECTION ALIAS Useful for our scripts ( less code) & for CICD management ( push CICD variables to connection & not the code) Similar new notebook addition ==> https://blog.fabric.microsoft.com/en-US/blog/32822/ Certainly Warehouse web console will need to offer ready to use connections Similar new notebook addition ==> https://blog.fabric.microsoft.com/en-US/blog/32822/ ... View more

Do you think it could be realistic to think about a more "clever" cache system for Warehouse queries caches ? Something like PBI semantic model direct lake ... the "reframe" mechanism ?   Underlying data ( rows) are changing ? ==>YES ==>  reframe / recalculate the CACHE 6 hours (or more 😁) offered for caches automatically reframed ... What a dream...and game changer But ok less CUs queries consumptions... But... ... View more

We are unable to add more users as owners, and according to the document, this is a known limitation only 5 owners can be added in a scorecard. https://learn.microsoft.com/en-us/power-bi/create-reports/service-goals-get-started-hierarchies#considerations-and-limitations We should add additional users as owners for the scorecard, since having only five owners may not be enough, could we have this feature in upcoming updates of power bi.     ... View more

🟦 Request Summary Provide a supported, least-privilege API or role to access Power BI usage and audit data (user, report, workspace, timestamp, etc...) without requiring tenant-wide admin roles, enabling secure and automated governance, analytics, and compliance reporting.   🟦 Background & Business Need Need to analyze Power BI usage and adoption for governance, cost optimization, security auditing, and compliance purposes. Typical requirements include understanding: Who accessed which Power BI report When the access occurred Which workspace and dataset were involved What type of connection was used (Import, DirectQuery, Live, AS) Currently, the Power BI Activity Events API is the only supported source that provides this level of detail. However, accessing this API requires assigning Power BI Service Administrator or Fabric Administrator roles to the calling identity (user or service principal). In many enterprises, especially those with: Strict security controls Segregation-of-duties policies Internal and external audit requirements Regulated environments (finance, healthcare, government) granting tenant-wide admin roles to automation identities or analytics teams is not acceptable, even for read-only reporting purposes. As a result, organizations face a difficult trade-off between: Achieving visibility into Power BI usage, or Maintaining least-privilege and compliance standards This challenge is common across organizations of all sizes and industries. 🟦 Expected Benefits Introducing a read-only, least-privilege access model for Power BI usage data would deliver significant benefits: ✅ Enables secure, automated usage and adoption analytics ✅ Reduces need for broad tenant admin role assignments ✅ Aligns with enterprise security and compliance best practices ✅ Improves governance, capacity planning, and cost management ✅ Supports audit and monitoring requirements without elevated risk ✅ Benefits all customers, from small tenants to large regulated enterprises Such an enhancement would allow customers to fully leverage Power BI and Fabric telemetry while maintaining strong security boundaries, and would encourage broader adoption of Microsoft-recommended governance practices. ... View more

Overview Microsoft Fabric provides strong governance constructs for data, semantic models, workspaces, and capacity usage. However, email subscriptions remain governed by a single tenant-wide on/off setting that does not align with how Fabric is operated in controlled enterprise environments. There is currently no supported way to allow managed subscriptions for administrators or reporting teams while preventing end-user self-service subscriptions. Context In many Fabric tenants: Only designated reporting teams are permitted to publish content to Fabric capacities Workspaces, apps, and access are centrally governed Reports often contain sensitive or regulated information Distribution of report outputs is considered a controlled operational activity These tenants do not operate as self-service environments. Instead, reporting teams act as trusted publishers responsible for both content and distribution. Current Limitation Fabric email subscriptions are controlled by a single tenant setting: Enabled: Any user with access to a report can create subscriptions Disabled: No subscriptions can be created, including by tenant admins, workspace admins, app owners, or service principals There is: No security group scoping No role-based permission No admin override No publisher-owned subscription model Fabric capacity, workspace roles, sensitivity labels, and admin APIs do not provide governance over subscription creation or ownership. Why This Is a Problem This design assumes that: Viewing data implies authority to distribute it Subscriptions are an end-user convenience feature In governed Fabric environments, this assumption does not hold. As a result: Native subscriptions must be disabled entirely Organizations are forced to build custom delivery solutions using Power Automate or REST APIs Reporting teams cannot use a built-in Fabric capability for a common enterprise requirement This creates unnecessary complexity for a basic reporting scenario. Requested Capabilities Fabric needs a governed subscription model aligned with enterprise usage patterns. Examples include: Security-group scoped subscription control Allow subscriptions only for specified Azure AD groups (e.g., reporting teams) Publisher-managed subscriptions Subscriptions owned by a workspace, app, or report — not by individual users Role-based permission separation Distinct permission for “Create subscriptions” separate from “View content” Admin override capability Allow tenant or workspace admins to manage subscriptions even when end-user subscriptions are disabled Business Impact Without a governed subscription model: Fabric’s native subscription feature cannot be used in sensitive or regulated environments, e.g., PII or publicly traded entity. Reporting teams cannot provide managed, auditable report delivery using first-party Fabric features. Reporting teams cannot control subscription distributed to Outlook, which leadership considers unsafe. This is not a request for additional self-service functionality, but for controlled, publisher-owned distribution consistent with Fabric’s governance direction. Closing Fabric has made significant progress in enterprise governance. Email subscriptions remain an exception that assumes a low-risk, self-service usage model. Introducing a governed, publisher-managed subscription capability would enable Fabric to better support mature, security-conscious tenants without compromising existing self-service scenarios. ... View more

Hello. As for now the when we connect SQL database source and there appears a SQL querry window. Currently this window shows only few rows and it seems very uncomfortable to write more complex querries. The idea is to expand this or make it expandable to see more querry code. ... View more

https://learn.microsoft.com/en-us/fabric/data-engineering/notebook-utilities At the moment if we want to work with the results from notebookutils.notebook.runMultiple we only get back the "Activity name", "Exit value" and "Exception". I would also like to get "Status" and "Duration" in the results, not only get it in the gui as we see in the picture. ... View more

There is a system storage option in the workspace settings that displays the size of the semantic model. This feature was available at the workspace level, but we need an option at the tenant level that displays the size of all semantic models across the tenant. ... View more

Currently identifying entities is manual, custom accelerator can be built. Does microsoft has any plan for same so that based on data and use case it can suggest entities and relation model ... View more

Learn more in Workspace availability points into microsoft.com website. It should point into correct documentation page or the link should be completely removed until documentation is ready.     ... View more

Support Wildcards in OPENROWSET for SharePoint-Backed OneLake Shortcuts Summary OPENROWSET does not support wildcard paths when querying files via OneLake shortcuts pointing to SharePoint/OneDrive, even though the same syntax works for native OneLake / ADLS paths. Current Behavior Wildcard patterns (e.g. *.csv) fail when the underlying path is a SharePoint shortcut because the engine attempts a directory listing that SharePoint shortcuts do not expose. SELECT * FROM OPENROWSET( BULK 'abfss://<workspace>@onelake.dfs.fabric.microsoft.com/<lakehouse>/Files/sp-shortcut/data_*.csv', FORMAT = 'CSV' ) AS r;     Msg 13807: Content of directory cannot be listed   Expected Behavior Wildcard expansion should work for SharePoint/OneDrive shortcuts, consistent with native OneLake and ADLS behavior. Impact Users cannot query partitioned or multi-file datasets stored in SharePoint via shortcuts. Forces manual file enumeration or data duplication into native OneLake storage.     ... View more

Hi, it would be very useful to enable taking control of mirrored databases, because if someone leaves the organization, it has to be recreated from scratch. ... View more

Shortcut variables are mapped to the variable library. When we change the default values to new ones and click "update variables" in Lakehouse, it still refers to the old values. The new values aren't reflected, and if we move to production, this could cause our data to be misleading. ... View more