Power BI custom visuals currently have no official and supported way to trigger report page navigation or apply report bookmarks from inside a .pbiviz visual. This is a significant limitation for developers building advanced navigation components, custom sidebars, dynamic menus, guided experiences, or application-like report interfaces. Power BI already supports page navigation and bookmark actions through native buttons, page navigators, and bookmark navigators. However, custom visuals cannot invoke those same actions through the Visuals API. A supported API would allow custom visuals to request actions such as: - Navigate to a report page by page name or page ID. - Apply a report bookmark by bookmark name or bookmark ID. - Optionally expose the list of available pages and bookmarks to the visual. - Respect report permissions, sandboxing, tenant settings, and security boundaries. Example API concept: ```ts host.navigation.navigateToPage("ReportSectionabc123"); host.navigation.applyBookmark("BookmarkName"); host.navigation.getPages(); host.navigation.getBookmarks(); ... View more

Currently, we understand that users can reference shared cloud connections within the Variable Library . However, connections created through On-Premises Data Gateway (OPDG) and VNet gateways are not supported in this experience.   We would like to request support for OPDG gateway connections to be available as selectable connection references in the Variable Library. This enhancement would significantly improve the overall user experience and align the Variable Library feature with broader connectivity scenarios commonly used by customers. ... View more

Do not remove classic Map and Filled Map visuals – they offer essential simplicity and control missing in Azure Maps Description: Please do not fully remove the classic Map and Filled Map visuals from Power BI. While Azure Maps is powerful, the classic map visuals are still far superior for many real‑world business scenarios, especially when users need: Simple and predictable formatting Direct control over legend colours Clear relationship between bubble size and legend Fast report development without complex layers Stable visuals for operational, safety, and compliance reporting Azure Maps introduces: Unchangeable legend symbols Complex layer‑based formatting Limited control over categorical legend colours More configuration for basic use cases For many users, this makes Azure Maps harder to use, not better. Request: Keep classic Map and Filled Map visuals available (even as “legacy”) Allow users to explicitly choose which map engine to use Do not force automatic migration where formatting control is lost This would: Reduce report rework Avoid breaking established reports Respect different user skill levels and business needs Azure Maps can coexist as the advanced option, but the classic maps are still essential.   ... View more

Currently via the ... next to a pipeline we can select recent runs and the window on the right hand side displays the start time of all recent runs, but does not detail the end time or durations of those runs. Whereas via the monitor hub if we locate a historical run and use the ... and select historical runs it shows the runs with the start end, end time and Duration. Due to a high number of pipelines locating previous runs in monitor can be slow as we cannot limit the filter to find pipeline names without first paging through 100's of jobs, so looking for historical runs is far quicker via the pipeline itself. Can we make these two different ways of access previous runs of a pipeline consist and show the start and end times as well as the durations.  This will make it easier compare historical runs time and performance. ... View more

Currently SSRS allows parameter visibility only at the individual report or parameter level.   In enterprise environments with hundreds of reports embedded in custom portals using ReportViewer, administrators need a global configuration option to:   1.Hide parameter pane globally 2.Define default parameter visibility 3.Apply organization-wide parameter UI settings   This would reduce repetitive report configuration and improve centralized administration.   Suggested options: Report Server level setting ReportViewer global property Folder-level inheritance Parameter visibility policy ... View more

Corporate Proposal Argument. Executive Summary Power BI has matured into a leading enterprise BI platform, yet it lacks a robust system of keyboard shortcuts comparable to Excel. This gap reduces productivity, limits accessibility, and creates inconsistency across Microsoft’s analytics ecosystem. Implementing a comprehensive and configurable set of shortcuts would align Power BI with industry standards and user expectations. Productivity Benefits Accelerates formatting, navigation, and visual editing without reliance on the mouse. Reduces time spent on repetitive tasks, increasing analyst efficiency. Provides consistency with Excel, lowering the learning curve for new Power BI users. Enhances workflow fluency in enterprise reporting environments. Accessibility Benefits Empowers users with mobility impairments to fully interact with Power BI. Strengthens compliance with accessibility standards (WCAG, Section 508). Allows customizable shortcuts, adapting to diverse user needs and keyboard layouts. Governance Benefits Enables organizations to standardize shortcut usage across teams. Facilitates training and onboarding with clear, documented productivity practices. Improves governance by reducing reliance on manual, error-prone mouse interactions. Technical Proposal Introduce a core set of universal shortcuts (formatting, color, type of visual, panel navigation). Extend Alt-sequence navigation to properties and formatting options. Provide a shortcut customization panel for user-defined mappings. Ensure multilingual and cross-platform compatibility for global adoption. Expected Impact 20–30% efficiency gains in report design and formatting tasks. Increased adoption and satisfaction among enterprise users. Stronger alignment between Power BI and Excel as part of Microsoft’s analytics suite.   ... View more

Hi MS Support team,   Currently, when you use Spark SQL to create a temp view with tables that have schema name, the temp view can't be used in later steps.   For example,   Firstly, create a temp view using below code   CREATE OR REPLACE TEMPORARY VIEW tmpvw1 AS SELECT     * FROM     IM.test t1     LEFT JOIN  ref.testref t2     ON t1.key= t2.key   In next step, select the temp view tmpvw1 using the following code:   SELECT * FROM tmpvw1   You will see a error message similar to below  "Error [TABLE_OR_VIEW_NOT_FOUND] The table or view `IM`.`test` cannot be found. Verify the spelling and correctness of the schema and catalog. If you did not qualify the name with a schema, verify the current_schema() output, or qualify the name with the correct schema and catalog. To tolerate the error on drop use DROP VIEW IF EXISTS or DROP TABLE IF EXISTS. SQLSTATE: 42P01; line 1 pos 14; 'Project [upcast(getviewcolumnbynameandordinal(`tmpvw1`, new_column, 0, 1), StringType) AS new_column#690, upcast(getviewcolumnbynameandordinal(`tmpvw1`, TestCol, 0, 1), StringType) AS TestCol#691] +- 'Project [*] +- 'UnresolvedRelation [IM, test], [], false"   In PySpark, it works fine. The current workaround is to encapsulate the SQL code inside a PySpark code.    %%pyspark spark.sql(""" --insert SQL code below SELECT     * from     IM.test t1     left join     ref.testref t2     on t1.key= t2.key """).createOrReplaceTempView("tmp_python_view")   Could you please enable Spark SQL to create temporary views using tables with schema, just as PySpark does?   Thanks, Homan   ... View more

The ability to hide specific pages for a report based on the audience they belong too in a power bi app. ... View more

There are 12 posts regarding ward maps in Search - Microsoft Fabric Community. From what I know of Tableau, it displays ward maps very well, like this:  We tried using the Shape Map, but it lacks road information. We also tried Azure Maps, but it only shows the boundaries and doesn't allow us to fill the background of the wards. Is it possible to integrate OpenStreetMap into Power BI Desktop, or is there a similar native solution? Since we work in government, we are not permitted to use third-party tools. Thank you. ... View more

Please can we make it possible to unassign an item from a task in the medallion?      Reason for this idea is that this is not currently available.  This was discovered whilst adding items into the medallion,  and a few were accidentally assigned and therefore no longer needed.    It would be very helpful as we would like to assign other tasks but we are seeing tasks which are no longer relevant.    Thanks ... View more

Power BI currently does not provide a native DAX function that allows comparing month‑to‑date values with the same proportional period of the previous year. Existing time‑intelligence functions such as SAMEPERIODLASTYEAR, DATEADD, and PARALLELPERIOD always return the full month from the previous year, which creates inaccurate comparisons when the current month is still in progress. This limitation directly affects one of the most important analytical needs in business: measuring operational and commercial performance by comparing the same period across different years. For example, if today (or the last sales date) is May 13th, 2026, I need to compare: May 1st–13th, 2026 with May 1st–13th, 2025 However, SAMEPERIODLASTYEAR returns May 1st–31st, 2025, which makes the comparison invalid because the periods are not aligned. This prevents accurate performance evaluation, especially in sales, retail, finance, and operational monitoring. Additionally, when navigating future months (e.g., June 2026), Power BI still returns values after May 13th, 2025, which should not be included because the current year has no data beyond May 13th. Example of the measure I currently need to write to solve this manually: M_Margem_Vs_LY_partial = VAR MaxDataGlobal = CALCULATE ( MAX ( fSales[Data] ), REMOVEFILTERS ( dProdutos ), REMOVEFILTERS ( dSubCategoriaProdutos ), REMOVEFILTERS ( dCategoriaProdutos ), REMOVEFILTERS ( dLojas ), REMOVEFILTERS ( dLocalidades ), REMOVEFILTERS ( dPromocoes ) ) VAR MaxDia = DAY ( MaxDataGlobal ) VAR MaxMes = MONTH ( MaxDataGlobal ) VAR MaxAnoLY = YEAR ( MaxDataGlobal ) - 1 RETURN CALCULATE ( [sales], SAMEPERIODLASTYEAR ( dCalendario[Data] ), FILTER ( ALL ( dCalendario ), YEAR ( dCalendario[Data] ) = MaxAnoLY && MONTH ( dCalendario[Data] ) <= MaxMes && NOT ( MONTH ( dCalendario[Data] ) = MaxMes && DAY ( dCalendario[Data] ) > MaxDia ) ) ) This measure works, but it is long, complex, hard to maintain, and not intuitive for most users. A native DAX function would solve this elegantly. Proposed Solution: Introduce a new DAX function such as: PARALLELPERIOD_MATCHDAY( <measure>, <reference_date>, [<offset_years>] ) This function should: Automatically align the previous year’s period to the same day of the current month Prevent returning dates after the last available date of the current year Support month, MTD, and YTD contexts Enable accurate performance measurement for the same period across years Eliminate the need for complex manual filtering Improve accuracy and usability for real‑world business scenarios Benefits: Accurate year‑over‑year performance evaluation Cleaner and simpler DAX Better performance Easier adoption by analysts and business users Reduced risk of incorrect calculations in executive dashboards Example:     ... View more

When deploying notebooks across workspaces via Fabric deployment pipelines, the attached environment does not adapt to the target workspace. I have to manually reconfigure each notebook after every deployment, which is error-prone.   My current setup is simple with 2 workspaces: Dev workspace → small capacity, notebooks run on the Starter Pool Prod workspace → large capacity, notebooks run on custom pools After deployment from Dev to Prod, every notebook falls back to the workspace default, which isn't what I want in Prod - I need notebooks pointed at specific environment. I have to click into each notebook to repoint it.    Can we have deployment rules for this? Or is there something I can already do to avoid manual work?      ... View more

  Probably it's not the best practice, but I need to import a lot of staging/intermediate queries before I transform it into my final report. I don't want to load them in table view because these are just intermediate one, but I can only diasable them 1 by 1. When I shift select there's no option to disable load, can we enable the "disable load" option for multiple selected queries?     ... View more

When a report page contains multiple sections such as Sales, Finance, etc., providing expand and collapse functionality would help users easily view or hide all visuals within each section.     ... View more

It would be valuable if users could share screenshots directly within Data Agent conversations. In many real world business scenarios, users struggle to fully describe: report layouts visual filters slicer selections KPI discrepancies matrix structures chart anomalies expected results A screenshot often communicates the issue immediately and far more accurately than lengthy written explanations. Potential use cases: “Why does this KPI look incorrect?” “Why is this total different from the visual?” “Why is this measure blank in this matrix?” “Explain this trend shown in the chart” “Why is this location excluded?” This would greatly improve: troubleshooting user adoption contextual understanding support workflows analyst productivity Especially for Power BI/Fabric reporting environments where visuals, filters, and interactions are critical to understanding the question. ... View more

Currently, Data Agents primarily rely on semantic model metadata and instructions. It would be highly valuable if thin reports could also be attached or referenced by the Data Agent. This would allow the agent to: reference validated business visuals understand report-level filters and slicers verify measure usage understand intended business context align responses with officially published reporting reduce incorrect or inconsistent measure selection Thin reports often contain: curated business logic approved visual layouts operational context measure combinations hidden assumptions not obvious from the semantic model alone Having access to thin reports could help the Data Agent better ground its responses and reduce inconsistent outputs. Example benefits: “Use the Monthly Dashboard as the source of truth for KPIs” “Verify measure and filter logic against the operational report” “Reference the published performance report when answering questions” This could significantly improve: answer reliability consistency trustworthiness explainability alignment with production reporting These enhancements would help Fabric Data Agents evolve from semantic model query assistant into more context aware enterprise analytical assistant. ... View more

For both activities and pipelines, users should be able to configure email notifications when the execution time exceeds a specified threshold. This would help users detect workflows that are taking unexpectedly long before they time out, allowing them to investigate and address potential issues proactively. ... View more

Currently, when .pbip report layout files (pages, visuals, config JSON) are modified externally by automation tools or scripts, Power BI Desktop does not detect or apply those changes while the file is open. The only workaround is to close and reopen the project — which severely breaks developer and automation workflows. Suggested behavior: Power BI Desktop should watch the open .pbip folder for file system changes and auto-reload, similar to how Visual Studio and VS Code handle externally modified files. This would be a significant improvement for developers building tooling, CI/CD pipelines, or automation layers on top of the .pbip format. ... View more

Problem When customers open Fabric ontology for the first time, they face a blank canvas. They have to design entity types, properties, relationships, and naming conventions from scratch — often without a clear reference for what "good" looks like in their domain. This design phase alone can take weeks of workshops before any technical work begins. For most enterprises, the patterns are well-known — a retail ontology has Customer, Product, Order, Store, Inventory; a manufacturing ontology has Asset, WorkOrder, Site, Material. Customers are reinventing the same models, slowly and inconsistently. What would help Ship a starter library of sample / template ontologies for common industry domains: Retail Manufacturing Supply Chain Financial Services Healthcare Sustainability / ESG HR / Workforce Sales / B2B Even read-only reference templates (entity types, properties, relationships, sample queries) would be valuable. Importable starter ontologies that customers can instantiate and then bind to their own data would be even better. Microsoft already has this domain expertise through Common Data Model, Dynamics 365 industry data models, and Industry Clouds — extending those into Fabric IQ would be a natural fit. Why it matters Removes the "blank canvas" problem and shortens design time from weeks to hours Provides Microsoft-validated patterns customers can trust Accelerates Fabric IQ and data agent adoption — a templated ontology plus Copilot can produce a working agent in a day Impact Templates lower the barrier to entry for ontology, especially for customers who know their data but aren't sure how to model it semantically. Combined with stronger creation paths (automation from lakehouse), this would make Fabric IQ approachable for any enterprise, not just those with existing semantic modeling expertise. ... View more