Need a direct option to restore deleted report in the workspace ... View more

Having to reapply filters manually each time I wish to have a different view in the monitoring hub is painful.   I want to be able to create views (or bookmarks) so I can quickly switch between the 3-5 different filter combinations I regularly use. ... View more

I wish this to be an option to copy the output if a cell by click on "Copy Output" from the cell's output menu as shown below        ... View more

Enable the Variable Library as a centralized location for storing all environment‑specific variables, allowing us to adjust them for promotion scenarios (e.g., from dev to prod) without relying on deployment pipelines.   It would be ideal if semantic model parameters or data sources could reference a Variable Library, similar to how deployment pipelines handle variables today. When using CI/CD Option 1 — Git‑based deployments — it isn’t possible to hardcode environment‑specific values or data sources, since these differ across environments. Example: If I build a report in a dev workspace/branch that uses a dev data source, and then promote it to a prod workspace/branch via PR, I have no way to automatically switch the data source to the production version. I would need to submit an additional PR just to update the prod branch, resulting in the same report with different hardcoded sources.  ... View more

When using pipelines/notebooks, we can successfully export tables with uppercase names. However, when converting CSV files to tables in Lakehouse today, the names are forced into lowercase. This causes data inconsistency for the enterprise, which requires uppercase naming. The documentation states that both uppercase and lowercase naming are supported; please add a case-sensitive mode for the "Load to Table" feature. ... View more

When importing a file from an Azure Storage Account, by default it can be processed in several formats. XML, a fairly common format, is not currently supported and therefore cannot be parsed. It would be good to have this option.   https://blog.fabric.microsoft.com/en-us/blog/continuous-ingestion-from-azure-storage-to-eventhouse-preview?ft=All  ... View more

One of our customer is using standalone copilot and their requirement is when ever a user uses the standalone copilot it should be billed under certain workspace which customer can be able to select inorder to avoid confusion on the usage of standalone copilot getting billed to random workspace. ... View more

When a user opens a report and selects the File dropdown, they see the “Embed report” option with the following choices: SharePoint Website/Portal Developer Playground So the Customer wants to Disable “Embed report” for View-only users in power bi ... View more

SharePoint Online domain rename, Users are facing Power BI OneDrive auto‑refresh failures because Power BI continues to reference the old SharePoint/OneDrive domain URL for reports imported from OneDrive. Power BI does not provide an option to update the OneDrive/SharePoint source URL for existing datasets manually. Solution: Re-importing the reports from the Ondrive updates the OneDrive URL. Problem: Re‑importing removes existing configurations such as: Row‑Level Security (RLS), Bookmarks, Report‑level settings and dependencies This is not scalable for enterprise environments with many reports. Feature request: Provide a supported way to update or rebind the OneDrive / SharePoint source URL for existing Power BI reports or semantic models after a domain change—without re‑importing and losing configurations. ... View more

Hello. Power BI edit/change to the report (change in report sheet “measure x” from Hidden to Visible), doesn’t show as ‘Different’ in deployment pipeline comparison results. January 2026, this has been shown as ‘different’ in pipeline, now,  since beginning of February no change visibility. We created a support ticket to MS and got answer that,  "PG confirmed that the behavior you observed is expected in the current design and the previous behavior was actually unintended, so what you are seeing now reflects the intended functionality moving forward. Report-level changes are not included in the comparison results. Newer builds focus primarily on Model Schema and structural changes, while updates made at the visual/report layer are treated as report artifact updates rather than structural differences." Since lots of our Power BI changes are on report-level the previous behavior observed was better. From our perspective this was not an improvement. Hopefully the report level changes can be shown in deployment pipelines comparison results. ... View more

Our team has been facing a consistent challenge when trying to present summarized trends alongside detailed data in the same view. Currently, we have to use separate visuals—a column chart to show the trend and a matrix to display the underlying breakdown. This creates a few problems: It is very difficult to align the visuals perfectly, especially when trying to match columns with matrix rows. There is limited layout flexibility, which often results in misalignment when resizing or adjusting visuals. Maintaining this setup becomes time-consuming and fragile, particularly when dashboards evolve. It would be extremely helpful to have a single visual that combines a column chart with a matrix/table beneath it, where the columns in the chart directly correspond to the columns in the matrix. This would: Improve visual alignment and readability Reduce dashboard maintenance complexity Enable clearer storytelling between aggregated trends and detailed data A unified visual like this would significantly improve the usability and design flexibility of reports. ... View more

I would like the ability to assign multiple legends in a scatter chart visual and select which legend label should be used as the data label from those multiple options. ... View more

Context & Observation In building pixel-perfect Power BI reports, we frequently use Shapes (rectangles, lines, rounded containers, icons) to create headers, separators, buttons, and layout scaffolding. When the shape count is high, we see noticeably slower page rendering and interactions (e.g., slicer response, bookmarks, hover, selection). Conversely, DAX measures—even in large numbers—do not show the same penalty because they don’t create additional draw calls or DOM-like visual nodes; they are calculated at query time and reused by visuals. Repro (high level) Create a report page with 100–300 Shapes (lines, rectangles with gradient/fill, shadows/rounding). Keep data volume minimal and visuals simple (e.g., a few cards/labels). Compare page navigation and selection interactions versus the same page with consolidated or fewer Shapes. Performance Analyzer shows more time spent in visual rendering rather than data query. Business Impact Authors avoid clean visual scaffolding and branding due to performance costs. Navigation/landing pages with many decorative elements feel sluggish, which reduces perceived quality. This disproportionately affects enterprise reports that require pixel-perfect layout and design consistency. Request: Could Power BI optimize the rendering pipeline for Shapes so that using many Shapes does not impact performance? Possible approaches might include: Treating Shapes as lightweight vector primitives with batching, caching, or GPU acceleration. Offering a Combine/Flatten Shapes option to reduce the number of render objects. Attachments (available on request) Sample PBIX files with high shape counts Screen recordings comparing interaction latency Performance Analyzer screenshotsProviding a Low-Overhead Shape type for decorative elements (no interactivity) Why this matters Other design tools (e.g., traditional drawing apps) handle numerous vector shapes efficiently through batching and caching. Bringing a similar approach to Power BI would allow rich layouts without compromising performance, aligning with enterprise design standards. Exposing a Shape Count / Visual Complexity metric in Performance Analyzer to help authors identify bottlenecks. Impact: This would enable authors to build richer layouts (headers, separators, callouts) without compromising responsiveness, particularly on navigation-heavy pages. ... View more

The primary axis are outdated and require significant improvement when compared to Excel. This makes it difficult for report creators and often leads to problems when trying to manage and style them effectively. By offering more format settings, greater control over displayed data can be provided, especially if axis ticks, new gridlines, and separators are also included. ... View more

End user is unable to retrieve data from Personal/My workspaces in Power bi through Rest APIs using Service principal identity. We understand that this is currently a platform limitation, which is also mentioned in below document: Embed Power BI content in an embedded analytics application with service principal and an applicati…   The currently available workaround to use "User" identity to access Personal workspaces will not help. Through "User" identity we can only access one Personal workspace at a time, and is not meeting end users requirement to access hundreds of personal workspaces data at one go.   Ask: End user would like the limitation "Service principal is not supported for personal workspaces" to be removed. If not possible, then to add some feature to help end users access multiple personal workspaces at a time.   ... View more

ServiceNow is a widely used enterprise service management platform, and many customers rely on Power BI and Microsoft Fabric to analyze this data. Today, integrating ServiceNow with Power BI usually requires custom connectors, REST API work, or third‑party tools, which adds complexity, maintenance effort, and support challenges. A native, Microsoft‑supported Power BI Service connector for ServiceNow would save significant time and cost, improve reliability and governance, and make it easier for organizations to adopt Power BI and Fabric at scale. This connector would allow customers to focus on insights and decision‑making instead of building and maintaining custom integrations. ... 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

Users are looking for a date when direct query and mixed mode reports will have updates similar to import. Any update on this feature would be helpful. ... View more

Summary Add an advanced context-menu option on standard visuals that allows users to view and edit the visual’s JSON directly from the Power BI canvas. Problem Statement Today, advanced users increasingly rely on editing visual JSON to apply formatting or behavior changes that are not currently exposed through the Power BI Desktop UI. The only way to do this is by saving the report as a .pbip project and manually editing the visual JSON files. While powerful, this workflow: Is unintuitive and error-prone for many users Requires leaving the Power BI canvas and working directly with project files Discourages experimentation due to the risk of breaking the report Creates a barrier for users who are comfortable with JSON but not with the .pbip file structure or source control workflows As a result, many users are editing .pbip files simply to unlock visual customizations that feel like they should be available in-context. Proposed Feature Introduce an Advanced option in the visual right‑click context menu (or Format pane) such as: Right‑click visual → Advanced → Edit Visual JSON This would: Open a modal or side-pane JSON editor scoped only to the selected visual Display the current visual definition JSON (read/write) Validate changes before applying them Allow users to revert to the previous state if the JSON is invalid Optionally, this could be gated behind: A preview feature flag A warning or “advanced users only” acknowledgment Read-only mode with an explicit “Enable Editing” toggle Benefits Improves productivity by keeping advanced customization in the canvas where users are already working Reduces friction compared to editing .pbip files directly Encourages experimentation with faster feedback and safer iteration Aligns with real-world usage—many users are already editing visual JSON today, just through unsupported workflows Future-proofs the product by allowing advanced users to access new or undocumented properties without waiting for full UI support Why This Matters Power BI already exposes the full visual definition internally; this feature simply makes it accessible in a safer, more discoverable, and more user-friendly way. Similar to how Tabular Editor exposes advanced model metadata, this would serve power users without impacting the default experience for most users.   This capability would significantly reduce reliance on .pbip file manipulation while empowering advanced users to push Power BI visuals further. ... View more