Currently, colors are automatically assigned randomly.  It would be nice if your dev workspace was always blue, and your prod was always pink for example.  Then you'd have a good visual as to where you're working in. ... View more

Imagine a world where report creators can automatically apply slicer and filter selections based on specific logic, revolutionizing data analysis and user experience. This innovative approach eliminates any need for complex workarounds, optimizes slicer functionality, and paves the way for more efficient and effective data reporting. ... 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

For the reports using Visualize your data quickly from Power Apps/ Dynamics 365 apps feature should be able change the visual type. ... View more

Many of our users think that when they select Relative Date: "In this year" - their YoY data will populate YTD vs Last YTD.  Small addition would make a huge impact on our business.  ... View more

Preview feature options are showing in local language set in laptop instead of showing the options in the language set in application level in Power BI desktop. This needs to be changed the preview features must be shown in language which is set by customer in Power BI desktop instead of considering the languag used in local machine. ... View more

We need support for Service Principal authentication when creating Lakehouse connections.   Right now, Lakehouse connections can only be created using a user account. As a result, Dataflow Gen2, Pipeline copy activity, and Copy Job cannot use a Service Principal (SPN) when connecting to a Fabric Lakehouse as a source or destination.   This is an issue for us. We want to avoid user-based connections because: We need environment-specific identities (dev/test/prod) to prevent accidental cross-environment writes (e.g., dev pushing data to prod). Tying connections to personal user accounts creates fragility - things break when someone leaves the project or the organization. Service Principal support for Lakehouse connections is required to ensure secure, reliable, and environment-isolated authentication.   The screenshot shows that only user authentication is available, not service principal authentication. ... View more

We would like to suggest a centralized usage metrics report that consolidates data across all workspaces. Currently, it's challenging to review workspace usage individually, as it requires checking each workspace one by one. A unified report would greatly simplify this process and improve efficiency. ... View more

Today, Power BI semantic models (datasets/DAX) work well when Power BI is the only BI tool. However, many organizations use Databricks as their lakehouse and need consistent, governed metrics across multiple BI tools, ML pipelines, and APIs. When the semantic layer lives only in Power BI: Logic is duplicated across datasets and tools Governance/security (RLS/CLS, masking) is fragmented Schema changes in Databricks break reports ML/AI pipelines cannot reuse business logic from Power BI models Proposal: Enable native Power BI integration with Databricks Metric View ... View more

As a large enterprise managing thousands of Power BI gateway connections across multiple clusters, we frequently encounter a significant operational challenge due to the current 1,000 connection limit per cluster. This limitation necessitates the manual recreation of data sources and rebinding of datasets when exceeding capacity, leading to a time-consuming and error-prone administrative process. We request a feature that enables Power BI administrators to seamlessly reassign existing data sources between gateway clusters. This functionality should be accessible via a user-friendly dropdown or bulk operation within the Power BI Service or Admin Center, eliminating the need to recreate connections from scratch on a new cluster. ... View more

Interpreting visuals without a clear legend to indicate logic behind specific styles can lead to confusion and decision-making errors. An idea to enhance clarity and transparency by ensuring legends and tooltips accurately display colors, patterns, and other visual components influenced by logics, would enable report consumers to easily understand the applied logic and make more effective decisions. ... View more

Currently, workspaces use a flat structure; adding folder metadata retrieval would allow automation for external storage replication (e.g., S3). ... View more

I would like to request the addition of a Kintone connector for Power BI. Kintone Official Website (US) Kintone Official Website (Japan)   By enabling seamless integration, we expect to unlock greator value from both platforms - leveraging Kintone's data capabilities and Power BI's powerful analytics and visualization features. In response to customer requests, we developed and provided a custom connector for Kintone. https://cybozu.dev/ja/id/90125c111898e77ad9a26618/ (Japanese only) ... 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

Hello Team, We would like to propose an enhancement to enable detailed tracking of semantic model usage. Specifically, we need the ability to capture, for each user: When they accessed a semantic model What activities or operations they performed Currently, we have options such as usage metrics for reports and the “View Report” activity, which allow us to retrieve logs for report-level interactions. We would like similar capabilities for semantic models, either through audit logs or APIs, so that organizations can maintain comprehensive tracking and governance of semantic model activities. ... View more

Description: Currently, Power BI automatically includes all fields used in the visual (Value, Target, Maximum, etc.) in the tooltip. This causes duplication when the same measure is used for multiple roles (e.g., Value and Target). Requested Feature: Allow users to independently select which fields appear in the tooltip, separate from those used in the visual. This would: Reduce redundancy in tooltips. Improve clarity and user experience. Give full control over tooltip content without requiring custom pages or DAX workarounds. Why it matters: Gauge visuals often use the same measure for multiple roles, and repeated values in tooltips look unprofessional. A simple toggle or separate field selection would solve this. ... View more

User want to set color for line graph in line and clustered column chart depending on X-Axis value.  Let's say if user visualizing sales, profit by months of particular year.  Setting profit in Line graph customer wants to make that the first 6-months period should be BLUE color(from January to June),  the other 6-months-period(July-December) should be RED color. Currently it is not possible to do in the Power BI.    ... View more

The Fabric Capacity Metrics App currently retains data (Item History, CU% over time, CU by workspace, etc.) only for the past one month, which limits long-term analysis. To effectively track optimization progress, capacity trends, and governance metrics, customers need access to historical consumption data over longer periods.   Instead of extending the built-in timeframe, the idea is to introduce a connector that exposes capacity metrics so customers can store and analyze historical data in their own storage units (e.g. Lakehouse, SQL DB or Data Warehouse). The connector doesn’t need to expose all data available in the Fabric Capacity Metrics App — it could simply provide key summarized metrics sufficient to deliver insights into capacity consumption trends over time across various factors.   This would enable organizations to create custom dashboards and reports for multi-month trend analysis, capacity forecasting, and optimization tracking, greatly improving administration and governance of Fabric capacities.   A similar approach to the Azure Cost Management connector, which enables users to extract and store cost data for custom and long-term analysis, would be highly valuable for Fabric Capacity Metrics as well. ... View more

Need a tool that can provide detailed information on which queries or DAX commands are being run by specific users, including the duration of each query, on their Power BI embedded capacity during times of CPU or capacity spikes. This will help us quickly identify the root cause of these spikes. ... View more