What is the idea? Add a comprehensive spell-check functionality in Power BI / Microsoft Fabric reports that covers all text elements — including visual titles, axis names, column and measure names, legend labels, page tabs, tooltips, and any other text fields — not only text boxes. Why is this important? It enhances professionalism and credibility in reports shared with stakeholders. It ensures consistency and prevents misunderstandings caused by small spelling mistakes. It saves time: authors currently must manually review all text or rely on external tools. It improves accessibility, localization, and inclusiveness. It aligns Power BI with modern expectations for enterprise tools, as Word, Excel, and PowerPoint already include full spell-check support. Real-world example / Use-case: I live in Austria for five years now and work for a Business Intelligence consultancy where many dashboards are created in German. Many of our developers, however, are foreigners who are not native German speakers. As a result, misspellings often slip into production dashboards, especially when testing teams overlook minor linguistic details. A native spell-check system would prevent these errors and significantly improve report quality and consistency across multilingual teams — a situation shared by many BI professionals worldwide.   What should it include? Red underlining and suggestions for misspelt words in all editable text fields. A configurable dictionary (supporting multiple languages and domain-specific terms). Options to enable or disable spell check per report or per element. A “Review Spelling” mode to scan the entire report for inconsistencies. Impact A global spell-check feature would directly enhance report quality, consistency, and trust, saving hours of manual proofreading for Power BI creators and teams across all industries and languages.   PS: This Text was revised and enhanced using Artificial Intelligence. ... View more

Currently when using the selection 'Recent Runs' on a pipeline we can only see Activity Name, Start time, Submitter and Status. Can we have more information available for comparision such as all the columns we can add in the monitor view.  We are looking to compare start, end times and duration see if the runs times are changing in duration over time.   ... View more

Currently python notebooks are subject to the same limits as spark notebooks Concurrency limits and queueing in Apache Spark for Fabric - Microsoft Fabric | Microsoft Learn   From my experiance this means that on an F2 you can not run more than 4 notebook sessions at once via a pipeline. This limit is fine for spark given the higher node size floor meaning that four sessions will likley consume 100% of an F2. However, as python notebooks run by default with 2 vCores you can run far more sessions at once for the same capacity. This limits how many jobs can run at once increasing ETL durations.   Ideally the queue limit for python notebooks should be double the spark notebook queue. E.g. 8 on an F2, or this could be a blended limit, e.g 2 spark notebooks and 4 python notebooks. ... View more

Highlight the components that are selected for each bookmark.  ... View more

PowerPoint has this functionality, PowerBI should too! ... View more

Slicer de Data "Between" com Padrão Dinâmico para Mês Atual Gostaria de expressar uma dificuldade notada por vários usuários, impactando a facilidade de uso dos relatórios: a falta de um segmentador de data "Entre" com valor padrão dinâmico para o mês atual quando o relatório abre, mas que permita ao usuário alterar o período livremente.   Hoje, recorremos a soluções alternativas que, mesmo engenhosas, são apenas provisórias e nunca oferecem a experiência ideal:   Bookmarks Estáticos: Um marcador para 'Mês Atual' até tem sua utilidade quando queremos visualizar mes fechado. Mas para o dia a dia, para o nosso slicer 'Entre' que precisa mostrar o mês corrente e permitir uma seleção flexível, ele é um problema. E se tentamos configurá-lo para ser 'dinâmico', ele acaba engessando a seleção livre de datas específicas, como um dia único. E se nao estiver selecionado sempre ira mostrar no slicer o ultimo periodo salvo o que causa confusão visual.   Filtros de Data Relativa: Opções como 'Este Mês' ou 'Últimos X Dias' limitam e eliminam a necessidade crucial de um filtro 'Entre' para o usuário escolher datas específicas, como '01/01/2023 a 15/01/2023' ou '10/02/2024 a 20/02/2024'.   Medidas DAX e Filtros de Página: Filtram o mês atual, mas impedem o usuário de explorar outros períodos sem desativar o filtro, ou não definem o estado inicial do segmentador de forma interativa.   O ideal seria que, ao abrir o relatório, o usuário veja os dados do mês atual (e o segmentador 'Entre' já configurado para esse mês: por exemplo, de 01/MM/AAAA a 30/MM/AAAA). No entanto, ele precisa poder arrastar os seletores do segmentador para qualquer período 'Entre' que desejar, sem precisar 'Resetar' ou 'Ver Mês Atual' ...   Ferramentas de BI menores e recentes oferecem essa funcionalidade nativamente. É frustrante que o Power BI não tenha uma solução pratica e objetiva para algo básico e impactante na experiência do usuário. Acredito que este recurso aumentaria a usabilidade, economizando tempo de desenvolvimento e oferecendo uma experiência mais fluida e intuitiva para o usuário final dos relatórios. ... View more

Please allow me to zoom in and out when I'm editing the mobile layout! ... View more

Allow all formatting tools to be used on both desktop & mobile layouts - this includes layer order, align & distribute. Additional items (text boxes, for example), should also be allowed to be added in the mobile layout editor. ... View more

Power BI theme files are great for controlling a lot of properties of visuals. However, there are quite a few bugs and limitations. I think at least all properties of all standard visuals should be controllable by the theme. Unfortunately, this is not the case. Microsoft should definitely fix this. At the moment these issues make it almost impossible to create a nicely and properly working theme file which can be adopted by the entire organization.   A few clear and easy examples: - Font sizes for slicer headers can only be affected by changing the global font size for titles... I mean, who would have guessed that. I consider this being a bug. - Font sizes for category lables cannot be controlled by the theme at all. - Text wrapping cannot be set by the theme. - Style presets and layouts cannot be set by the theme. - Etc.   A lot of these properties can be defined in the theme file and Power BI will import the file but they don't seem to have any effect on the visuals (even after choosing "Reset all settings to default").   Please fix this Microsoft Power BI Team!   Please note: We are working with the 64bit September 2025 version of Power BI so may be some issues have been fixed already. ... View more

Currently, the "Update App" feature in Power BI overwrites the entire application content, requiring you to re-arrange the navigation, report order, and sections every time you add a new report. In other apps, "update" means a minor change, not a complete re-creation of the structure. In Power BI, it's more like "create from scratch." Suggested improvements: 1. Preserving the existing navigation structure when updating the app. 2. Ability to add a new report without having to re-arrange everything. 3. Warning that the update will overwrite the application structure. Such changes would significantly simplify the work of Power BI administrators and users. ... View more

Please consider adding a native Box & Whisker plot to Power BI with full customization options. This includes editable whiskers, quartiles, and outlier settings, ideal for statistical and industrial data analysis. ... View more

It would be extremely helpful to allow users to define fixed unit intervals (e.g., every 5, 10, 100) on both axis in line and column charts. This would improve readability and precision, especially in dashboards used for monitoring KPIs and production metrics. ... View more

Idea Summary In Power BI / Fabric workspaces, managing semantic models becomes challenging when there are many models and reports — especially after some reports (Power BI or paginated) are deleted or unpublished. Currently, there’s no quick way to identify which semantic models are still in use and which are orphaned. Problem While the Item Lineage view allows us to see dependencies, manually opening the lineage for each model is time-consuming and repetitive. When numerous reports and models exist in a workspace, this becomes inefficient and error-prone. After removing unused reports, many semantic models remain with no dependents, and confirming this requires checking them one by one. Proposed Solution Add a “Dependency Count” column for semantic models in the workspace view. This column would display the number of dependent items (e.g., reports, paginated reports, datasets, dataflows) connected to each model. Example: Name Type Dependency Count Git Status Refreshed Included in App Analysis of Sales Semantic Model 2 Synced 10/14/2025 — Average Accumulated Cost Semantic Model 0 Synced 10/14/2025 — Benefits Simplified workspace cleanup: Quickly identify unused semantic models that can be safely deleted. Improved governance: Prevent clutter and optimize storage by keeping only active models. Enhanced visibility: View dependency information directly in the workspace list without navigating to the lineage view. Better efficiency: Reduces repetitive manual checks, saving time for workspace administrators and developers. Optional Enhancements Clicking the dependency count could open a small popup listing dependent items with direct links. Enable sorting and filtering by dependency count (e.g., show only models with 0 dependents).   ... View more

Monitor Page -  Add an upcoming tasks option in Monitoring with options like skip refresh so we can plan ahead instead of looking at current / history of refreshes  This can help in optimizing the Fabric capacity during working hours ... View more

Hello Team, We have noticed that when the app is updated with new content, users cannot see the changes unless they open the URL and refresh their browser. This affects the user experience. We request that the app be changed to automatically display the new content when the user opens the app via the URL. We hope this change can be implemented soon to help prevent customer dissatisfaction with the product. ... View more

To reduce administrative burden in telephony systems due to requirements for VQs to be built to report out on unique business requirements, a filter should be added to the OmniChannel Reporting that will allow us to filter by group id when a member authenticates. Queue Summary Report Adjusted SL Daily KVPs - Power BI ... View more

When dataflows run into errors and Microsoft Support is involved, the feedback is always the same. Resumed: "we need logs to do any investigation. We don't collect anything ourselves, so your only option is to use your browser developer tools to record a run".  This is frustrating and quite limited when considering that:  Some issues are intermittent and only/mostly happening on scheduled dataflows (sometimes in the middle of the night) Some issues are related to internal connections not transiting via the browser (e.g. connection issues between a dataflow and the underlying staging lakehouse) which will never be captured via browser logs.    Please enable some background logging for dataflows to enable better support for issues here.  ... View more