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

Trying to assign Fabric capacity to over 25,000+ My Workspace in organization. Assiging manully is not feasible. Requesting an automatic feature to enable bulk assignment to users instaed of manual as it is time consuming. ... View more

Want to download reports that are created in the Power BI service or Power BI Desktop and based on a semantic model in My Workspace in live connected mode.     ... View more

Currently for customers who purchased Azure from CSP provideres need to reach out to the provider to get the emission information.    https://learn.microsoft.com/en-us/power-bi/connect-data/service-connect-to-emissions-impact-dashboard But the options for the CSP provider to share the data are below: Providing customer‑specific exports or reporting packs from EID visuals and reports ·   Using exported EID data to create offline or downstream customer‑specific reports   We would request either one of the below solution to be implemneted so that the CSP providers can share the emissions to the individual customers .  OPTION 1 (preferred option) As a CSP, we are in need of a filter in the Emissions Impact Dashboard (EID) by specific customers/tenants. At the moment, there is no option to apply such a customer/tenant filter. While we could add a Tenant–Subscription mapping to the semantic model to enable this, the model would need to be updated. Since the EID is delivered as a template app, it’s not possible to download (see screenshot) or modify the semantic model to include this mapping. Allowing this option would give us what we need to help our customers in most simple way.       OPTION 2  An alternative solution would be to let you add a customer/tenant filter directly to the report. Our preference, however, is to gain access = have to ability to click"Open" to both the semantic model and the report so we can customize them as needed. This would also allow us to share the report with our customers without manually applying filters and exporting it to PDF or PowerPoint for distribution.         ... View more

The request is to ensure Schedules are not included in the definition of a Data Pipeline for purposes of Deployment Pipelines.   Today, when we deploy content across environments, the item frequently appears as “different” because the schedule configuration is included in the comparison. This creates constant noise and makes it harder to identify meaningful differences.   More importantly, a schedule configured in DEV or TEST can be promoted into PROD as part of a deployment. This creates a real operational risk and is unacceptable — PROD scheduling must be managed independently and explicitly, not carried over from lower environments. ... View more

Currently, Excel workbooks connected to a Power BI / Microsoft Fabric semantic model (for example, via Analyze in Excel or Power BI dataset connections) do not automatically refresh when the underlying semantic model is updated. Users must manually open the Excel file and trigger a refresh for the latest data to be reflected.   Current Behavior The semantic model refreshes successfully in Power BI / Fabric. Data refresh occurs only when: The Excel file is opened in Excel Desktop, or A manual refresh is triggered. Expected / Desired Behavior Provide an option to automatically refresh Excel workbooks when the connected semantic model completes a refresh, especially for files stored in OneDrive or SharePoint while opening a report in Excel web. ... View more

Currently, the only available authentication method is the Organizational Account. Service Principal and Workspace Identity authentication methods are required.   Lakehouse connector overview - Microsoft Fabric | Microsoft Learn ... View more

When exporting large amounts of data from a visual, the export may fail or return incomplete results without a clear explanation. Power BI should display a user‑friendly and actionable error message when an export cannot be completed due to data size or platform limits.   This would help users quickly understand the limitation, take corrective actions (such as applying filters or reducing data volume), and avoid confusion caused by partial or failed exports. ... View more

Currently, when a Dataverse Link to Fabric is recreated, refreshed, or experiences configuration changes, there is no exposed audit log or telemetry that allows customers to identify who or what triggered the action. This lack of traceability creates operational risk, investigation delays, and customer mistrust—especially in production environments where Fabric tables are business‑critical. ... View more

The new "view usage metrics report" does no longer support dashboards - it only works for Power BI reports.   And the "old" usage metrics report does no longer give back any values for dashboard usage.   It would be great to have this standard feature back, The old usage metrics would again give back usage values for Dashboards, or The new usage metrics would work for Dashboards, too Thanks a lot, in advance! ... View more

The current card visual forces users to overlap elements or waste copious amounts of time creating custom visuals. The new card feature should give users the ability to create multiple cards in a single container and provide a greater level of customization. ... View more

It would be beneficial to incorporate features from Pivot tables that allow for the expansion and collapse of columns and hierarchical column groups within tabular visuals. This would not only solve the current limitations of matrices but also provide report creators with the flexibility to hide and show rows and columns, saving these settings for future use, thus eliminating the need to scroll through irrelevant data. ... View more

Possibility for Power BI Apps to choose content across different Workspaces. ... View more

Enabling customized calculations at the query level for subtotals and grand totals would offer greater flexibility in reporting and preserve performance. Efficient organization of control settings to modify the style of these totals separately will empower report creators to achieve their desired appearance, while addressing their need for more control and customization in reporting. ... 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

Power BI displays numbers correctly based on regional settings (e.g., comma as decimal separator), but copying values exposes the raw floating‑point value with a dot separator. Please add an option to copy the formatted (displayed) value so locale, rounding, and readability are preserved. ... View more

We would like to have a Date selection slicer which allows the report viewer to decide which type of slicer to use: relative/between/etc. Nowadays I have both users who like 'relative' slicer and users who like 'between' slicer. Because of that I have to waste space on my reports by including both types of slicers, only because there is no option for end user to manually change it: Instead I would like the end user to decide, some sugestions how it could look like:         ... View more

The Dynamics 365 Business Central connector in Power Query only supports authentication using a user account.   Please add support for Service Principal authentication using Azure AD App Registration with Client ID and Secret.   This would allow automated refresh processes and remove the dependency on personal user accounts.   Business Central APIs already support Service Principal authentication so enabling it in the Power BI connector would greatly improve enterprise scenarios and Microsoft Fabric integrations. ... View more

Currently, when using Git integration or Fabric Deployment Pipelines with a semantic model, the Model view layout is not preserved across environments.   Instead, the Model view is regenerated with an automatic, arbitrary layout.   This makes it harder for developers and users to understand the structure of the model and how it is intended to be used.   We deliberately organize tables in the Model view to communicate the model’s logic and intended usage. This layout needs to persist across feature, test, and production workspaces.   Therefore, support for preserving the Model view layout through Git integration and Deployment Pipelines is required.   This applies to both Import mode and Direct Lake mode models.   For more information: https://www.reddit.com/r/PowerBI/s/rdSNelMaHB ... View more