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との連携を実現いただけるよう、強く要請いたします。
Paginated Reports with PowerQuery - Cloud connections for Snowflake connector
Current situation: Power BI report builder used to build a report using Power Query dataset. Report builder picked the right cloud snowflake DB connection (created in Power BI service portal - app.powerbi.com) However, once we deployed / published the report into power bi service portal (workspace), we are not able to see the connection it uses in the background. We only see the disabled connection settings. Refer the screenshot. It would be great if we display the cloud connection information just like how we display for semantic models. Otherwise, we have to download the rdl file from the portal and check the connection ID from the report file and fetch the connection detail from the "Manage Connections and Gateways" page from the portal settings.
Allow multi-column conditions /output in Power BI Activator rules (Power BI visual-based alerts)
Description: When I create an Activator alert from a Power BI report visual, the rule can only evaluate the single column or measure it was created from, and the alert can only reference that same value. This blocks common governance and monitoring scenarios. Example scenario: I wanted an alert for Dev workspaces that sit on a billable (Premium/Fabric) capacity. That needs a condition on both Workspace Name (contains “Dev”) and Capacity/Billing type (not blank). Activator can’t combine the two in one rule, so I had to build the alert in Power Automate with a DAX query instead. Limitations: A condition can use only one column or measure, with no AND/OR across several attributes. The alert message or action can include only that same column. I can’t add related details like workspace name, dataset link, or owner. There’s no way to run a DAX query as the rule logic. Requested improvements: Conditions across multiple columns/measures (AND/OR). Selectable output fields, so the Teams or email action can include several columns, and dynamic links. Optionally, the ability to define the trigger with a DAX query, as the Power Automate “Run a query against a dataset” action does. Impact: Without this, governance and monitoring alerts need a separate Power Automate flow, which is harder to build and maintain than a native Activator rule.Fabric Workspace Operator Role for Pipeline Monitoring and Rerun Operations
Many organizations have dedicated production support and operations teams responsible for monitoring Microsoft Fabric pipelines and responding to failures. Currently, the available workspace roles are Admin, Member, Contributor, and Viewer. While Viewers can monitor content, they cannot rerun failed pipelines. Contributors can rerun pipelines, but they also have permissions to modify pipeline definitions and other workspace artifacts. This creates a governance gap for enterprises that require segregation of duties between development and operations teams. Proposed Solution Introduce a new built-in Operator workspace role with permissions such as: Allowed View pipeline definitions Monitor pipeline runs and run history View execution logs and error details Manually trigger pipeline execution Rerun failed pipeline runs Cancel running pipeline executions Access workspace monitoring capabilities Not Allowed Create, edit, or delete pipelines Create, edit, or delete Fabric artifacts Modify notebooks, lakehouses, warehouses, or dataflows Manage workspace access or permissions Change workspace settings Connect/disconnect Git repositories Business Value This role would: Support enterprise segregation of duties requirements. Enable production support teams to resolve operational issues without granting development permissions. Reduce the risk of accidental changes in production workspaces. Improve governance and compliance. Align Microsoft Fabric with operational models commonly used in enterprise data platforms. Many organizations need a role that sits between Viewer and Contributor, providing operational control without development privileges. An Operator role would significantly improve security, governance, and supportability for Fabric Data Factory workloads. Use Case: Production support team monitors Fabric pipelines, investigates failures, and reruns failed executions, but should not be able to modify pipeline definitions or other workspace assets.
More Granular Workspace Permissions (RBAC)
Allow Workspace Admins to assign more granular permissions and create custom roles based on atomic permissions, following the principle of least privilege. Examples of possible atomic permissions: Read workspace settings Manage workspace settings Read workspace role assignments Manage workspace role assignments Read OneLake security access role assignments Read workspace activity logs Read data Write data Share read data permissions Share write data permissions Create and edit workspace items Delete workspace items Share create and edit workspace items Share delete workspace items etc. This would enable Workspace Admins to automate auditing and governance, delegate specific responsibilities, and follow least-privilege principles without granting unnecessarily broad workspace roles.Disable App Sharing Notification to Audience
Can we have the option to turn off the notification when we add people to an audience in Power BI Apps? Sometimes, I want to share an app with a wider group of people, but I don't want to notify all of them. I just want to make sure they can access the app when they need to. We've been trying to get viewers in our organization out of workspaces, but we've been having to give viewer access to workspaces as a workaround when we are sharing with a large group.Overview of all Item permissions in a Workspace
We need a single page overview where we can see a complete list of which users and security groups have item permissions on any Item in the workspace. Today, we need to click on every single Item to see who has access to that item. We need a complete overview to easily spot if someone has a permission that they should not have.
Org apps - Cannot be arranged in folders and do not stay hidden
Currently, Organizational Apps (Org Apps) are displayed in the standard Apps section of the Get Apps experience, alongside regular workspace apps. For organizations managing large-scale Power BI deployments, this creates navigation and discoverability challenges. **Current Behavior:** Org Apps appear mixed with regular apps in a single list, making it difficult for end-users to distinguish and locate organizational-level content, especially in environments with dozens of apps. **Requested Behavior:** Add the ability to display Organizational Apps in a separate, dedicated section within the Get Apps experience (similar to how Featured and Recommended apps are organized separately). This would: - Improve discoverability for org-level content - Create clear visual separation between user-scoped and organization-scoped apps - Enhance the app navigation experience at scale **Business Impact:** Organizations deploying large numbers of apps (particularly during migrations and multi-tenant rollouts with 100+ apps) would benefit significantly from dedicated Org Apps visibility. This is especially valuable for external-facing platforms serving multiple client organizations, where organizational apps serve as the primary content distribution mechanism. **Suggested Implementation:** Add a new collapsible "Organizational Apps" section in the Get Apps experience that displays all Org Apps separately from regular workspace-published apps. Admins should have the option to control this visibility via tenant or workspace settings. **Workaround:** Currently unavailable.📉 How Would You Investigate a 20% Drop in Revenue?
A data analyst shouldn’t stop at identifying what happened. The real questions are: Where did the decline occur? → Why did it happen? → What caused it? → What should we do next? By analyzing regions, products, customers, time periods, and key business metrics, raw data can reveal the root cause behind the numbers. Good data analysis turns numbers into decisions. 📊 #DataAnalysis #BusinessIntelligence #PowerBI #MicrosoftFabric #DataAnalytics
