During Lakehouse deletion operations in Microsoft Fabric, users may observe that the associated SQL Endpoint and Semantic Model are not automatically removed. These orphaned artifacts may cause downstream deployment errors or stale resource references.   There is one available API to remove it, but it is not very user friendly and also requires admin rights so developers cannot do this on their own. It is mentioned here: Solved: Can't delete orphaned lakehouse SQL analytics endo... - Microsoft Fabric Community   The idea is to make this option available in the UI or at least provide more user friendly ways to do it. ... View more

I’m building a logic in my application that depends on the size of my Power BI or Fabric datasets. Currently, there’s no available API or endpoint to get this information. It would be really helpful if Microsoft provided a way (through the Power BI REST API or Fabric API) to retrieve the dataset size — similar to what is shown in Workspace Settings → System Storage (API) inside the Power BI service.   Having access to this value programmatically would help developers: Monitor dataset growth automatically Implement custom alerts and optimizations Manage workspace storage usage efficiently ... View more

Currently the only option for connecting to a lakehouse using a cloud connection is an organisational account. Adding in Service Principal as an option would avoid the reliance on single user accounts and would bring the lakehouse connector into parity with the warehouse connector. ... View more

Considering the most powerful and versatile machines are being built on ARM processors and many developers preferring these machines due to the extended battery life, or performance per watt, I think it would be critical for Microsoft to start developing Power BI Desktop to be fully compatible with ARM64 processors. Windows ARM with a snapdragon processor is a great machine. It is where all machines are going. It's time for Power BI Desktop to get up to speed with everything else. ... View more

This is purely for aesthetic and usability reasons.   Now that a default semantic model is no longer generated when creating a new Lakehouse, could we consider streamlining the user experience by merging the Lakehouse and its SQL analytics endpoint into a single item? At the moment, having them listed separately feels a bit redundant and visually inconsistent. Consolidating them would make the interface cleaner and more intuitive.       ... View more

To fix inconsistencies in analytic settings, functionality needs to be enhanced to ensure they are on par with other visual component enhancements made for Cartesians, and additional settings for scatter charts is also necessary. Report creators will find it easier to format and customize settings to align with the overall look and feel of their reports. ... View more

Situation :  Currently, Power BI (/Microsoft Fabric) do not provide a native way to automatically configure credentials for Synapse Serverless connections, especially in scenarios where automated deployments or service principals are used. This limitation makes it difficult to implement fully automated solutions for data access and refresh without manual intervention.   Requested Feature: Introduce native support for automated credential configuration for Synapse Serverless connections in Power BI and Fabric. Specifically, it should: Allow service principals and managed identities to authenticate without manual setup Support secure, scalable automation across enterprise environments Integrate with deployment pipelines and governance models Optionally integrate with Azure Key Vault for secure credential storage Why this matters: This feature would enable organizations to build robust, secure, and automated BI solutions while eliminating manual, error-prone steps. It is critical for: Large-scale deployments and CI/CD automation Enterprise compliance (MFA, ISO, SOC, GDPR) Reducing credential leakage risks from insecure workarounds Additional Technical context (use case): Current workaround using ROPC (Resource Owner Password Credentials) fails when MFA is enforced, which is common in enterprise environments. Service accounts with MFA cannot be used for automated refresh, creating a gap for organizations that follow strict security policies. A native solution should support Azure AD authentication via service principals or managed identities, similar to other Fabric connectors. This would align with modern security practices and eliminate the need for insecure credential storage or manual intervention. Technical Context (Use Case) The current ROPC (Resource Owner Password Credentials) workaround fails under MFA — now mandatory in most enterprises. Service accounts with enforced MFA cannot be used for automated refresh, leaving a gap for secure automation. A native solution should support Azure AD-based authentication via service principals or managed identities, similar to Azure Data Factory and Synapse Pipelines. API Attempts Power BI REST API: PATCH /gateways/{gatewayId}/datasources/{datasourceId} → update credentials programmatically POST /gateways/{gatewayId}/datasources → create data sources with credentials Fabric / Power BI Service Principal Authentication: Tested OAuth2 flows using client_id and client_secret for service principals MFA enforcement blocks ROPC flow Synapse SQL Connection (DirectQuery): Attempted credential injection via deployment pipelines using Update Datasource API No native credential automation support Proposed Direction Add Managed Identity and Service Principal support for Synapse Serverless in Power BI datasets Enable credential binding through REST API or Fabric Deployment Pipelines Integrate Key Vault for secure, centralized credential management Call to Action / Request We strongly encourage Microsoft to prioritize this capability to align Power BI and Fabric with modern cloud security and DevOps automation standards, comparable to Azure Data Factory and Synapse Pipelines.   Thanks to @v-pnaroju-msft for your assistance & ideas   ... View more

Currently, detailed run log access from the Monitoring Hub for Dataflow Gen2 (CI/CD), notebooks and others items are not available. The idea is to use Monitoring Hub to debug and have detailed run log access directly from the Hub.   Vote if it's USEFUL for you !  ... View more

Paginated reports - please make it available in Pro as well as Premium .. thank you ... View more

It would be extremely helpful to have a built-in feature in Power BI that allows administrators to identify inactive users segmented by license type (Free, Pro, Premium Per User, Embedded, etc.). ... View more

Experimenting with Copy Job. Yeah, OK, but not great. Some suggestions: 1) Make the option for OVERWRITE available for Warehouse destinations. Currently available for Lakehouses only. This article (What is Copy job in Data Factory - Microsoft Fabric | Microsoft Learn) does not differentiate that option. Honestly, how hard it is to program in a DROP TABLE IF EXISTS statement in the back end code? Warehouses support such actions.   2) Give the user the abiltiy to DISABLE a table in the list. If I have a list of 50 tables in my job, but during development only want to refresh 2 of them, I have to run the whole job. Waste of time and resources. ... View more

Description: In Power BI Report (PBIR) metadata, every visual already has an isHidden property that controls its visibility. Today, however, this property can only be set manually in the UI (via the Selection pane). There is no way to drive this property dynamically using a DAX expression. This is a major limitation because one of the most common use cases for Bookmarks is to simulate conditional visibility (show/hide visuals depending on user selection or business logic). While bookmarks work, they are cumbersome, static, and hard to maintain at scale. Proposal: Enable a new “Visibility” binding for visuals in the format pane, where authors can assign a DAX measure (fx) returning TRUE/FALSE (or 0/1). If the measure evaluates to TRUE → visual is shown. If FALSE → visual is hidden (not rendered). Benefits: Much more flexibility for UX/UI design. Reduces dependency on complex bookmarks. Simplifies scenarios such as: Show a chart only if a slicer is selected. Hide detailed visuals until a KPI passes a threshold. Display different layouts per user role or context. Aligns with the existing isHidden property already in PBIR at visual level, making it available for dynamic scenarios. Why now Conditional visibility is a frequent request feature in the community. Users of other Microsoft data platform solutions, such as Power Apps, are accustomed to having the ability to modify this property. PBI developers already simulate this via workarounds (blank measures, bookmarks, overlaid shapes with managed transparency).   A native solution would make reports more dynamic, performant, and easier to maintain.   @Miguel_Myers  ... View more

Description: Currently, Fabric Pipelines connect to native Fabric Lakehouses and Warehouses using user-bound tokens that expire approximately every 90 days. When these tokens expire, pipelines that invoke Warehouse or Lakehouse activities fail with authentication errors. The only workaround today is to manually open and re-save each pipeline, which regenerates the token. This approach becomes impractical and error-prone as the number of pipelines and workspaces grows across enterprise environments. Impact: Pipelines fail unpredictably in production after token expiry. Requires manual intervention across dozens or hundreds of pipelines. Causes disruption to scheduled ETL/ELT workflows. Inconsistent behavior compared to external connectors, which already support Workspace Identity. Typical Error Message: ErrorCode=UserAuthFailedToGetToken Message=Failed to get User Auth access token. AADSTS700003: Device object was not found in the tenant directory. This occurs after token expiration and causes pipelines to fail until re-saved. Proposed Enhancement: Add support for Workspace Identity Authentication for native Fabric Lakehouse and Warehouse connections in Pipelines. This would allow Fabric pipelines to: Authenticate using the workspace’s managed identity (non-user-dependent). Automatically renew tokens without user re-login. Align authentication behavior with Dataflows Gen2, Notebooks, and other Fabric connectors that already support Workspace Identity. Business Justification: Enterprise tenants typically operate multiple Fabric workspaces and dozens of pipelines per domain. Removing token dependencies will: Ensure reliable, unattended execution of production data pipelines. Eliminate recurring manual maintenance. Improve operational scalability and governance consistency. ... View more

Please fix this, so the Dataflow will get validated automatically after syncing changes from Git or using deployment pipelines:   "When you sync changes from GIT into the workspace or use deployment pipelines, you need to open the new or updated dataflow and save changes manually with the editor. This triggers a publish action in the background to allow the changes to be used during refresh of your dataflow. You can also use the on-demand Dataflow publish job API call to automate the publish operation."   https://learn.microsoft.com/en-us/fabric/data-factory/dataflow-gen2-cicd-and-git-integration#limitations-and-known-issues   Because this currently doesn't happen automatically, it causes confusion, unnecessary manual work, and often we forget this and therefore get unexpected results when running the dataflow. ... View more

Power BI Semantic Data Modeling - More than one relationship.  If this option is enabled, we can avoid creating more calcualted columns to define the key for establishing the relationship.  ... View more

Re: API Call for Workspace Contacts in Workspace S... - Microsoft Fabric Community   Retrieve workspace contacts from workspace settings via REST API Call   I need to Track Capacity backed workspace contacts across the organization in a Workspace catalog So that i can ensure each workspace is properly administered and managed       ... View more

Current Problem Different departments create reports in separate workspaces (e.g., Sales, HR, Finance). Each report contains pages segmented by audience (executive, manager, operational). Current functionality doesn’t fully solve this scenario: Workspace App → allows audiences, but only within a single workspace. Org App → allows multiple apps per workspace, but cannot combine pages across workspaces. As a result, to build a corporate app (e.g., for the Board) that consolidates only executive-level pages from each department, we must either duplicate PBIX files or create separate versions of reports, leading to redundancy and maintenance overhead. Suggested Feature Introduce a new capability, for example: “Corporate App with Cross-Workspace Pages” or “Cross-Workspace Page Selector.” This feature would allow: Selecting specific report pages across multiple workspaces and aggregating them into a single Org App. Example: “Executive View – Sales” (Sales Workspace) + “Executive View – HR” (HR Workspace) → App “Board of Directors.” Defining page-level visibility rules by audience profile (without duplicating PBIX). Executives → see only executive summary pages. Managers → see management pages. Operational staff → see detailed tactical pages. Maintaining a single source of truth → updates to the original PBIX automatically flow into all apps where its pages are used. Benefits Reduced redundancy → no need for multiple PBIX files per audience. Centralized governance → reports remain in their original workspaces, respecting ownership and security. Personalized experiences → each audience gets a tailored app containing pages from different workspaces. Scalability → leadership can access a single consolidated app with executive views across all departments. Idea Summary 🔹Today: PBIX files must be duplicated or apps limited to a single workspace. 🔹With the new feature: build custom multi-workspace apps by selecting specific pages per audience, without duplication. -------------------------- PT/BR Proposta de Nova Funcionalidade para Power BI – "Cross-Workspace Page-Level Security nos Apps" Problema atual Departamentos diferentes produzem relatórios em workspaces distintos (ex.: Comercial, RH, Financeiro). Cada relatório possui páginas segmentadas por público (diretoria, gerência, operacional). As funcionalidades existentes não resolvem o cenário: Workspace App → permite um único app com audiências, mas só dentro de um mesmo workspace. Org App → permite múltiplos apps por workspace, mas ainda não mescla páginas/reportes entre workspaces. Resultado: para criar um app corporativo único (ex.: Diretoria) que agregue apenas páginas executivas de cada departamento, é preciso duplicar relatórios ou criar PBIX separados, gerando redundância, retrabalho e manutenção complexa. Sugestão de Funcionalidade Criar um recurso chamado, por exemplo: “App Corporativo com Páginas Cruzadas” ou “Cross-Workspace Page Selector”. Esse recurso permitiria: Selecionar páginas específicas de relatórios em diferentes workspaces e agregá-las em um único Org App. Exemplo: Página “Visão Executiva – Comercial” (Workspace Comercial) + Página “Visão Executiva – RH” (Workspace RH) → App “Diretoria”. Aplicar regras de visibilidade por perfil no nível de página, sem precisar duplicar PBIX. Diretores → veem apenas páginas executivas. Gerentes → veem suas páginas de gestão. Operacionais → veem suas páginas táticas. Manter a fonte única do relatório original → qualquer atualização no PBIX se reflete automaticamente em todos os apps que utilizam suas páginas. Benefícios Menos redundância → elimina necessidade de múltiplos PBIX por público. Governança centralizada → páginas continuam no workspace de origem, respeitando ownership e segurança. Experiência personalizada → cada perfil recebe um app customizado com páginas de diferentes workspaces. Escalabilidade → diretoria pode ter um app único consolidando visões executivas de todos os departamentos. Resumo da Ideia 🔹Hoje: ou duplicamos PBIX ou limitamos apps a um workspace. 🔹Com a nova funcionalidade: montar apps personalizados multi-workspace, selecionando páginas específicas por público, sem duplicar relatórios. ... View more

Anyone who uses PowerBI long enough has had a PBIX with 50-60 measures and it has become time consuming and tedious to mantain. In Excel you can do a quick find/replace to edit several formulas - in PowerBI you need to select each one individually. An "excel-like" interface for editing measures would save a lot of time! This would take PowerBI to the next level regarding productivity. I've prepared a mockup for this as well as a DAX Editor. Let me know what you think. Mockup: https://i.imgur.com/z6TBOQb.png?1 ... View more

I think it would be nice to have locks at various heirarchies within Fabric to prevent accidental deletion for items that could be WORM (write once read many).  As a scenario, say you have an old system with historical data that you want to retire but still want the data for analytical use.  In this case you would write it to a Lakehouse, but you want to ensure that data is safe from as many risks as possible.  One of those being accidental deletion of a Lakehouse or files.   This way you can retire the old system to free up overhead, have the data available and not have a lot of concern about loosing it. ... View more