While AI Insights support is available in Dataflow Gen1, it is currently not supported in Dataflow Gen2. Since enabling AI Insights in Dataflow Gen2 would make it a more useful tool, we propose this as a feature improvement. ... View more

Add targets within the Pins dashboard. currently shows growth unit and pins but nothing in relations to targets.  ... View more

We are in the process of on boarding a new supervisor and changing schedules around at our Smuckers/Palumbo site. Per Tyler Abbot, he wanted us to submit for this change here.   Current Assignments: First Shift - Paula Mcnally Second Shift - Jason Bush Weekend Shift - Michael Feller   Needed Changes: First Shift - Michael Feller Second Shift - Will Hicks Weekend Shift - Jason Bush   Let us know if you need anything from our end. These changes have already occured in the LMS environment.   Thank you! ... View more

A Drill-Down action that expands the heirarchy of a Matrix table - this can be used to configure a button. Currently, the drill-down buttons are very hard for users to see/navigate to in the Web.  ... View more

See Attached Image. Quick Overview When working on large Power BI models, it’s easy to end up with 50, 100, or even more queries in Power Query. These come from all kinds of sources and transformation steps, and the list gets long fast. At that point, just finding the query you’re looking for becomes a real hassle. Right now, the only option is to scroll through the list manually—and in big projects, that’s just not practical. Why This Would Help Models grow quickly: staging queries, reference layers, intermediate logic—all stack up fast. Scrolling through a huge list every time to find a query breaks flow and wastes time. A simple search/filter option in Queries Pane would make it way easier to work efficiently, especially under deadlines. The Ask Would love to see a search bar added at the top of the Queries pane in Power Query. Just something lightweight to help quickly jump to a query by name. That’s it—nothing to do with loading data or transformations, purely about improving authoring experience. I've included a screenshot as well to help visualize the idea. ... View more

In the current configuration: Dataset is hosted in a Premium Per User (PPU) workspace. Report is deployed to an Embed Capacity (A1) for embedding into a website. This setup leads to inconsistent behavior due to resource governance limitations: Although PPU allows up to 100 GB per dataset, the semantic model memory limit in A1 capacity is capped at 1 GB. When the report accesses the dataset from PPU, the embed token generation process is constrained by the PPU capacity limits, resulting in failures and unreliable embedding. Additionally, this architecture causes inefficient license utilization: Internal users with PPU licenses are underutilized because the embedding relies on A1 capacity, not leveraging the full benefits of PPU. ... View more

Currently, it's confirmned that fabric operates in UTC. This causes issues when hosting few paginated reports which are time sensitive, causing confusion in the report audience. Should have an option to set the timezone in fabric so it matches with local time (like the option for subscription time zone) ... View more

Please do what you can to make EVERY connection type in Fabric support Service Principal authentication, AND make it so that the Secret (Service Principal Key) can be stored in an Azure Key Vault. Many Fabric solutions involve connections to other data sources inside an organization's data landscape. Right now, there is a mix of authentication types available to the various connections. Service Principals are great, but they secret has an expiration date. When that expiriation is met and a new Secret generated, EVERY connection that uses that Service Principal need to be updated. For a moderately sized solution, that could be several or dozens of connections. Needing to edit the Secret on each one is not sustainable. But by allowing the Secret to be stored in an Azure Key Vault, and making that Key Vault reference available in Fabric, now there is only ONE place to refresh that Secret and all (Service Principal) Connections can utilize it. ... View more

We are having issues inititiating the mirrored tables for large tables. There is very little info on the net about removing the timeout. It would be nice if that is not a restriction for seeding new large tables ... View more

I hope you're doing well. I wanted to check if it's currently possible to programmatically add goals to a Power BI Scorecard, either via APIs, PowerShell, or any other supported automation method. We're exploring ways to streamline our goal-setting process and integrate it with our internal systems. If this is supported, could you please point me to the relevant documentation or share any prerequisites we should be aware of? Looking forward to your guidance. ... View more

Some of us don't want to use Copilot (or even have a license to use it).   So why not make it OPTIONAL?! This includes the ability to HIDE all AI Features! ... View more

The current KPI card doesn't allow for a middle orange value. It's either green if the value is above target and red if it's below target. There doesn't appear to be the option to have a middle ground whereby, if the value is between the highest and lowest target then it can be orange - or some other colour.  This seems very binary and doesn't reflect how our business compares a value against benchmarks where we use RAG indicators a lot.  ... View more

The idea is very simple.  Power BI should allow users to sort the columns on a matrix visual, based on measures. The most straight foreward example would be to sort based on the grand total. So the column with the highest grand total should appear on the left (or right) and vice versa with the lowest grand total one. This feature is already implemented in Excel yet, power bi still won't allow it. ... View more

Currently, Power BI REST APIs allow automation of dataset refreshes, report updates, and workspace management. However, there is no API available to programmatically update or publish Power BI apps after changes are made to reports or datasets. This limitation creates a gap in CI/CD workflows and hinders full automation of Power BI deployments. Adding support for app publishing via REST API would: Streamline enterprise-level deployments. Reduce manual intervention. Improve governance and version control. Enhance integration with DevOps pipelines. Please consider adding this capability to empower developers and admins with a fully automated Power BI lifecycle. ... View more

I would like to propose an enhancement to the current Purchase Order (PO) Details Dashboard that would improve our workflow efficiency and data visibility. Suggested Enhancement: Please consider adding the following fields to the PO Details table: PR Number (Purchase Requisition Number) Ariba Request Number, and associated PO number PO Requestor Name Benefits: Enables quicker reference and tracking of prequests. Reduces the time spent cross-referencing data across systems. Improves accuracy. ... View more

There is currently a limit of 1,000 characters as a prompt. I would like this increased to 5,000 characters so that a complete prompt can be provided. ... View more

Feature Request: Page-Level Sharing in Power BI Reports In Power BI, reports often contain multiple pages (tabs), each built using different datasets or designed for different user groups. Currently, when we publish or share a Power BI report, all pages are accessible to the end user - there is no native way to restrict access to only a specific page. This becomes especially challenging when: Each page is connected to different datasets or has sensitive information. Different audiences require access to different insights within the same report. Maintaining multiple single-page reports for each group leads to redundant work and version control issues. This would greatly improve flexibility, reduce duplication, and support better data governance. @Miguel_Myers and @fbcideas_migusr, can you guys please share your ideas on this? ... View more

Hi Team, As organizations begin adopting Microsoft Fabric's Data Activator, we need centralized administrative visibility and control over reflexes (alerts) created across the tenant. Currently, there is Mechanisam to: Retrieve a list of all reflexes (Data Activator rules) Identify owners, workspace locations, trigger conditions Audit or manage usage at scale We request the introduction of Admin REST API endpoints or any other possible method that allow administrators to: List all reflexes across all workspaces Filter by workspace, owner, status (enabled/disabled) Export configuration details Detect inactive or duplicate alerts Monitor real-time activation logs (optional) This functionality is critical for enterprise adoption, governance, and automation in regulated or large-scale environments. Thank you ... View more

Currently it's not possible to recover a deleted Fabric Lakehouse.   Which is a big problem in case someone accidentally deletes a Lakehouse in Fabric.   Please make it possible to recover a deleted Fabric Lakehouse. ... View more