Revival of report hiding feature in New App UI
The previous App UI, we can hide report pages in app settings, and we can use cross report drill-through with the target reports hidden. This was a great way to build a simple app. But in contrast to the previous APP UI, the new UI cannot hide the target report (there is only feature which grants the user access to) So the distributor must locate the target report so that it is visible, and this can be a complex and confusing part of the app building for the user. We would like you to release the feature in the new App UI which hides the report itself from navigation pane, while still having access to the report.
Allow hiding non-functional JSON file links in Fabric Data Agent responses
**Description** Fabric Data Agent automatically displays generated JSON file references (e.g., `result_4.json`) alongside query results, even when the user asks a simple question that returns a single value. These references appear as clickable links but do not actually open or download a file. This creates unnecessary clutter and confusion for business users, who may assume that the file contains additional information or that something is broken. **Suggested improvement** - Provide an option to disable automatic file references in Data Agent responses. - Alternatively, hide file references unless the user explicitly requests a downloadable file. - Only display download links when the file can actually be accessed or downloaded. **Business impact** Fabric Data Agents are intended to make data accessible to non-technical business users through natural-language questions. Displaying non-functional technical file references in every response reduces the clarity and professionalism of the experience, particularly when the answer is a simple KPI. For production deployments, administrators should be able to control whether these technical artifacts are visible to end users.
Auto Y axis labels and gridlines to be above max value
The operation of the auto y axis labels and gridlines frequently results in charts where the max value is above the maximum visible y axis value. For eg. line charts like the below, where much of the top line is above the auto selected max y axis value of 8,000. I am aware that we can create DAX expressions to solve this issue, but in this case we have charts where there are a number of dimensions that the user can move between, all of which result in different values in the charts - which means many additional DAX expressions, just to ensure the y axis behaves in a reasonable way. It would be great if the auto y axis naturally ensured values were below the max.
Group/Collapse Filters in Filter pane
For larger reports/dashboards with unwieldly number of Filters in the pane it would be helpful to allow add/edit for a "Group" or Folder that could collapse/expand filters within to supplement the search facility when browsing for filters. At the moment the only "grouping" that really exists are filters on this visual OR filters on the page or filters on all pages.. around 10 filters are ok but what about 30 or 40 filters?Dynamic current-period defaults for separate Year and Month slicers
Scenario The target scenario is a report viewed in Power BI Service, using a DirectQuery semantic model and a dedicated Date dimension. Separate Year and Month slicers are part of the required user experience. Requested behavior Automatically select the current calendar year and month at the start of every new report visit. Allow readers to select historical years and months using the same separate slicers during that visit. Reset to the current period on the next visit, rather than restoring a previous historical selection. Roll forward automatically at month and year boundaries, without manual monthly updates, changes to static bookmarks, or report republishing. Example When opened in October 2026, the report should start with Year = 2026 and Month = October. A reader can then select March 2025 for historical analysis. On the next visit, the report should again start at the current period. When November arrives, the defaults should automatically become November 2026. At the year boundary, they should become January 2027 without author intervention. Why the alternatives do not meet this scenario A relative date slicer supports a rolling period but replaces the required separate Year and Month controls with a different experience. Static bookmarks or saved categorical selections require calendar maintenance. Filtering the report to show only the current period would prevent the historical analysis that must remain available. Business value Most viewers in this scenario need current-month and current-year data first, while still needing flexibility to explore history. Dynamic defaults would reduce repetitive manual selections and ongoing report maintenance while preserving the existing navigation experience.Conditional Formatting on Matrix Rows
Currently, the matrix visual only supports conditional formatting on a per-field basis. If you want to apply the same formatting for an entire row of values you need to set it once for each field, and then the calculation runs once for each field, resulting in the same calc running many times over and greatly impacting load performance of the visual. If instead the row-level Values settings had conditional formatting, the condition could be run once and apply to all cells in each row. See terrible mockup for example of my meaning:
Fabric / Power BI Copilot と PowerPoint Copilot の連携強化
Fabric / Power BI Copilot と PowerPoint Copilot の連携強化について、CATチームおよびプロダクトチームで真剣に検討いただきたく、要請としてお伝えします。 【背景】Microsoft Fabric / Power BI を活用し、顧客の経営データ(顧客単体データ+複数顧客の統合DBによる立ち位置比較)を分析しています。目的は「BIの閲覧」にとどまらず、経営コンサルティング提案(顧客向けPowerPoint+グラフ)を継続的に行うことです。しかし現状の Fabric / Power BI 側の Copilot は、レポート内のQ&Aや要約に留まっており、提案資料レベルまでつながるワークフローが存在しません。 【現状の課題】 1.提案は最終的に PowerPoint+グラフが必須実際の顧客提案(報告・改善提案)は、必ず PowerPoint 形式の資料とグラフが必要です。Fabric 側の Copilot は Power BI レポート内での分析・要約はできますが、PPTXテンプレートグラフに沿ってグラフ付きの提案資料を自動生成することはできません。 2. BI の中だけで完結することは現実的ではない顧客ごとに毎回状況が変わるため、そのたびに Power BI のモデルやレポートを作り替えながら提案するのは運用コストが高すぎます。コンサルタントの実務では「Power BI で分析 → PowerPoint でストーリー化 → 顧客面談」がワンセットであり、BI だけで閉じた世界では提案として成立しません。 3. Fabric の Copilot と PowerPoint Copilot の分断PowerPoint の Copilot は PPTX テンプレートを読み込み、スライドマスターに沿った資料生成が可能です。一方で Fabric 側の Copilot は BI レポートの構造を理解しているにもかかわらず、PowerPoint(提案アウトプット)側と連携できていません。結果として「Fabric の AI は分析の途中で止まり、提案にはほとんど役に立たない」という印象になってしまいます。 【要請内容】ゴール:Power BI / Fabric 上の分析結果を、PPTX テンプレート+グラフ付きの提案資料に半自動で落とし込めること。 具体的には以下の機能を強く要請します。 (1) Power BI レポート → PowerPoint 提案資料 までをつないだシナリオ強み・弱み・提案事項などの分析結果を整理し、「顧客 vs 統合DB(複数顧客)平均」の率ベース比較グラフ+解説付きで、PPTX テンプレートに自動配置するような一連の機能が必要です。 (2) Fabric 側 Copilot から PowerPoint Copilot へのブリッジ機能Fabric の Copilot 上で「このレポートとこのテンプレートを使って、顧客提案用のスライドを作成してほしい」と指示を出すと、裏側で PowerPoint Copilot と連携し、指定した指標のグラフと対応するテキストを PPTX として生成する、そのようなブリッジ機能の実装を要請します。【なぜ「要望」ではなく「要請」に近いのか】複数の経営支援を実施している企業にとって、「分析結果をどう説明し、どのような行動を促すか」が重要であり、BI 画面を見せるだけではコンサルとして成立しません。現場では毎回、Power BI から数字を読み取り直し、PowerPoint で手作業でグラフと文章を作るという重い作業を強いられています。Fabric / Power BI を「経営の標準的なプラットフォーム」として広げていくためには、提案資料まで一気通貫で支援するシナリオが不可欠です。すでに PowerPoint では Copilot による優れた資料作成が実現されています。ぜひ Fabric / Power BI Copilotとの連携を実現いただけるよう、強く要請いたします。
CoPilot for Power BI improvements
With the advent of AI - it's becoming a lot easier to visualize data by quickly generating HTML pages using CoPilot, than it is to do this using Power BI. It is time to stop insisting on the Workspace being included in a Fabric Capacity, to enable use of CoPilot in power BI. Even when the workspace is in a Fabric capacity - the CoPilot agent can't "see" any of the data - only the schema - so it's a lot less useful than it really should be. Even people who love Power BI are starting to code up web pages instead for near-instant visualizations - MS needs to make CoPilot more useful for Power BI Report Builders - and FAST. Suggest: For Power BI Workspaces: Let CoPilot in Power BI Work - with visibility limited to Schemas only. For Fabric Workspaces/Semantic Models: Make CoPilot in Power BI talk to the Fabric Data Agents by default, to ensure it can actually see the data as well. (It's also time to give Report Reader rights at something smaller than the F64 Capacity).
Visual filters should apply before cardinality limits on charts
When a visual-level filter (including Top N rank filters) is applied to a high-cardinality legend field, Power BI hits the cardinality limit before evaluating the filter, causing alphabetical truncation instead of the expected filtered results. The filter should reduce the legend first, then apply the cardinality limit.
