Enable individual users / freelancers to study and practice fabric with a per-user license similar to Premium Per User in Power BI. F2 is a price point that is too high for them. Strong limitations in time and resources available would make sense, but there should be a clear monthly cap that cannot be like the current F2. ... View more

Make it possible to see storage consumption at Item level in the Capacity Metrics App.   At the moment, we can only see storage consumption at Workspace level, and this makes it difficult to pinpoint exactly which items (lakehouses, warehouses) consume most storage in our workspace.   Displaying the storage size (gigabytes) at Item level would increase the usability of the Storage page in Capacity Metrics App. ... View more

We need insights into the storage consumption of active files and soft deleted files.   The Capacity Metrics App's Storage page should have the ability to show the storage size of soft deleted files and the storage size of active files. And the total.   Today, it is not possible to differentiate between storage size of soft deleted files and active files in the Capacity Metrics App. ... View more

Can we have a built-in RBAC implemented for Fabric.   In our Org we had a requirement to restrict users from updating the Fabric Capacity admins while at the same time, they should be allowed to change the SKU size.   Since both the operation SKU and Capacity Admin update use the same type:   "type": "Microsoft.Fabric/capacities",   The IAM Actions Microsoft.Fabric/capacities/write is able to update both SKU and Capacity Admin.   Is there a possibility for the PG Team to segregate the IAM actions for both SKU and capacity admins? Something like this:   For SKU Updates - Microsoft.Fabric/capacities/skus/(read/write). For capacity Admins Updates - Microsoft.Fabric/capacities/admins/(read/write). ... View more

When reserving 64 CUs or more, we should be able to use the F64 benefits (Copilot, report readers without pro license, etc.) on any workspaces assigned to capacities which are backed by the reserved CUs.   Even if we create 2xF32, the workspaces assigned to those F32 capacities should get F64 benefits because these capacities are backed by 64 reserved CUs. ... View more

As a capacity administrator, it would be extremely helpful to see all the scheduled notebooks/refreshes/dataflows/pipelines/etc in one place -- ideally with a perspective on what impact these jobs may have on the overall capacity of the workspace. Right now, anyone can set up a job to run whenever they want... and most everyone just leaves it at default -- which means twice a day (1am Pacific Time and India Time) my capacity gets dropped to its knees. Knowing what's scheduled (and who scheduled it) will enable me to mitigate this issue. ... View more

In Azure we give our resource a name using a standard naming convention. For Fabric one of our capacities is named something like xxx02prdxxxfab001 (xxx1 = our prefix, prd = production, xxx2 = solution abbrivation, fab = fabric resource, 001 = capacity number 1). We are using this naming convention, because properties of a resource can change and you don't want te get stuck with a resource name with a specific name, that might not be valid in the future.   But this name is now also the name of the capacity in Fabric, where, in Fabric, we actually want to rename it to a name more recognizable to it's properties, like "F64 production capacity". The option is already there in Fabric on the capacity settings, but you can't change the name after clicking the pencil button. We are using multiple capacities, so it would be usefull to have the ability the rename the capacities.   ... View more

When multiple ungrouped slicers are selected and copied to another page, the option to sync slicers is available.   If those slicers are in a group and said group is copied, that option no longer exists.   I like to set up a slicer page and have it sync across the whole report. Syncing all the slicers in the group would reduce clicks and allow me to quickly copy the slicers to other pages and set them as hidden. ... View more

Microsoft should allow users to choose whether to enable smoothing rather than making it a mandatory feature. The smoothing capability should be an option, not an imposition from Microsoft. Smoothing introduces uncertainty, making it difficult to optimize costs for a Microsoft Fabric subscription. Additionally, smoothing is causing challenges across multiple areas, as highlighted in discussions within the Microsoft Fabric Community. Search - Microsoft Fabric Community ... View more

This is an idea regarding the lack of possibility to limit the usage from interactive operations in Fabric and Power BI Premium capacity as that isn't possible today and users can easily cause the Fabric and Power BI Premium capacity to halt.   Request is to be able to limit usage from single interactive operations of all types (Query, XMLA Read Operation, etc) on at least the following: - Duration in seconds - % of Base capacity   Nice to have is to be able to limit usage on: - Total usage from individual dataset/semantic model - Total usage from individual workspace ... View more

It would be helpful to have a permission level between viewer and contributor that allowed users to create things like notebooks, pipelines, data flows, and add things to lakehouses, but not have the ability to create new environments.  We at Duke would like to be able to create shared environments with the approved libraries and spark settings for different size spark pools, without giving developers the ability to create their own environments, spark settings, or spark pools.  This would give us the ability to help control costs and reduce exposure to un-approved libraries. ... View more

Objective: To improve the export capabilities of Power BI reports by allowing users to export reports to PowerPoint in an editable format and ensure consistent color formatting when exporting to Excel. Current Challenge: PowerPoint Export: Currently, when exporting Power BI reports to PowerPoint, the reports are often generated as static images. This limits users' ability to make post-export modifications directly within PowerPoint, such as adjusting text, resizing visuals, or changing layouts. Excel Export: When exporting reports to Excel, users frequently experience inconsistencies in color formatting, which affects the visual consistency and presentation of the data. Proposed Solution: Editable PowerPoint Exports: Enable Power BI reports to be exported to PowerPoint in a fully editable format. Each visual and text box should be converted into native PowerPoint objects, allowing users to edit text, change colors, and resize visuals directly in PowerPoint. Maintain the structural integrity of the report to ensure that the layout remains consistent with the original Power BI report. Consistent Color Formatting in Excel Exports: Implement a feature that preserves the color scheme applied in Power BI when exporting to Excel. Ensure that all visual elements such as charts, tables, and conditional formatting rules retain their colors in the Excel export, providing users with a consistent visual experience and reducing the need for manual adjustments. Benefits: Increased flexibility and efficiency for users who need to tailor reports for specific audiences or presentations without returning to Power BI for minor edits. Improved user satisfaction by reducing the time and effort required to manually adjust formatting in exported files. Enhanced consistency in reporting across different formats, reinforcing the professional appearance of reports. Implementation Considerations: Ensure compatibility with various versions of PowerPoint and Excel to maximize the adoption of this feature. Provide users with options to choose between static and editable exports based on their preferences or needs. Consider offering a preview option to view how reports will look in PowerPoint and Excel before finalizing the export. ... View more

To make it easy to filter workspaces, and also enable cost chargeback scenarios, it should be possible to apply Tags to workspaces. ... View more

Possibility to split an F64 capacity into smaller sub-capacities, while retaining F64 benefits (e.g. Power BI free readers can read content). The capacity admin should be able to set a "ceiling" on how much compute each sub-capacity is allowed to use. This will help to avoid compute consumption getting out of hand. The sum of the max limits ("ceilings") for each sub-capacity could exceed the max limit of the original capacity. So we could be "optimistic" when assigning limits to sub-capacities, if we choose. However, if the actual combined consumption of the sub-capacities hits the limits of the original capacity, then we would of course be throttled just like today. The purpose would be the ability to limit the resource consumption of some workspaces, by assigning them to a limited sub-capacity, while also keeping the benefits of being on an F64+ capacity. ... View more

One stop display of Spark Autoscale Setting in the Admin Portal > Capacity Settings > Fabric Capacity page for all the F skus. ... View more

We would need a feature to track background operation for time ragne according to selection of filter in fabric capacity metric app ... View more

Current Challenge: Fabric Mirroring runs continuously, leading to unnecessary data replication and higher Snowflake costs. There is no built-in option to schedule mirroring based on specific times or external triggers. Suggestion: Add a native scheduling option for Mirroring (e.g., daily, hourly, or custom times). Allow event-driven refresh, triggered by external sources like Snowflake Webhooks or Azure Event Grid. Provide a data-change-based refresh, where mirroring checks for last modified timestamps before running. Benefits: Cost Optimization → Avoids unnecessary refresh cycles, reducing Snowflake compute costs. Better Data Accuracy → Ensures Fabric mirrors only when the Snowflake data is fully updated. Automation → Enables organizations to align Mirroring refresh with their Snowflake data pipeline schedules. ... View more

In Power BI premium, we can change the name of the capacity but this feature is not available for fabric capacity. This feature would allow us to maintain a clear and consistent naming convention, which is beneficial for managing multiple capacities effectively. It will also help us in auditing and reporting. ... View more

We want the option to choose metered billing in Microsoft Fabric Capacities. With this model, the billing will be based directly on the CU (s) consumed. If we consume fewer CU (s) in a month, we will pay less, and if we consume more CU (s) in another month, we will pay more. The price will be per CU (s). The compute (CU) will be elastic, so it will scale according to our consumption. This will provide maximum flexibility. This is in contrast to the established model, which charges a fixed price per second, independently of how many CUs are actually used. The new model, which can live side-by-side with the existing model, will charge a price per CU (s), where the CU is allowed to scale elastically. A customer can choose to have a mix of Elastic Fabric Capacities and F SKUs (F2-F2048). Throttling limits would be optional in the new Elastic Fabric Capacities model, empowering customers to decide whether to set an upper limit on resource usage. ... View more