In Power BI, I would like to suggest adding an additional Format option to the Button / Action / Type drop down for "Show/Hide Group". This would allow creators to pick a Group that would then have its visibility toggled on or off whenever a user presses the button.   Here's a mock up of my idea to show how I imagine it would look added to the current Button / Action section:     Also as shown, if creators want a button to only show or only hide a visual (like an X to close), then the creator can set that functionality as well. (For bonus points, if one option is off and the creator tries to turn off the second one as well, Power BI automatically turns on the other option.)   I recommend designing this to only work for Groups as listing every element in a dashboard would make the drop down far too cluttered. (Maybe also divide up the list of Groups by page?) Creators can always place a visual inside its own Group if they wish to show/hide just that one element with a button.   This would drastically cut down on the number of bookmarks creators would need since pop-out panels, which would probably be the most common use for this, no longer need a show and hide bookmark. It'll also save creators from the painful process of having to update those bookmarks whenever something changes. (I always forget to swap out the show and the hide button.)   There's an additional security benefit too. Malicious users can use bookmarks to jump to pages they weren't meant to access if the creator forgets to uncheck "Current page" for that bookmark. (Currently, you can't disable the bookmarks list in Report Server.) This functionality would drastically reduce, and in some cases entirely eliminate, the number of bookmarks creators have to manage.   Hopefully people like my idea. Thanks for reading. ... View more

(General - Can you had a cropping function to get rid of the white space around visuals? Exactly the same as photo crop in Word, Excel and PowerPoint)   Can you add a manual drag option for Data Labels on Pie Charts? Essentially, allowing the user to drag and drop the Data Label to a better suited position and fixing it there? Also allowing stacking where you have the actual number and then the percentage underneath if desired to stop the ... from appearing.    Also, being able to increase the size of the Pie Chart either by circumference size (using a value) or by dragging the outer edge of the Pie Chart to the desired size.  ... View more

Introduce UAE-resident support for Microsoft Fabric Data Agent by enabling Azure OpenAI processing within UAE North, or provide a sovereign pattern/private preview that guarantees zero cross-geo data movement ... 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

Currently, when users export data from any Power BI visual (via the three-dot menu), the downloaded file is saved with a generic name like data.csv. We request a feature to dynamically assign a custom filename to exported data files. The custom name should ideally include context such as a date/time stamp and the values of currently applied report filters or slicers. This would eliminate the need for manual renaming after every export. ... View more

Currently, the Explore setting in Power BI (preview) can only be enabled or disabled at the tenant level, meaning it applies to the entire organization. Customers are requesting the ability to enable this feature for specific groups or subsets of users rather than globally. This would allow organizations to test and adopt the feature gradually without impacting all users, providing better governance and controlled rollout during the preview stage. ... View more

The Paginated Report visual currently hard-codes the workspace and report guid of the target report. This makes testing and promoting versions of reports withe visual difficult, as the target report does not change as the source report gets promoted. It would be very valuable to be able to make these items dynamic.   This could be implemented by doing the following: Add measure parameters on the visual for report and workspace name. Alternatively, add measure parameters on the visual for report and workspace guid. Developer would need to create the neccesary measures to be used.   ... View more

when a Power BI embed report remains idle overnight or for several hours,it takes some time to load the data which impacts user experience—especially for reports that need to stay open for monitoring purposes. ... View more

Need to implement a feature where guest user should access the semantic model in the Power BI desktop  which is helpful for the guest user who are part of the tenant by accepting the invitation which was sent by respective tenant administrator ... View more

Currently, with the new multiple scheduler feature, we can define multiple run schedules for a Fabric item. However, when using deployment pipelines, there’s no way to control which schedules are active in Dev, Test, or Prod. This means schedules intended only for Prod must also run in Dev, consuming unnecessary compute.   It would be very useful to allow using the Variable Library or deployment rules to set the active/inactive state of each schedule per environment, making deployments more efficient and flexible. ... View more

Currently, Power BI does not provide a way to change the owner of a Dataflow via the REST API. This limitation creates challenges in scenarios where ownership needs to be transferred due to organizational changes, role transitions, or automation requirements. Having the ability to programmatically change the owner of a Dataflow would improve governance, reduce manual intervention, and support enterprise-level management of Power BI assets.   Use Cases: Automating ownership transfer when users leave the organization or change roles. Assigning ownership to service accounts for better control and monitoring. Enabling centralized management of Dataflows in large environments.   Impact: This feature would enhance administrative flexibility and support better lifecycle management of Dataflows, especially in enterprise scenarios where automation and governance are critical. ... View more

Add options to the Power BI Controller that will control "Enable add-in Show as a saved image"  and “Show as a saved image”.  Reason: Snapshot ruins the image quality.  ... 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

We would like to implement a dedicated Fabric Copilot Capacity. But encountered an issue because the capacity (South Central) that we are using is in a different home region (West US). Fabric Copilot Capacity not available if capacity is on a different home region.   We had an issue (ticket number 2510170040000740) wherein the user used up all the capacity and it took 2 days for smoothing to happen. The capacity is not usable for 2 days and we have to move workspaces to a different capacity. This is the reason why we want to implement FCC.   It would be great if Fabric Copilot Capacity can be configured even if the home region is different from the capacity region.   ... View more

Please make it possible to use Managed Identity with Fabric items like Notebooks and Data Pipeline.   Benefits: No need to handle credentials. The item won't be related to a physical person. Then, we can give the Managed Identity access to read (and write to) data storage items in other Fabric workspaces, Azure SQL, ADLS, Dataverse, etc.   So that we don't need to rely on human users, and also don't need to handle credentials. ... View more

Please add a workspace-level toggle that allows the workspace admin to make all items read-only in the Fabric user interface.   With this setting enabled, items (such as notebooks, semantic models, dataflows, etc.) cannot be edited, created, or deleted manually via the UI. Instead, all changes must go through:   Deployment Pipelines Git API Ideal implementation: A toggle in the workspace settings (e.g. “Make items read-only in UI”).   Only workspace admins can enable/disable this setting. ... 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

As a developer I would like to be able to create a pull request to my connected repository branch from the Fabric workspace.  Imagine you have a DEV workspace connected to your main branch. Your development process is to create feature branches/workspaces for feature development and only changes via pull requests can be merged into your main branch. This leads to the situation that no changes in the DEV workspace can be merged into main branch because only commits are possible.  ... View more

RIght now, on powerbi.com, there is no ability to organize reports, dashboards, etc into folders. If you have a lot of content or users, this gets messy quickly. Please add the ability to organize into folders (and secure those folders separately) ... View more