Paginated reports - please make it available in Pro as well as Premium .. thank you ... View more

Empower data owners and administrators with precise control over which data Copilot can access and use for responses. This ensures sensitive or irrelevant information isn't inadvertently shared or processed.   A centralized system allowing data responsible persons/admins to set clear controls at three key levels: Capacity Level: Define broad default settings or hard exclusions for entire data capacities. Workspace Level: Override or refine capacity-level policies for specific workspaces. Item Level: Provide the finest control, allowing direct inclusion or exclusion of individual items (semantic model, eventhouse, etc.) from Copilot's scope. Key Benefits: Enhanced Trust & Compliance: Users and organizations gain confidence knowing data usage is controlled, meeting privacy and regulatory standards. Reduced Risk: Prevents Copilot from using sensitive, outdated, or inappropriate data. Empowered Data Owners: Puts control directly into the hands of those who understand the data best. ... View more

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

Enable individual users / freelancers to study and practice fabric with a per-user license similar to Premium Per User in Power BI. F2 is a price point that is too high for them. Strong limitations in time and resources available would make sense, but there should be a clear monthly cap that cannot be like the current F2. ... View more

Power BI reports currently do not fully meet WCAG 2.2 AA requirements for Keyboard Accessibility (2.1.1). Some interactive elements, such as tooltips or information boxes for data visualizations that appear on mouse hover, cannot be accessed using a keyboard alone. While screen readers can read the content, keyboard-only users who do not use screen readers cannot access this information. Impact: This creates a significant barrier for users who rely on keyboard navigation, preventing them from accessing all report content and functionality. It also means reports cannot achieve WCAG 2.2 AA compliance. Request: Please enhance Power BI so that all interactive elements, including hover-triggered tooltips and information boxes, are fully operable via keyboard navigation. This change would help ensure Power BI content meets WCAG 2.2 AA standards and supports accessible digital services. ... View more

Currently, when configuring Edit Interactions in Power BI reports, users must manually adjust filters and highlights for each individual visual. This process is time-consuming and prone to inconsistencies, especially in reports with multiple visuals. Proposed Enhancement: Introduce a global option that allows users to apply the same Edit Interaction settings (filter or highlight) across all visuals in a report or within a selected page ... 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

We need support for Service Principal authentication when creating Lakehouse connections.   Right now, Lakehouse connections can only be created using a user account. As a result, Dataflow Gen2, Pipeline copy activity, and Copy Job cannot use a Service Principal (SPN) when connecting to a Fabric Lakehouse as a source or destination.   This is an issue for us. We want to avoid user-based connections because: We need environment-specific identities (dev/test/prod) to prevent accidental cross-environment writes (e.g., dev pushing data to prod). Tying connections to personal user accounts creates fragility - things break when someone leaves the project or the organization. Service Principal support for Lakehouse connections is required to ensure secure, reliable, and environment-isolated authentication.   The screenshot shows that only user authentication is available, not service principal authentication. ... View more

Anyone who uses PowerBI long enough has had a PBIX with 50-60 measures and it has become time consuming and tedious to mantain. In Excel you can do a quick find/replace to edit several formulas - in PowerBI you need to select each one individually. An "excel-like" interface for editing measures would save a lot of time! This would take PowerBI to the next level regarding productivity. I've prepared a mockup for this as well as a DAX Editor. Let me know what you think. Mockup: https://i.imgur.com/z6TBOQb.png?1 ... View more

Please make it possible to run a notebook as the Workspace Identity, instead of running as a user identity.   This means the notebook (and the notebook's security context, i.e. the notebook's authentication to data connections) will not depend on any single user but use the Workspace Identity instead. ... View more

Power BI reports currently do not fully meet WCAG 2.2 AA requirements for Content on Hover or Focus (1.4.13). When additional information appears on hover (e.g. tooltips), users cannot move the pointer over this content without it disappearing. If a user is zoomed in (particularly when using smaller screens), they may need to scroll or pan to view the entire content, which can be impossible unless the user can move their pointer off the trigger without the content disappearing. Users utilizing particularly large pointers may also need to be able to hover over the content without it disappearing if, when positioned on the trigger, the pointer partially obscures the content. Impact: This creates a significant barrier for users who need to zoom in and/or use large pointers due to vision impairments, preventing them from accessing all report content. It also means reports cannot achieve WCAG 2.2 AA compliance. Request: Please enhance Power BI so that hover-triggered content can be hovered over without disappearing. This change would help ensure Power BI content meets WCAG 2.2 AA standards and supports accessible digital services. ... View more

Hi, to order an array into a pipeline it could be very useful to have an appropriate feature, e.g. a sort activity or a sort regex function, without using any notebook codes. F.e. an array could contain the name of files read by a get metadata activity against an on-premise folder and before copying the related files into a lakehouse it could necessary to order this array to perform a right copy following a temporal order. Thanks ... View more

Power BI reports currently do not fully meet WCAG 2.2 AA requirements for Use of Colour (1.4.1). Data visualizations rely on colour alone to convey meaning (ie. identify categories or data types). While data labels can be applied to address this, the labels are presented via tooltips, which are not fully accessible due to other issues (keyboard navigation and hover behavior). Impact: This creates a significant barrier for users who cannot perceive colour and rely on keyboard navigation and/or hoverable behavior in tooltips, preventing them from accessing all report content. It also means reports cannot achieve WCAG 2.2 AA compliance. Request: Please provide built-in options to include accessible alternatives to colour coding, such as patterns, shapes, or persistent text labels within visuals. This change would help ensure Power BI content meets WCAG 2.2 AA standards and supports accessible digital services. ... View more

Power BI reports currently do not meet WCAG 2.2 AA requirements for Reflow (1.4.10). At screen resolution 1280 x 1024, when users zoom in up to 400%, the content does not adapt to a single-column layout. Instead, users must scroll both horizontally and vertically to access information. Impact: This creates a significant barrier for users who need to zoom in due to vision impairments - they can lose their place and must expend more physical and cognitive effort accessing the content. It also means reports cannot achieve WCAG 2.2 AA compliance. Request: Please enhance Power BI so that published reports can reflow responsively without loss of information or functionality when zoomed. This change would help ensure Power BI content meets WCAG 2.2 AA standards and supports accessible digital services. ... View more

Currently, user-defined functions are defined at the model level. It would be nice to be able to define functions that are local to a DAX expression (e.g. the DAX expression of a measure, calculated column, or even a variable) so that the model-level scope does not get cluttered with functions that are needed in only a few places. This might require treating functions as first-class citizens, similar to what was done in Excel with LAMBDA, so that functions can be assigned to variables. ... View more

To fix inconsistencies in analytic settings, functionality needs to be enhanced to ensure they are on par with other visual component enhancements made for Cartesians, and additional settings for scatter charts is also necessary. Report creators will find it easier to format and customize settings to align with the overall look and feel of their reports. ... View more

Need a tool that can provide detailed information on which queries or DAX commands are being run by specific users, including the duration of each query, on their Power BI embedded capacity during times of CPU or capacity spikes. This will help us quickly identify the root cause of these spikes. ... View more

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

Power BI reports currently do not fully meet WCAG 2.2 AA requirements for Info and Relationships (1.3.1). While it is possible to add visible headings, there is no way to apply a proper heading hierarchy programmatically. For example: There is no option to apply heading 1 formatting to the main text heading (ie. nest it within an h1 HTML element). Heading tags (h1-h6 HTML elements) can only be applied to entire text boxes, not specific text within them. A 'Power BI Report' visually hidden heading 2 (h2 HTML element) is automatically inserted and cannot be edited or removed. Impact: This creates a significant barrier for screen reader users, preventing them from reliably identifying and navigating using headings. It also means reports cannot achieve WCAG 2.2 AA compliance. Request: Please provide full support for semantic heading structures in Power BI reports, including the ability to apply heading levels (H1–H6) to individual text elements. This change would help ensure Power BI content meets WCAG 2.2 AA standards and supports accessible digital services. ... View more