Users are currently able to Personalize visuals, but the current personalization is limited to changing the Visualization Type and changing the Fields that are in the visual.   Users cannot apply any additional formatting.   Please add this ability... for users to be able to see the Formatting Pane dialogue window and make adjustment to the formatting (colors, text size, data labels, etc.) when Personalizing a visual. ... View more

It is basic ability that is availble in most popular applications (including natove Copilot), but somehow is not supported by PowerBI copilot. Sometimes we need to share the results of copilot investigation, discuss it or just save for a future references. But currently the only option is to copy/paste the content manually which is very inconvenient. Export to PDF or at least JSON will be much better. ... View more

Hi, I think that it could more useful to have a Set multi variables activity for pipelines in order to use only one activity to set multiple variables without implementing more Set variable activity in the same pipeline. Less development effort, more readability. Thanks   Work better to work less. ... View more

Currently, in Power BI’s Matrix visual, the Format Visual > Column Subtotals setting applies to all measures in the visual. There is no option to selectively enable or disable column subtotals for individual measures. This limitation can lead to confusing or empty subtotal columns for certain calculated measures (such as MoM% Growth), where subtotals are not meaningful. Requested Enhancement: Please enhance the Matrix visual formatting so that under Format Visual > Column Subtotals, users can see a list of measures in the visual, and selectively enable or disable column subtotals for each measure independently. This would allow report designers to: Show subtotals only for relevant measures (e.g., sums, averages) Hide subtotals for calculated measures (e.g., ratios, growth rates) where they do not make sense Business Benefit: This feature would improve report clarity, reduce user confusion, and enable more professional and tailored reporting experiences. ... View more

2 Related Ideas:   1. The ability to customize the size of the page to eliminate charts that have horizontal scroll bars. I.e table too large for PDF / PPT export.   2. Another way to create more space is to allow font sizes smaller than 8. ... View more

As of today Microsoft Fabric capacity doesn't have explicit user-controlled warm pool for custom pools/capacity pools.   Fabric offers Starter Pools (pre‑warmed, always-on Spark clusters) and High Concurrency sessions (session reuse) as the main “warmth” mechanisms.    Microsoft documentation notes typical startup times of Starter Pools is ~5–10 seconds, whereas Custom Pools/Capacity Pools can take as long as ~2–5 minutes. Fabric capacities should be allowed a “keep warm” feature for custom pools in the sense of keeping clusters alive continuously. It will allow data engineering processes to run without a cold start-up. This can be a toggle button to allow admins to decide how they want to set it up.  ... View more

Currently there is no way to delete multiple items simulataneously in a workspace. Also there is no way to delete an entire folder and it's contents at once.    This issue was raised previously (here) and the response was that the introduction of folders (released Q1 2024) would solve this. However this functionality is still not compatible with folders.    There is a workaround to do it programatically however I feel this should be a feature within the Fabric UI.    ... View more

Summary Please add backup and restore capabilities for Cosmos DB in Microsoft Fabric, similar to what is available in SQL DB in Fabric and in Azure Cosmos DB (e.g., continuous backup / point-in-time restore). Why this matters In production scenarios, we need an officially supported way to recover from: accidental updates/deletes application bugs causing data corruption operational mistakes (e.g., bad scripts, wrong parameters) Today, Cosmos DB in Fabric lacks a native restore mechanism, which makes it difficult to define a reliable operational recovery plan (RTO/RPO) for mission-critical workloads.   Expected capabilities (examples) Point-in-time restore (PITR) / continuous backup restore Restore to a new database/container (safe recovery) Clear retention settings and documented limitations Current workaround (not ideal) We currently shortcut Cosmos DB in Fabric data into a Lakehouse and rely on Lakehouse time travel as a pseudo “backup/restore.” While this helps, it is a workaround and comes with additional complexity, operational overhead, and potential gaps compared to a first-class Cosmos DB restore feature. Reference Continuous Backup with Point-in-Time Restore - Azure Cosmos DB | Microsoft Learn Request Please provide a native, supported backup/restore solution for Cosmos DB in Fabric. ... View more

Would be great if PBI allowed buttons to be enabled and disabled via measure value. This will allow us to set visual restriction in Power BI that works with the current row level security. Currently there is no alternative to restricting users without row level access to click on a specific button. Instead they are able to click and navigate to an empty visuals. I understand this can be done by creating multiple reports with individual reports and setting specific audiences for each report, however we also need the consolidated report for the higher management. This causes the developers to maintain and do changes across multiple reports. Goal is to allow a single report button or bookmarks to be conditionally restricted by measure values. ... View more

1. Lakehouse with shortcut connections Problem Statement: Lakehouse deployment fails when shortcut connections are present. Additionally, the deployment pipeline is unable to create a Lakehouse with the default schema in the target workspace. Even if a Lakehouse with the same name is manually created and shortcut connections are added, the deployment pipeline treats it as a different item and continues to fail. As a result, complete manual intervention is required for each deployment, which is not scalable or feasible for ongoing development and release cycles.   2. Lakehouse with custom schema and tables Problem Statement: Deployment of a Lakehouse without shortcuts succeeds; however, the deployed Lakehouse does not include any custom schemas or table definitions that were created in the development workspace. In our implementation, we work with multiple datasets and rely on custom schemas and structured tables for better organization and tracking of data. Currently, the deployment process results in a newly created Lakehouse without any of the existing schema or table metadata, which significantly limits the usefulness of Lakehouse deployment.   Similarly, Git integration does not capture custom schemas or table definitions in the repository, leading to increased manual intervention during deployment.   img: Metadata of Lakehouse in GitHub Repo As a result, deploying a Lakehouse create only a new Lakehouse in the target workspace. Recreating schemas and tables manually or through scripts is more complex and time-consuming than creating a new Lakehouse itself. Lakehouse deployment should not be limited to merely creating an empty Lakehouse. 3. Warehouse or SQL Database deployment as complete unit Problem Statement: Currently, Warehouses and SQL Databases are deployed as a complete unit, without the ability to selectively deploy individual schemas or tables. In real-world development scenarios, multiple schemas and tables are often developed in parallel. While some objects may be ready for deployment, others may still be under active development. The existing deployment approach forces teams to deploy all schemas and tables together, even when only a subset of objects is production ready.   Deployment pipeline (No selective options for SQL Database modified objects) This increases the risk of deploying incomplete or unstable objects and limits flexibility in release planning. As a result, teams are either forced to delay deployments or rely on manual scripts and workarounds, which reduces the effectiveness of automated deployment pipelines. ... View more

We would like to have the option of allowing our report viewers to adjust visual COLORS to their their own preference.  We are ok with end-users modifying reports using slicers, filters, and drill options, but it would also be valuable to allow them to select their own color scheme if they would like to drive emphasis.   This could be achieved through some sort of toggle in the filter pane (allowing for whole report, or individual visual adjustments), but ultimately can be controlled by the report designer (in the case of locked-in design expectations).  That control could be a report setting.  Once these settings are active, a small color pallet could be provided to the end-user as part of a right-click menu option or a 3-dot menu option. ... View more

I have a Warehouse with multiple user schemas. I wish to have Dataflow Gen2 Destinations create/populate tables in those schema. But in the dialog to enter the table name when setting up the Destination, if I enter something such as MySchema.MyTable (where MySchema ALREADY EXISTS in the warehouse as a schema) I do NOT get MyTable located in MySchema.    What I get is an object in the dbo schema named [MySchama.MyTable].   Yes, I finally figured out that you have to go BACK one screen and expand the Advanced options and select True for Full Hierarcy Navigation, and THEN you can target a specific schema. But HONSTLY, who figured that out FIRST TIME AROUND?    Those of us that have been working SQL databases for years have been referring to objects with two-part nomenclature (<schema name>.<table name>) so to have THIS outcome instead of what I expected is a huge disappointment.   PLEASE MAKE THIS EASIER TO USE. Take a page from the Azure Data Factory folks where you have TWO boxes displayed at once: one for schema name and one for table name. THAT is easy to understand. ... View more

When using the Power BI cloud version, after completing a dashboard you can create subscription emails that Copilot can summarise using the dashboard data. Nevertheless, it would be ideal to allow prompt engineering before the message or email is sent to subscribers to amend content and focus for copilot.   ... View more

Power BI crashes when the amount of data imported into it is huge. As an analytic tool, this should not happen. Please improve the ability of power bi to handle multiple databases without efficiency being affected.  ... View more

In Power BI Apps, section headers are organizational only, they can’t serve as a clickable destination. To create a “hub” page and still group child items, authors must duplicate the name: once as a section and again as a page/link inside that section. This leads to redundant labels, extra maintenance, and user confusion. Current navigation lets authors add sections, links, and (optionally) one overview page, and the first navigation item becomes the app’s landing experience, but there is no way to make a section header itself open content. ... View more

When datasets are created in BigQuery using the BigQuery API without explicitly specifying a location, the API defaults to the US multi‑region. This default behavior causes issues for users need a way to change the default setting ... View more

Enable support for milliseconds on date time fields   dd/MM/yyyy HH:mm:ss.fff Related link  https://community.fabric.microsoft.com/t5/Desktop/timestamp-custom-format-for-milliseconds-not-working/m-p/4886987#M1448223    Regards ... View more

When you are in the advanced filter screen of you Power BI report, it would be nice if you are able to tables based on their name when you are editing. Currently, you have to find the table based on the name as you also need to look into the right folder. It is benifitial if we are able to search for the table based on the name/title of the table. ... View more

Hi   Please change the translation of the panel name Format Image from Formatbild to Bildformat or Formatera bild in Swedish.               Thanks, Anna-Karin   ... View more