I learned today that Microsoft is limiting the number of Trials per tenant. It makes sense, but there is, currently, no way to see the number of Fabric Trials that have been activated.   So please disclose this number in the Fabric Admin portal, for instance in the Capacities part under Trials. It makes it much easier to decide if we can still use a Trial for Proofs of Concept or need to log a call with Microsoft to upgrade the quota for Fabric capacities from 0 to any other number. ... View more

Service Principals cannot currently be added as Capacity Admins in Fabric/Power BI. This blocks automation, forces dependency on user accounts, and limits secure enterprise governance. Request: Enable Service Principals (or Managed Identities) as Capacity Admins to support scalable and secure operations. ... View more

Currently workspace monitoring is tied to contributor+ workspace memebers only. It does not respect workspace Permissions. This is not ideal as in a production scenario. Whereby you need to give everyone contributor or greater access to view monitoring. Thereby giving these same users ability to create/delete/update fabric items. The workaround is to build a custom monitoring report in another workspace where you use the Monitoring KQL Database as your datasource. This is a lot of overhead and effort to workaround a rather arbitrary built in security gap. Please open this up to whatever the workspace permissions are, or alternatively introduce a Monitoring Viewer role that allows access to monitoring without granting the ability to affect workspace artifacts. ... View more

Hi there,   as a Fabric Admin I would like to be able to see, which user or security group is assigned to which workspace or item in a central place like the OneLake secure tab. E.g. if I want to see, to which workspaces a user belongs to, this is not possible, only to see which role are assigned how often. Currently:   Use Case: Imagine, a security group needs to be recreated and newly assigned to the same workspaces as the old one. This is currently not possible in a central place rather than the admin needs to go through all workspaces and check if the group is assigned.   Thanks and best regards! ... View more

Writing DAX can be challenging, especially for beginners and intermediate users. While a formula may return the correct result, it is not always the most efficient or readable. Suggested Improvement: Introduce an AI-powered DAX Optimizer that can: Analyze DAX measures and suggest performance improvements. Recommend simpler and more readable alternatives. Identify redundant variables and unnecessary calculations. Highlight potential performance bottlenecks. Explain optimization suggestions in plain language. Benefits: Helps users learn DAX best practices. Improves report performance. Reduces development time. Makes Power BI more beginner-friendly. Encourages consistent, high-quality DAX development. An integrated DAX optimization assistant would be a valuable addition for both new and experienced Power BI developers and would further enhance the AI capabilities within Microsoft Fabric. Thank you for considering this idea. I believe it would improve both developer productivity and report performance across the Fabric ecosystem. ... View more

When viewing schemas and tables through the SQL Endpoint, objects are sorted alphabetically. However, when adding a Warehouse or Lakehouse as a data item inside a Fabric Notebook, the Object Explorer lists tables and directories chronologically by creation date.   With large numbers of tables, finding a specific item in the Notebook UI becomes frustrating and inefficient. Developers expect a consistent, predictable sorting behavior across all Fabric artifacts.   Requested Solution: Please change the Notebook Object Explorer so that all attached data items (Warehouse tables, Lakehouse tables, and files) automatically sort alphabetically, matching the standard SQL Endpoint experience.     ... View more

I created a Fabric App (Rayfin) with a filter on the main page to show certain vehicles (available via a semantic model).   I want to make a call to Fabric where the filter is checked via a URL query item like:   https://app.fabric.microsoft.com/groups/abc/appbackends/def?vehicleid=261008894&experience=power-bi   Unfortunately, the Fabric app does not get access to the vehicleid so the page cannot show related data.   Adding support for query parameters arriving at the app provides a more flexible way of sharing Fabric Apps URL.      Here, I tried to pass on '?userid=261008894&experience=power-bi': Nothing arrived at the app. ... View more

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

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

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

Power BI currently does not support passing advanced ODBC driver parameters in native connectors such as Amazon Redshift. Unlike other BI tools (e.g., Tableau), Power BI abstracts the connection layer and restricts authentication to predefined methods, which prevents usage of enterprise-standard authentication mechanisms. Specifically, Power BI does NOT allow configuring: IAM-based authentication (IAM=1) Custom authentication plugins (AuthType=Plugin) External Identity Provider (IdP) integration (e.g., Ping SSO) Role assumption using IAM roles (preferred_role) Advanced connection string parameters at driver level Custom proxy and federation parameters Working Scenario in Other Tools (Tableau Example) In Tableau Desktop, we are able to use advanced ODBC parameters such as: AuthType=Plugin; IAM=1; plugin_name=Ping; preferred_role=arn:aws:iam::<account-id>:role/<role-name>; idp_host=<idp_host>; idp_port=443; http.proxyHost=localhost; http.proxyPort=9000; ... This allows: AWS IAM role-based authentication Federated SSO using enterprise identity providers (Ping SAML) Dynamic role-based access control across environments (DEV/PPR/PRD) Standardized enterprise security model Business Requirement Our organization uses AWS-based data platforms (Redshift / Databricks) with: IAM role-based access control Federated authentication via Ping SSO Service accounts (SRV accounts) for BI tools We require Power BI to support: Secure IAM-based authentication Role assumption similar to Tableau Consistent enterprise authentication patterns across BI tools Microsoft Support has confirmed that: Current connectors are standard and do not allow adding custom parameters, and feature requests should be submitted via the Fabric Ideas portal.   We request the product team to evaluate and prioritize support for advanced authentication and ODBC parameter configuration, as this is a critical requirement for enterprise adoption. ... View more

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

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

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

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

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

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

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

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