In the Matrix visual, I would like to be able to apply formatting without using DAX or conditional formatting to the following types of cell intersections: - Intersection of a Subtotal Row and a Subtotal Column - Intersection of a Grand Total Row and a Subtotal Column - Intersection of a Subtotal Row and a Grand Total Column - Intersection of a Grand Total Row and a Grand Total Column   These cells often represent the most important summary values (such as team-level totals within overall totals), but currently they cannot be formatted separately unless complex DAX or conditional formatting is used.   Request: Please provide built-in, no-code formatting options (e.g. background color, font color, bold, etc.) specifically for subtotal rows, subtotal columns, grand total rows, grand total columns, and their intersection cells. This would significantly improve the readability and usability of Matrix visuals for reporting and management scenarios. ... View more

Currently when using the Onelake Governance screen only Fabric Admin can see the scope of Onelake artifacts outside of their ownership If you are not a Fabric Admin you can only see "My Items" I request that another scope be added so that you can see the governance of all Onelake artifacts in workspaces you have admin rights in.   ... View more

I would like to suggest enhancing the conditional formatting icon options by adding: More color variations for existing shapes Example: circular icons in blue, orange, and other colors Currently, color options are limited and do not fully support common status schemes (e.g., blue = informational, orange = warning) Hex color customization for icons Allow users to define icon colors using custom HEX codes This would enable alignment with company branding and dashboards More flexible icon design options Ability to mix icon shapes and colors (e.g., circle with custom color) Not limited to predefined sets Use Case: In dashboards, different statuses (Ahead, On Time, Slight Delay, Moderate Delay, Critical Delay) require distinct visual indicators. Current icon sets are restrictive and limit clarity and consistency in reporting. This enhancement would significantly improve data visualization and user experience ... View more

Currently buttons do not support MailTo, so we have to use hack workarounds. Please support *all* valid URIs, per the specs, in all places we can put hyperlinks: https://datatracker.ietf.org/doc/html/rfc3986 ... View more

Notebooks have builtin resources, which is helpful, but some code assets are used across multiple notebooks. Provide a central code repo per tenant that is git enabled. ... View more

Hi,   We would like to collect run history logs using the Job Scheduler API.   It would be very helpful if the response included the workspaceId. This would allow us to store the raw JSON response as-is in our Lakehouse while still being able to identify which workspace each item belongs to.   Without the workspaceId in the response, we need to maintain an external mapping between items and workspaces, which adds unnecessary complexity and potential for inconsistency.   Including the workspaceId would make the response self-contained and easier to manage in downstream ingestion and auditing scenarios.   Current response sample:   {   "id": "f2d65699-dd22-4889-980c-15226deb0e1b",   "itemId": "431e8d7b-4a95-4c02-8ccd-6faef5ba1bd7",   "jobType": "DefaultJob",   "invokeType": "Manual",   "status": "Completed",   "rootActivityId": "8c2ee553-53a4-7edb-1042-0d8189a9e0ca",   "startTimeUtc": "2023-04-22T06:35:00.7812154",   "endTimeUtc": "2023-04-22T06:35:00.8033333",   "failureReason": null } ... View more

I would like the ability to add a dynamic input box  on a spark job definition's "Main Definition File" "ADLS-Gen2 path". this would be useful to set base and variable paths across all spark jobs. and have them set in a library folder so if I have 50 definitions, and  instead of making a change to all 50 files i can just make a single change on the variable. and it would be consistent across workspaces on other environments.  ... View more

Product: Fabric IQ Plan (preview); PowerTable sheets Context: Built a complete EPM proof-of-concept for budget planning global offices: Fabric SQL Database (star schema with fact + dimension tables) > Direct Lake semantic model > Plan item with PowerTable and Planning sheets. Grid editing of existing records with Reference Columns works perfectly, write-back, audit trail, and approval hooks all validated. The gap: When creating new records, Reference Columns do not support dropdown/lookup selection: Insert Row in the grid: clicking a Reference Column cell returns "This column is restricted for editing" Forms: Reference Column fields render as plain number inputs ("Enter a number") with no dropdown or search capability Users cannot select valid dimension values (e.g. pick "US" from a country list). They would need to know internal integer foreign keys, which is not viable for production. Expected behaviour: Reference Columns should render as searchable dropdown selectors when inserting new rows, both in grid view and in Forms. The user picks a display value; the system resolves to the correct FK integer on save. Impact: This blocks the primary use case Plan is designed for — governed budget/forecast data entry by non-technical business users. Without dropdown support on new records, organisations cannot replace Excel-based planning workbooks with Plan. Workaround: None within Plan. External tools (Power Apps) can write to the same SQL table with proper dropdowns, but this defeats the purpose of a unified planning platform. @ ... View more

Add visual-level option to preserve scroll position (e.g., Keep scroll position on right) In Power BI (Fabric / Service), visuals that require horizontal or vertical scrolling currently reset their scroll offset to the default origin (left/top) every time a report is rendered. This occurs regardless of the scroll position at save time and cannot be controlled by report authors. As a result: Initial render frequently hides the most relevant data (e.g., latest periods in time-series visuals positioned at the far right) Users must manually scroll on every load or refresh Report authors rely on non-semantic workarounds (sorting, filtering, duplicate visuals) that alter visual meaning or increase maintenance overhead There is no visual-level or page-level API or formatting property to define or preserve the initial scroll position during the render lifecycle. Proposed Enhancement Introduce a visual-level formatting property that allows authors to explicitly define the initial scroll offset when a report page is rendered. Suggested configuration (Format pane → General / Advanced): InitialScrollPosition Auto (default – existing behavior) Start (left / top) End (right / bottom) PreserveLastSaved This property would be evaluated during: Initial report load Page navigation Visual re-render triggered by filter/context changes Expected Behavior When configured: The visual’s scroll container initializes at the configured offset without user interaction Behavior is deterministic and consistent across: Power BI Service Microsoft Fabric Power BI Apps Embedded scenarios The setting does not alter data semantics, sorting, or filtering logic Existing reports retain current behavior unless explicitly enabled Justification / Engineering Rationale Scroll offset is a presentation concern, not a data concern, and should be configurable independently of model logic Lack of control forces report authors to encode UX intent into data transformations, which is brittle and semantically incorrect Similar lifecycle control already exists for: Page state Filters Bookmarks (manual only) Visual layout and sizing This enhancement would close a functional gap at the visualization rendering layer. Common Scenarios Time-axis visuals where the most recent data appears at the end of the categorical or continuous axis Operational dashboards with daily/weekly monitoring patterns Executive reports where first render must surface “current state” without user guidance Large categorical visuals where scrolling is unavoidable Summary Providing a visual-level mechanism to control initial scroll position would significantly improve UX consistency, reduce report complexity, and align Power BI visual behavior with modern dashboard expectations—without impacting backward compatibility or data logic. ... View more

Hi everyone, I’m working on designing a bot experience in Microsoft Teams that allows users to query report data using natural language. Below is the intended behavior — I’d appreciate feedback or suggestions on improving this approach. Core Behavior 1. Teams Integration The bot is available within Microsoft Teams. 2. Personalized Greeting When a user opens the bot, it greets them based on: Time of day (e.g., Good Morning / Afternoon / Evening) Their Microsoft Entra ID display name 3. Natural Language Query Users can ask questions in plain English, for example: “Get the count of studies which are Phase 1” 4. Intelligent Report Identification The bot should: Respect user access Only consider reports the user has access to Example: TRIP, RDDC, Connect, PRISSM Understand user intent (semantic matching) Identify key entities/attributes from the query Example: Query: “Get the count of studies which are Phase 1” Key concepts: Studies, Phase 1 Map query to relevant reports Determine which reports contain the required data Example: Relevant reports: TRIP, RDDC Prompt user for report selection Respond with something like: “I found relevant data in the following reports. Please select one to proceed.” Require the user to select exactly one report Note: The bot should infer intent even when exact attribute or column names are not used — similar to how Power BI Copilot interprets queries. 5. Query Execution Once the user selects a report: The bot answers the question using only that report’s semantic model Ensures accuracy and avoids cross-report ambiguity Goal To create a Copilot-like experience within Teams that: Understands natural language queries Respects user-specific data access Guides users to the correct data source Provides accurate, context-aware responses ... View more

Real-Time Operation Agent Using Workspace Monitoring: Enhance with L2 Activity Data for Pipelines ... View more

The API endpoint described in https://learn.microsoft.com/en-us/rest/api/power-bi/admin/reports-get-reports-as-admin is missing a few fields. A few are Contact list and Endorsement level. These should be made available to the API, because currently the API is very incomplete. ... View more

Currently the only method of authentication in Fabric pipeline connections to Fabric SQL databases is using OAUTH2, meaning that the credentials of a specific user need to be used (with all the attendant issues around user/credential expiry). By allowing the option of workspace identity for authentication, no user creds would be needed.  Obviously correct access controls would need to be defined, but that's standard SQL Server maintenance. ... View more

Come on man, keyboard shortcuts still aren't available in PBI, why not and when is it going to happen?????? ... View more

On the Microsoft 365 Usage Analytics Template app, on the Activation/Licensing page there is a table at the bottom called "Users Assigned a Subscription" There used to be columns to the right of Assigned count, which brokedown the Assigned count per month.     This is a request to reinstate these columns.   ... View more

DAX development in Power BI is inherently complex due to its dependency on evaluation context (row context, filter context), relationships, and data modeling structure. While experienced users can write optimized measures, a large portion of users struggle with translating business requirements into correct and performant DAX expressions. I propose a context-aware AI DAX engine embedded within the formula bar that goes beyond simple text-based suggestions. This system should leverage the underlying semantic model (tables, relationships, column data types, hierarchies, and measures) to generate accurate, optimized, and contextually valid DAX expressions. Unlike generic AI suggestions, this feature should: Understand data model relationships automatically Detect active/inactive relationships Interpret filter propagation and evaluation context Recommend best-practice DAX patterns (e.g., CALCULATE optimization, use of variables, iterator functions) The AI should allow users to input natural language queries such as: “Calculate year-over-year growth for sales by region” “Create a rolling 3-month average of revenue” “Generate a dynamic segmentation table based on customer revenue” The system should then: Generate the DAX expression Explain the logic step-by-step Suggest performance improvements Validate correctness against the data model  Key Advanced Features  1. Context-Aware DAX Generation Uses schema + relationships Avoids incorrect aggregations Handles filter context automatically 2. Performance Optimization Engine Suggests: Using VAR for readability Avoiding expensive iterators Replacing inefficient patterns 3. Debugging & Explanation Layer Explains: Row context vs filter context Why a measure returns a specific result Helps users learn DAX, not just use it 4. Auto-Pattern Recognition Detects use cases like: Time Intelligence Ranking (Top N) Cohort Analysis Suggests pre-built optimized templates 5. Interactive AI Prompt Panel in Formula Bar Inline AI assistant (not separate tool) Works while writing DAX Suggests corrections in real time  Advanced Use Cases  1. Time Intelligence (Complex) User Input: “Calculate year-to-date sales and compare with last year” AI Output: Generates TOTALYTD, SAMEPERIODLASTYEAR Handles date table automatically 2. Dynamic Segmentation User Input: “Group customers into High, Medium, Low based on revenue” AI: Creates calculated column or measure Uses SWITCH + thresholds 3. Advanced Filtering Logic User Input: “Show sales only for top 10 products within each category” AI: Uses RANKX + CALCULATE + FILTER properly 4. Rolling Calculations User Input: “3-month moving average of profit” AI: Builds window logic using DATESINPERIOD 5. Multi-Table Context Handling User Input: “Total sales per customer with region filter applied” AI: Handles relationships correctly Avoids common mistakes ... View more

Sometimes we may have several visuals on one page in a dashboard filtered by a slicer, if one of the visuals (size like 1/4 or 1/3 of the screen) on a selected date is blank, can we use conditions  or parameters in another visual to hold the space. (Also for using BI visuals in slides)    ==>    Thank you!  ... View more

Currently, Scorecard metrics only support a fixed set of fields (owner, status, value, notes). There is no way to tag or categorise metrics beyond what is built in. The request is simple: allow users to add custom metadata columns to metrics — similar to how SharePoint Lists allow you to add custom columns. Example use case: A business may have metrics spread across multiple scorecards owned by different teams. Without a way to tag each metric with a "Process" or "Department" field, there is no way to report across scorecards by process or ownership group — you can only view metrics within the scorecard they live in. What we're asking for: Ability to add custom text/choice columns to metrics (e.g. Process, Department, Region) These fields to be queryable via the Scorecards REST API Ideally, filterable within the Scorecard view itself This would unlock cross-scorecard reporting without requiring hierarchies, and aligns with how metadata is already handled elsewhere in the Microsoft 365 ecosystem. ... View more

It would be nice to have the ability to move items from one workspace to another (at least the ability to move to "My Workspace") if you have the same privilages in Power BI Service. Right now, It only allows to "save a copy" and that is only for Reports. You cannot move semantic models to another workpsace.  ... View more