Hello Team, As you may be aware, scheduled refreshes of the semantic models will be deactivated after a period of inactivity. Users will need to reset the refresh schedules, and this has caused unnecessary production issues. Please notify users before disabling these refreshes to ensure everyone is informed. it will be very usefull to the users to avoid such refresh failures and production issues  Thanks in advance. ... View more

It would be helpful to add dynamic context to visuals using a measure within this field:     ... View more

Need Power BI rest api which list all data sources from all the sematic model at tenant level ... View more

Hi, the deployment pipelines are represented a convenient and useful feature than using DevOps or Git and I hope that they can be improved as soon as possible. I think in order to deploy a warehouse it it very important that a deployment pipeline is able to follow the order of dependencies between warehouse objects without generating any errors. F.e. a deployment pipeline should first deploy the schemas, then deploy the tables and next the views and so on. A view could depend on another view. Thanks ... View more

Proposed Solution: Allow image visuals to support Report Page Tooltips, similar to charts and tables. Enable theme JSON properties (e.g., visualTooltip) to apply to image tooltips. Provide options for customizing tooltip appearance (background, font color, font size) directly in the Format pane for image visuals. Benefits: Consistent branding and design across all visuals. Improved user experience for reports with interactive images or navigation buttons. Greater flexibility for developers and designers to create visually appealing reports. ... View more

When a user clicks Save in the Power Apps visual embedded in a Power BI report, the expectation is that the Power BI visuals refresh automatically to show updated data. However, this refresh is not happening, so the report still shows old data even after saving changes through Power Apps. The response we got from Engineering team is Users with viewer permissions cannot see updated data in visuals automatically after applying and saving filters on the PowerApp visual. They need to refresh the visuals page to view the refreshed data. Users with admin/member/contributor permissions will see the refreshed data automatically after applying filters on the PowerApp visual.   We are currently utilizing the Power Apps visual in Power BI to allow users to interact with data and update reports in real time. This functionality has proven to be highly valuable, and we would like to make it available to all app viewers without assigning them admin, member, or contributor roles. The reason we cannot add these users to the workspace with elevated roles is that they only require access to a specific set of reports, rather than full workspace permissions. We grant access to users through the app, not directly from the workspace. Please enable this functionality for all app audiences. ... View more

Problem Statement: Currently, Power BI only offers Row-Level Security (RLS) to control data access, but there's no native way to control which report pages users can see in the navigation pane. All users with report access can view all pages, even if those pages aren't relevant to their role. Requested Feature: Implement Page-Level Security (PLS) that allows report developers to: Define which user roles can access specific report pages Automatically hide pages from the navigation pane for users without access Prevent unauthorized users from manually navigating to restricted pages Business Use Case: Many organizations have reports with different sections for different audiences: Executive dashboards for leadership Detailed financial analysis for finance teams Operational metrics for operations staff HR metrics for HR department Currently, we must create separate reports or apps for each user group, leading to: Content duplication and maintenance overhead Multiple versions of similar reports to manage Increased workspace clutter Higher administrative burden Proposed Solution: Add a "Page Security" setting similar to RLS in Power BI Desktop Allow assignment of security roles to individual pages In Power BI Service/Apps, only display pages the user has permission to view Integrate with existing RLS roles for unified security management Benefits: Simplified report management (one report instead of many) Better user experience (users only see relevant content) Reduced administrative overhead Consistent with existing RLS security model More scalable enterprise deployment Alternative Considered: Creating multiple reports/apps works but creates significant maintenance challenges and doesn't scale well for large organizations with many user roles. ... View more

Although we all agree that Polars/Pandas/DuckDB is faster on single node, the Spark Engine has a strong, nearly bug free API that has many efficient implementations (e.g. one of the best Delta/Iceberg/Hudi Writers). It also offers Stream Processing across many matured data sources.   There's nearly 15 years worth of rich tutorials on Spark patterns. Copilot/AI is extremely proficient at producing high-quality Spark code. Data Engineers can be highly productive in Spark in a very short period of ramp up. It is also a great API to learn, since all hyperscalers offer a managed Spark runtime, so it's easy to find a Data Engineering role (job security etc.)   Spark Declarative Pipelines will also significantly reduce the barrier to entry to writing ETL code: Spark Declarative Pipelines Programming Guide - Spark 4.1.0-preview1 Documentation   But - due to the lack of a cheap/fast/single-node runtime, instead of taking advantage of these awesome API investments in Spark Engine, many Data Engineers who have smaller volume of data end up writing entire heterogenous API centric codebases, when they could just use the Spark API and it's innovations, so the code can scale out when the job needs to with simple config changes, or run in local mode when it doesn't need to.   Ideally, one day Fabric could offer a serverless Spark runtime, but until then, it might be fairly easy to tune up a single-node Spark runtime that is opinionated with spark configs that do not force shuffles. Perhaps NEE could back this runtime to reduce the memory footprint as well.   OSS Apache Spark can run pretty fast(er) on a single node if you tweak a few settings. The problem is, you need to be a Spark Expert to read these things and tweak it. It'd be good if Fabric could do this for laymans.   How to Speed Up Spark Jobs on Small Test Datasets How to cut the run time of a Spark SBT test suite by 40% | by Matthew Powers | Medium Setting Shuffle Partitions in order to limit the number of Tasks by qnob · Pull Request #291 · holdenk/spark-testing-base Spark Standalone Mode - Spark 4.0.1 Documentation   For non-distributed datasets on a single VM, Fabric could go ahead and provision a Spark runtime that is Executor heavy, say, on a 6 core VM, do this:   Here's an example of an opinionated spark config ```yaml spark:   local: true                           # Fire spark in local[*] mode   ui: false                               # Turn off Spark UI to save resources   offHeapEnabled: false        # Disable offheap   driverCore: 1                       # Driver doesn't do much, reduce it more if needed   driverMemory: "512mb"    # "   executorCore: 5                 # Executor does the most work, I'm not sure if odd numbers are allowed 🙂   executorMemory: "11.5g"  # "   shufflePartitions: 1             # Don't need shuffles on small data sizes ``` ... View more

We would like to have a tenant setting that allows us to completely disable report sharing with other users. Currently, to block report sharing, we can disable the tenant setting for people within our organization. Similarly, we need a tenant setting that either blocks sharing with specific people or disables sharing entirely. ... View more

We have issues where Power Quary requires realoding the dataset every time we need to work on it. Ideally, once the data is loaded, we should be abel to work on it without having to reaload it repeatedly. Please investigate this behaviour, as it impact workflow efficiency and incraeses processing time. ... View more

When using a Copy Activity with a REST source in Microsoft Fabric, the current activity input and output only provide minimal metadata about the request and response. This makes troubleshooting difficult, especially when using dynamic URLs, query parameters, pagination, or REST APIs that rely on correlation IDs for traceability.   Today, the activity input shows basic request settings such as method, timeout, and configured headers, but it does not show the final resolved request URL or the details of the HTTP response returned by the server. Without this information, diagnosing issues like invalid query parameters, authentication failures, pagination errors, throttling, and server-side errors is significantly harder.   Problem / Pain Point: When a REST-based Copy Activity fails or behaves unexpectedly, users cannot see the actual request URL, including the evaluated query string. They cannot trace the request back to server logs because correlation IDs are not surfaced. They cannot inspect the HTTP status line, response headers, or the response body returned during an error. Pagination information such as Link headers is also missing. These fields are standard diagnostics for debugging REST calls, and without them, troubleshooting in Fabric becomes guesswork. Proposed Enhancement: Add the fully resolved request URL to the Activity Input. This should include the full URL with dynamically evaluated parameters and query string so developers can see exactly what Fabric sent to the server. Expand Activity Output to include detailed HTTP response metadata. The requested fields are: HTTP Status Line (for example: HTTP/1.1 404 Not Found) Response Headers, specifically: Correlation ID (such as X-Request-ID or X-Correlation-ID) Timestamp returned by the server Content-Type Content-Length Link header (RFC 5988) for pagination Response body when the server returns an error (HTTP 4xx or 5xx) Impact / Value: Adding this metadata would significantly improve troubleshooting for REST ingestion pipelines, allow correlation with server logs using correlation IDs, reduce debugging time for dynamic URL issues, improve visibility into pagination and throttling scenarios, and bring feature parity with tools like Azure Data Factory. This enhancement would make REST-based data ingestion in Fabric more reliable, debuggable, and aligned with enterprise observability practices. ... View more

Sinto falta de um recurso que destaque as colunas e medidas que estão sendo utilizadas no relatório. Por exemplo, às vezes quero excluir uma medida, mas não sei se ela está sendo usada em algum visual do dashboard. Seria muito útil ter um indicador mostrando se e onde cada medida ou coluna está sendo utilizada.   ... View more

Power BI mobile app is great for viewing reports, but it’s missing two critical features: Export to PDF/Excel and Share / Print. Mobile users often need to share insights quickly during meetings or while traveling. Having these options directly in the app would: Boost productivity on the go Enable instant sharing Create consistency with the desktop experience Request: Please add Export to PDF/ Excel and Share / Print the report options to the Power BI mobile app. This would make the app far more powerful and user-friendly for business users everywhere. ... 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

Data segmentation visual, configured as a dropdown, is overlapping the main panel, as shown in the image above. ... View more

Ter mais opções de ícones nas formatações condicionais, as vezes sinto falta de alguns ícones específicos, como seta para baixo verde. Seria legal se pudessemos personalizar/escolher nossos próprios ícones também!  ... 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

Problem: Currently, downstream consumers who need to query Eventhouse data via Lakehouse shortcuts must have read access to the primary Eventhouse tables. This creates two main challenges: Security / Governance: Users can access the primary Eventhouse, which may not be desirable. Operational Overhead: Teams must schedule incremental .export commands for each table to provide Lakehouse access, which is cumbersome and difficult to manage at scale.   Proposed Solution: Introduce a feature that allows Eventhouse to automatically export data to Lakehouse shortcuts without requiring users to have read access to the primary tables. Benefits: Downstream consumers can query Lakehouse shortcuts without impacting Eventhouse compute or hitting query limits. Eliminates the need to schedule per-table exports manually. Maintains strict security and governance by preventing direct access to the primary Eventhouse tables. Supports both full and incremental exports, keeping Lakehouse data fresh and up-to-date. ... View more