VOOZH about

URL: https://community.fabric.microsoft.com/t5/Fabric-Ideas/idb-p/fbc_ideas

⇱ Fabric Ideas - Microsoft Fabric Community


skip to main content

Get Fabric or SQL Certified for Free.

Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.

Join now
Skip to main content
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Data Days is here! Join us now for 60+ days of learning, challenges, and connection. Learn more

Share your ideas and vote for future features

Suggest an idea
Submitted Friday Submitted by 👁 Microsoft Employee
MSReshma
Friday
Currently, Microsoft Fabric / Power BI does not provide a built-in, native alerting mechanism to notify administrators before capacity throttling occurs.   While the Capacity Metrics App helps monitor utilization trends, there is no out-of-the-box feature that proactively notifies when capacity is nearing its limit (for example 80–90% utilization). This makes it difficult for administrators to take preventive action before throttling impacts users.   Capacity throttling can lead to: Report performance degradation Delays in query execution Poor end-user experience Having a native alerting capability would significantly improve proactive monitoring and operational efficiency. ... View more
Status: New
See more ideas labeled with:
Submitted Thursday Submitted by AbhinavDhami Thursday
Is there an option to show the Report Name in the URL of a report published on Power BI workspace using Premium Capacity. Currently the URL only shows up Report ID and not the name of the report, Below reference to the problem : Current : https://app.powerbi.com/groups/4897864dfhf-dght56nn-edonnd88/reports/a409be977-91c9-489d0-be56-1870d2e165b8/ReportSection?experience=power-bi Requirement : https://app.powerbi.com/groups/4897864dfhf-dght56nn-edonnd88/reports/Sales_Incentive_Report/ReportSection?experience=power-bi ... View more
Status: New
See more ideas labeled with:
Submitted Thursday Submitted by Sivasankarir Thursday
When using the search bar in a slicer, the "Select All" option disappears from the list, making it impossible to select all matching results at once. Users are forced to manually check each item individually. Expected behavior: "Select All" should remain visible (and functional) while a search filter is active, selecting only the items matching the current search — not all items in the slicer. This would significantly improve usability, especially for slicers with large datasets. ... View more
Status: New
See more ideas labeled with:
Submitted Thursday Submitted by AbhinavDhami Thursday
We have multiple columns which we need to drag and drop into a Table visual and need the aggregation (summation to be performed ). Currently whenever we drop a field iin the table it renames to Sum of "XYZ" and we have to manually remove Sum from the name of the field. Is there any option whereinwe could do this by defa ult in settings and if not could this be considered as an enhancement request ? ... View more
Status: New
See more ideas labeled with:
Submitted Thursday Submitted by valeria_dia Thursday
Hi, we have a Silver Warehouse and in many cases we create views instead of copying the data from the bronze layer. The Warehouse is located in EDW workspace, but analysts and data scientists work in other workspaces. So for their convinience we would like to add shortcut to the Silver warehouse views and tables in their workspace. But currently only tables are available for selection when we do that.   What we do to create a shortcut: 1. Create a Lakehouse in the Shortcuts folder. 2. Open the Lakehouse and click on Tables -> New schema shortcut.   3. Choose Microsoft OneLake. 4. Choose the warehouse from the different workspace. 5. We can only see the Tables, and not Views   Can we please ask to add the ability to add Views as well as tables. It will help our data consumers to simplify their queries and improve the data exploration options. ... View more
Status: New
See more ideas labeled with:
Submitted Tuesday Submitted by wendy_jackson Tuesday
Power BI App audiences are a key access management feature, yet audience membership cannot be retrieved through the REST API. This limits governance, auditing, and automated access review capabilities. Problem Power BI App audiences are widely used to manage access to reports and dashboards across organisations. However, audience membership can currently only be reviewed through the Power BI Service user interface. This creates challenges for report owners, workspace administrators and governance teams who need to perform regular access reviews. For organisations with many apps and audiences, reviewing access requires manually navigating through each app and audience configuration, making periodic reviews time-consuming and difficult to evidence. Proposed Enhancement Provide REST API support for retrieving Power BI App audience configuration and membership, including: App details Audience names Assigned users Assigned security groups Assigned Microsoft 365 groups Effective audience permissions and visibility settings Business Value Improved Governance Supports periodic access reviews by allowing organisations to generate consolidated reports of who has access to Power BI Apps. Compliance and Audit Many organisations are required to regularly review user access to business-critical reporting platforms. API access would enable automated evidence collection for audit and compliance processes. Operational Efficiency Reduces the need for manual review through the Power BI Service and enables self-service reporting for app owners. Better Adoption of App Audiences App audiences are a recommended way of managing report access at scale. Providing API visibility would increase confidence in using audiences as a governance mechanism. Example Use Cases Quarterly access certification exercises Internal and external audit requests Governance dashboards showing who can access which business reports Identification of stale or over-permissioned audiences Automated notifications to app owners for access reviews Additional Consideration Ideally, the API would also support retrieving effective membership where Entra ID groups are assigned, enabling a complete view of report access without requiring manual investigation across multiple systems. ... View more
Status: New
Submitted Thursday Submitted by Pamela_Asc Thursday
Power BI restricts the use of complex DAX measures within page- or report-level filter panes and prohibits their use as dimensions on chart axes. This forces developers to duplicate logic by creating static calculated columns, which inflates the in-memory model size (VertiPaq) and eliminates dynamic interactivity based on user context. Enabling this feature would drastically optimize report performance. It would avoid redundant ETL processes or overloaded DAX code (such as the excessive use of disconnected virtual tables).     ... View more
Status: New
See more ideas labeled with:
Submitted Thursday Submitted by Pamela_Asc Thursday
Calculated columns are computed statically only during data refresh (within the VertiPaq engine). Once processed, they remain fixed in memory and completely isolated from user interactivity; they do not respond to slicers, page filters, or cross-visual selections. This limits advanced data segmentation. If a developer needs to classify customers or products based on dynamic, user-influenced criteria (e.g., changing a date range), the calculated column becomes useless. Introduce a new column type ("Runtime Column"). This object would retain the structural properties of a column (serving as chart axes and slicer inputs) but would recalculate its rows on the fly, responding dynamically to the active filter context in the report. ... View more
Status: New
See more ideas labeled with:
Submitted Tuesday Submitted by p_tomas Tuesday
Descripción Actualmente, cuando se necesita aplicar formato condicional en Power BI o Microsoft Fabric comparando una métrica con otra métrica, es necesario crear medidas adicionales en DAX específicamente destinadas a gestionar la lógica visual (colores, iconos, indicadores de estado, etc.). En entornos corporativos con un elevado número de indicadores, objetivos y métricas de referencia, esta limitación obliga a crear numerosas medidas auxiliares que no aportan valor al modelo de negocio, sino que existen únicamente para soportar el formato condicional. Como consecuencia, los modelos semánticos se vuelven más complejos, difíciles de mantener y menos intuitivos para desarrolladores y administradores. Propuesta de mejora Incorporar la posibilidad de definir reglas de formato condicional mediante comparaciones directas entre métricas, sin necesidad de crear medidas intermedias. Por ejemplo, permitir configurar condiciones como: Ventas Reales > Ventas Objetivo Cumplimiento Actual ≥ Cumplimiento Planificado Nivel de Servicio < Umbral Objetivo Valor Actual entre Límite Inferior y Límite Superior utilizando directamente las métricas existentes en el modelo. Beneficios Simplificación de los modelos semánticos Reduciría significativamente la cantidad de medidas auxiliares necesarias, facilitando el mantenimiento y la comprensión de los modelos. Menor complejidad en DAX Se eliminaría la necesidad de desarrollar medidas específicas cuyo único propósito es devolver estados, colores o indicadores visuales. Mejor gobernanza y escalabilidad Al disminuir el número de medidas: Los modelos serían más limpios y fáciles de administrar. Se reduciría el esfuerzo de mantenimiento. Se simplificaría la gestión cuando cambien las reglas de negocio. Los autores de informes trabajarían con listas de campos menos saturadas. Mejor experiencia de usuario Los usuarios podrían configurar reglas de formato condicional de forma más intuitiva desde la interfaz, sin necesidad de conocimientos avanzados de DAX. Ejemplo práctico Supongamos que un modelo dispone de las siguientes métricas: [Valor Real] [Objetivo] Actualmente es necesario crear una medida adicional como:         DAX   Estado = IF ( [Valor Real] >= [Objetivo], 1, 0 ) Mostrar más líneas   o una medida que devuelva colores para poder aplicar el formato condicional. Con esta mejora, podría configurarse directamente una regla como: Si [Valor Real] ≥ [Objetivo] → Verde En caso contrario → Rojo sin crear ninguna medida adicional. Impacto empresarial Las organizaciones que gestionan cientos de KPIs e indicadores suelen requerir múltiples reglas de formato condicional en cuadros de mando e informes. Permitir comparaciones directas entre métricas reduciría el esfuerzo de desarrollo, mejoraría la mantenibilidad de los modelos y favorecería la adopción de buenas prácticas en Microsoft Fabric y Power BI. Esta funcionalidad aportaría una solución más simple, escalable y alineada con las necesidades reales de los entornos empresariales donde las comparaciones entre métricas son una necesidad habitual. ... View more
Status: New
See more ideas labeled with:
Submitted Thursday Submitted by Pamela_Asc Thursday
When using Power BI’s modern Visual Calculations feature to perform mathematical operations directly on chart axes—such as running totals, moving averages, or differences—the source columns (text or base numeric values) must be present in the visual for the formula to work. Keeping these base columns visible clutters the report, overwhelms the view with data that is duplicated or irrelevant to the end user, and compromises the design experience (UI). ... View more
Status: New
See more ideas labeled with:
Submitted Tuesday Submitted by kritchensBMcD 👁 Advocate III
Tuesday
When it comes to mirroring there is a gap when it comes to sharepoint Libraries. In the Main Interface it shows the library as a list, but it defaults to just creating a onelake shortcut to the files without the associated metadata.  Metadata should also be mirrored or be an option to mirror than just sharepoint lists alone. Many Sharepoint Libaries are enriched with metadata that can be used for reporting or data transformation.      ... View more
Status: New
See more ideas labeled with:
Submitted on ‎06-18-2026 10:10 AM Submitted by 👁 Microsoft Employee
mdrakiburrahman
on ‎06-18-2026 10:10 AM
Scenario I have Admin in Production Workspace, meaning I can write to Production OneLake. I am doing work in Development Workspace, I want to OneLake shortcut Production Workspace Delta Table.   Problem is, in my Development Workspace, I can mutate the Production table through my shortcut.   Solution I understand OneLake shortcut uses blobfuse: Azure/azure-storage-fuse: A virtual file system adapter for Azure Blob storage   Blobfuse already comes with a `--read-only` flag: blobfuse2 mount "${mount_path}" --config-file="${config_file}" --read-only=true --allow-other   So, if Lakehouse shortcut could expose this flag via your Control Plane, we could mount a shortcut with read only. ... View more
Status: New
See more ideas labeled with:
Submitted on ‎06-16-2026 11:30 PM Submitted by tkirschke on ‎06-16-2026 11:30 PM
Problem Statement Currently, Microsoft Fabric’s Zero-Copy Cloning functionality is limited in scope, making it difficult to implement robust CI/CD and "environment-switching" workflows for dbt projects. Specifically, we cannot perform a cross-warehouse clone for tables and views when the source and target warehouses reside in different Fabric Warehouses, even when they are within the same Capacity and Workspace. Use Case I am utilizing dbt to manage data transformations in Microsoft Fabric. To follow best practices, I need to maintain distinct environments (e.g., DEV, STAGING, and PROD) represented by separate Warehouses. In a dbt workflow, the dbt clone command is critical for: Environment Parity: Creating lightweight, ephemeral copies of production data for testing changes without duplicating storage costs or incurring massive data movement overhead. Safe CI/CD: Validating dbt models against a snapshot of current data before merging into production. Requested Feature Please extend the CREATE TABLE AS CLONE OF / CREATE VIEW AS capabilities to support cross-warehouse cloning within the same Workspace and Capacity. This would allow dbt to seamlessly manage environments by cloning objects from a PROD warehouse into a DEV or STAGING warehouse instantaneously, without physically copying the underlying data. Expected Business Impact Cost Efficiency: Eliminates the need to physically copy large datasets across environments, drastically reducing storage and compute costs. Development Velocity: Allows data engineers to create production-mirror environments in seconds rather than minutes or hours, leading to faster iteration cycles. Adoption of Data Ops: Removes a significant barrier for dbt users migrating to Fabric, making Fabric a first-class citizen in the modern Data Ops ecosystem. ... View more
Status: New
See more ideas labeled with:
Submitted Sunday Submitted by RahulPatel96 Sunday
We would like Microsoft to add full support for embedded custom fonts when exporting Power BI reports to PDF, including reports distributed through subscriptions and Power BI Service exports. Many organisations invest in licensed brand fonts as part of their corporate identity and reporting standards. While custom fonts can be used successfully within Power BI reports, exporting to PDF often results in font substitution, causing reports to lose their intended formatting, brand consistency, and professional appearance. Current Challenges Custom fonts are replaced with default fonts during PDF export. Exported reports do not match what users see in Power BI Desktop or the Service. Corporate branding requirements cannot be fully met. Report layouts may shift due to differences in font sizing and spacing. Organisations are forced to redesign reports using supported fonts rather than approved brand fonts. Proposed Enhancement Provide one or more of the following options: Embed custom fonts directly into exported PDFs when licensing permits. Allow administrators to upload approved organisation fonts within Power BI or Microsoft Fabric. Support font packaging during report publishing so exports preserve the exact typography used in the report. Display compatibility warnings when unsupported fonts are detected. Include custom font support in PDF exports, PowerPoint exports, and email subscriptions. Business Impact Maintains corporate branding across exported reports. Produces board-ready and client-facing documents without manual rework. Improves consistency between Power BI Desktop, Service, and exported outputs. Reduces time spent recreating reports in external tools purely for branded PDF distribution. Supports organisations with strict marketing and brand compliance requirements. Example Use Case Our organisation has purchased and uses corporate brand fonts across all reporting platforms. Reports display correctly within Power BI; however, when exported to PDF for executive leadership, board packs, and external stakeholders, the fonts are replaced with alternatives. This results in inconsistent branding and requires manual intervention before distribution. This enhancement would significantly improve Power BI's suitability for enterprise reporting and align exported documents with organisational branding standards. Vote if you need exported PDFs to look exactly the same as the report displayed in Power BI, including support for licensed custom fonts. ... View more
Status: New
See more ideas labeled with:
Submitted on ‎10-07-2024 10:00 PM Submitted by 👁 Microsoft Employee
Miguel_Myers
on ‎10-07-2024 10:00 PM
The current card visual forces users to overlap elements or waste copious amounts of time creating custom visuals. The new card feature should give users the ability to create multiple cards in a single container and provide a greater level of customization. ... View more
Status: Needs Votes
See more ideas labeled with:
Submitted on ‎10-07-2024 10:00 PM Submitted by 👁 Microsoft Employee
Miguel_Myers
on ‎10-07-2024 10:00 PM
It would be beneficial to incorporate features from Pivot tables that allow for the expansion and collapse of columns and hierarchical column groups within tabular visuals. This would not only solve the current limitations of matrices but also provide report creators with the flexibility to hide and show rows and columns, saving these settings for future use, thus eliminating the need to scroll through irrelevant data. ... View more
Status: Under Review
See more ideas labeled with:
Submitted Tuesday Submitted by basenergy Tuesday
BUG: Page controls Fabric Lakehouse PDF preview not visible on default browser zoom level   Files in a Fabric Lakehouse can be previewed in the Fabric Lakehouse UI.  However the page controls for the PDF are not visible unless the user zooms out to about 60% zoom level in the browser. At 100% level the page controls are cut off from the UI and there is no way to scroll down to the buttons.  ... View more
Status: New
Submitted on ‎06-14-2026 11:58 PM Submitted by 👁 Microsoft Employee
kyubaekkim
on ‎06-14-2026 11:58 PM
Currently, SAP Connectors in Microsoft Fabric do not support integration with Azure Key Vault (AKV). However, in many enterprise environments, it is a mandatory requirement to manage credentials centrally using Azure Key Vault for secure access to databases and external systems. SAP Business Warehouse Server SAP Business Warehouse Message Server SAP HANA       ... View more
Status: New
Submitted on ‎10-07-2024 10:00 PM Submitted by 👁 Microsoft Employee
Miguel_Myers
on ‎10-07-2024 10:00 PM
Enabling customized calculations at the query level for subtotals and grand totals would offer greater flexibility in reporting and preserve performance. Efficient organization of control settings to modify the style of these totals separately will empower report creators to achieve their desired appearance, while addressing their need for more control and customization in reporting. ... View more
Status: Needs Votes
See more ideas labeled with:
Submitted on ‎10-07-2024 10:00 PM Submitted by 👁 Microsoft Employee
Miguel_Myers
on ‎10-07-2024 10:00 PM
Imagine a world where report creators can automatically apply slicer and filter selections based on specific logic, revolutionizing data analysis and user experience. This innovative approach eliminates any need for complex workarounds, optimizes slicer functionality, and paves the way for more efficient and effective data reporting. ... View more
Status: Needs Votes
See more ideas labeled with:

Helpful resources