The Problem: Currently, navigating and organizing report pages in Power BI Desktop becomes inefficient and frustrating when a report has many tabs. The small navigation arrows and the lack of standard keyboard shortcuts create significant "workflow friction" for power users compared to other Microsoft ecosystem tools like Excel. The Solution: I propose implementing a set of standard navigation and organization features to align Power BI Desktop with the Office 365 user experience: Tab Cycling via Keyboard: Enable Ctrl + Page Up / Page Down to switch between report pages sequentially. Tab Reordering via Keyboard: Implement Ctrl + Shift + Page Up / Page Down to move the active tab left or right in the sequence without needing to drag-and-drop. Quick Duplication: Enable Ctrl + Click and Drag on a page tab to instantly create a duplicate (cloned page) in the new position, just like in Excel or PowerPoint. Horizontal Scroll Support: Support Shift + Mouse Scroll over the tab bar to quickly navigate through the list of pages when they exceed the screen width. Why this matters: This is about Feature Parity. Most Power BI developers come from an Excel background. Standardizing these hotkeys and gestures would drastically reduce the learning curve and, more importantly, significantly increase development speed (DX - Developer Experience) for complex, multi-page reports. ... View more

The Problem: The current "Native Query" input window in database connectors (SQL Server, Azure Databricks, Snowflake, etc.) is a simple text box that offers a poor developer experience. It lacks basic modern code-editing features, forcing developers to constantly switch to external IDEs (like SSMS or VS Code) to write and debug queries. The Solution: I propose upgrading the SQL input field to a modern IntelliSense-enabled code editor, bringing it to the same standard as the DAX Query View, TMDL, and the Power Query Advanced Editor. Key Improvements Requested: Expandable UI & Full-Screen Mode: Resizable input box or a "Pop-out" option to handle long queries without excessive scrolling. Syntax Highlighting & Zoom: Color-coded support for SQL keywords, strings, and comments, plus Ctrl + Mouse Scroll for font scaling. IntelliSense & Auto-complete: Support for standard SQL functions and context-aware suggestions for table aliases/fields. Real-time Syntax Validation: Visual cues (red squiggles) for unclosed parentheses, trailing commas before FROM, or missing logical operators. Minimap Navigation: A high-level overview (minimap) on the right side of the editor for quick navigation in large scripts, consistent with the Power Query Advanced Editor. Advanced Search & Replace: Full support for Ctrl + F (Find) and Ctrl + H (Replace) within the query window. Smart Highlighting & Multi-cursor Editing: * Selecting a word should automatically highlight all other occurrences of that string. Support for Multi-occurrence selection (similar to Ctrl + F2 in Databricks/VS Code) to allow mass editing of aliases or field names simultaneously. Why this matters: This update would provide UI Consistency across the Fabric ecosystem. Power users rely heavily on Native Queries for performance and complex logic; providing a professional-grade editor inside the Connector UI would significantly reduce "workflow friction," minimize syntax errors, and increase development speed. ... View more

Today, Power BI Copilot is available only to users who are members of the workspace that hosts the report or semantic model. Users who consume content exclusively via Power BI Apps do not have access to Copilot, even when they have view permissions to the same reports and models. This is a significant limitation for large enterprises that deliberately use Power BI Apps as their primary consumption model. In these organizations, workspaces are restricted to development and analytics teams, while the majority of business users access content through centrally governed apps. As a result, Copilot adoption is effectively blocked for most end users, despite strong interest in conversational analytics (“ask questions about your data”) and existing investment in Fabric capacity and Copilot enablement. ... View more

When using a Copy Activity to generate a CSV file it would be very helpful to have a setting in the Destination tab, File Format settings list, to put items in the header row in quotes.  ... View more

It would be very helpful to have a way to throttle users in the capacity rather than a workspace. Giving user their own workspace is not an acceptable workaround. For example, if there are 500+ users but 3 are frequent problem users, and we have advised on best practices and re-trained them yet they still spike, we need a way to protect the 500 from being impacted by the 3. Taking away their access is unfortunately not an option and they are using the same models as the bulk audience. Once they make the naughty list, throttling them at the capacity level would be extremely helpful. ... View more

Hi all, I would like to submit a feature request regarding the Microsoft Fabric Eventstream REST API. Currently, it is possible to programmatically: Create an Eventstream Update its definition Configure an Eventhouse destination (including database and table mapping) However, there is a missing step that cannot be performed via API: After publishing the Eventstream topology, the final step "Configure KQL Data Connection" (available in the UI) is required to fully enable ingestion into the Eventhouse table. At the moment: This step is only available through the UI There is no documented or supported API to complete this configuration This creates a blocker for full automation and CI/CD scenarios   For teams working with Infrastructure as Code and automated deployments, the inability to configure the KQL Data Connection programmatically means: Eventstream deployments cannot be fully automated Manual intervention is required after each deployment CI/CD pipelines are incomplete Requested enhancement Provide an official and supported way to: Configure KQL Data Connection via REST API Or include this configuration within the Eventstream definition payload This could be implemented as: A new API endpoint for managing Eventhouse ingestion connections or Extending the Eventstream definition schema to include this configuration This capability would significantly improve automation scenarios and align Eventstream with other Fabric resources that already support full API-based deployment. Thanks for considering this request. ... View more

In Row level security add a search bar to search a user and see which roles are assigned.  Or add an export feature to export the roles and users to csv or excel file ... View more

  Product Area Power BI → Visualizations → Card (New Card Visual) Problem Statement In the new Card visual, the shadow applied at the visual container level and the shadow applied to individual card values (inside the visual) behave differently. Even when identical shadow settings (offset, blur, transparency, color) are configured, the rendered visual result is inconsistent. This results in: Mismatched shadow depth and softness Visual inconsistency within the same card visual Difficulty in maintaining a clean and uniform design across reports Card shadow settings:   In the above image we can see that there is a difference in main shadow and inside value's shadow even though we have used the same configuration for both the shadows:   Card shadow settings (inside value):     Main shadow's configuration:       Current Behavior The Visual → General → Effects → Shadow setting applies a shadow to the entire card visual container. The Visual → Cards / Callout / Reference Label → Shadow settings apply shadows to individual values inside the card. Despite configuring the same shadow properties in both places: The container shadow and value‑level shadow render differently Shadow intensity, spread, and blur do not visually match The result looks misaligned and inconsistent from a UI/UX perspective Request to Product team: Power BI should ensure consistent shadow rendering logic across: Card visual container (entire visual) Individual card elements (callout values, reference labels, multi‑card values) Specifically: Identical shadow settings should produce visually identical results Shadow depth, blur, and offset should follow a single rendering model Optionally, the value‑level shadow could inherit from the container shadow by default, with the ability to override if needed. ... View more

Feature request: Visual-level recalculation control As a Power BI user working with DirectQuery and heavy KPI calculations, I need an option to freeze or disable automatic recalculation of selected visuals, similar to how filter interactions can be disabled per visual. This would allow static KPI visuals (e.g. yearly totals) to avoid unnecessary recomputation, significantly improving performance and usability in DirectQuery scenarios. Informing the user, that re-calculation is disabled, we could just add a "banner" when hovering over the visual.  I know it sounds more easy than it is, but looking at data out of the past year, users wont expect re-calculation when ever we access. Is there something planned ? This would increase prerfomance on tables which need updates . thanks Karen ... View more

Today I got e-mail: C4C Quotes Analytics I do not know why I got this e-mail. I stopped working in C4C 6 years agon. The information is irrelevant to me.  Please find a way how to send e-mails only to relevant personel, and apply it.  Thank you. Michal ... View more

Hi. The subject pretty much says it all. It would be great if we could add some sort of conditional formatting to the cell colors of the timeline slicer. Thanks! ... View more

Please consider enabling Dataflow Gen2 to: Dynamically adjust schema mapping at runtime based on the resolved parameter value. Allow resource paths (such as Lakehouse table names) to be fully driven by public parameters from pipelines. Support end‑to‑end dynamic data ingestion patterns commonly used in modern data engineering. @https://learn.microsoft.com/en-us/fabric/data-factory/dataflow-parameters#considerations-and-limitations ... View more

When creating a report in the service using an Excel or CSV source, it's not possible to download the report, which is a known limitation. However, it would be helpful if a banner could pop up to notify users of this while creating the report directly from the service. ... View more

When building a semantic model that references another the workspace name is used in the connection path. When the workspace name changes the connection is broken and the path cannot be updated. Opening in power bi desktop there is no source query to edit. Request that the semantic model editor use the workspace GUID to build the connection string. ... View more

Currently, it is only possible to add individual users for notifications—unfortunately, groups (e.g., Entra ID / AD groups) cannot be selected. This isn't ideal for us, since users change frequently, and managing individual users is time-consuming and prone to errors. Using groups would be a much lower-maintenance and more sustainable solution. ... View more

We would like Microsoft Fabric to support Spark write operations to Fabric Warehouse when Private Link is enabled, ideally including full read/write support under both tenant-level and workspace-level Private Link configurations. Background In our scenario, we need to perform multiple transformation steps with PySpark directly against Warehouse tables. At the moment, with Private Link enabled, this is not possible due to the documented product limitation. Current Challenge The currently possible workaround is a repeated flow like: PySpark → Lakehouse → Warehouse → PySpark → Lakehouse → Warehouse → Power BI This creates significant operational overhead, including: additional data movement between engines more complex orchestration and pipeline maintenance increased runtime and storage duplication more potential failure points reduced architectural simplicity and efficiency Why this matters For enterprise environments, Private Link is often a mandatory security requirement. At the same time, organizations want to use PySpark as a central transformation engine while still leveraging the Warehouse as the serving layer for analytics and reporting. Without direct Spark-to-Warehouse write support under Private Link, teams must choose between: a secure network architecture, or an efficient and streamlined data transformation process This is a major limitation for production-grade enterprise data platforms. ... View more

The AI-generated summary in Power BI report subscriptions is a very valuable feature and often provides useful insights from the report data. However, the generated content is fully determined by the AI, with no option for users to guide the structure or priorities of the analysis. This sometimes results in important business information being omitted or the narrative format changing between subscription emails. A potential improvement would be to introduce an optional Custom Prompt field in the subscription configuration. This field would allow users to provide instructions or guidelines for the AI-generated summary, such as: key metrics that must always be mentioned preferred analysis structure or narrative format tone of communication (executive summary, operational insight, etc.) priority comparisons or time periods Additionally, allowing users to preview the generated AI summary before sending the subscription would help ensure consistency and alignment with internal reporting standards. This enhancement would improve consistency, governance, and trust in AI-generated insights, while still keeping the automation benefits of the current feature. ... View more

The Issue When the contact (owner) of a Power BI Report is changed, the API response begins returning two user entries in the users array, where both users are reported with the same Owner access right. There is currently no distinguishing field in the API response that indicates: - Which user is the current/active owner - Which user is the previous/former owner This creates an ambiguity in our metadata catalog — we are unable to accurately attribute ownership and governance accountability to the correct individual. Sample API response (simplified): "users": [   {     "displayName": "User A",     "emailAddress": "usera@company.com",     "appUserAccessRight": "Owner",     "principalType": "User"   },   {     "displayName": "User B",     "emailAddress": "userb@company.com",     "appUserAccessRight": "Owner",     "principalType": "User"   } ] Both entries appear identical in terms of access right, with no timestamp or status field to differentiate them. What We Need  We would need help with one of the following: 1. Whether there is an existing field or flag in the API response that can distinguish the current owner from a previous one (that we may be missing) 2. If no such field exists, whether Microsoft can add a discriminating attribute (e.g., a isPrimaryOwner flag, an assignedDate timestamp, or a status field) in a future API update 3. Alternatively, if there is a separate API endpoint that returns the definitive current owner of a Report --- ... View more

 BI Concept Note ## Intouch & EDI High‑Value Sales Order Monitoring ### Purpose Introduce a BI‑driven monitoring and alerting capability for Intouch and EDI sales orders to identify high‑value transactions (> €5,000) and enable timely, data‑driven sales and customer engagement actions. --- ### Business Problem High‑value orders currently enter the system without structured, proactive follow‑up. This results in: • Missed opportunities for customer appreciation • Limited insight into exceptional or irregular buying behavior • Underutilized cross‑sell and upsell potential --- ### BI Solution Overview A centralized BI solution that: • Detects high‑value sales orders in near real time • Enriches orders with customer and historical context • Triggers notifications to relevant business stakeholders • Provides dashboards for monitoring and performance tracking --- ### Scope & Trigger Logic • Trigger condition: - Sales order total value > €5,000 • Channels: - Intouch - EDI • Threshold configurable via BI parameters --- ### Data Inputs • Sales order data (Intouch, EDI) • Customer master data (new vs existing customer) • Historical order data (frequency, average order value) • Product / category data (where available) --- ### Data Enrichment & Indicators For each triggered order: • New vs existing customer • Regular vs exceptional order (based on history) • Order value vs customer average • Channel and Business Unit mapping --- ### Alerts & Consumption • Automated notifications to: - Sales BU - Account owner / sales rep • Notification content: - Customer details - Order value and channel - Key indicators (new customer, irregular pattern) • Delivery via email or collaboration tools (e.g. Teams) --- ### Analytics & KPIs • Number of high‑value orders by BU and channel • New vs existing customers for >€5K orders • Follow‑up SLA compliance • Cross‑sell / upsell outcomes (future phase) --- ### Business Value • Improves proactive customer engagement • Supports sales prioritization based on impact • Enables cross‑sell and upsell at the right moment • Positions BI as an event‑driven decision enabler, not just a reporting function --- ### Next Steps 1. Validate data availability and latency 2. Align on business rules and thresholds 3. Define alert ownership and follow‑up process 4. Deliver MVP (alert + basic dashboard) --- Kind Regards  Cemal Ozturk ... View more