Enhance Power BI with Advanced AI-Powered DAX Optimization and Performance Monitoring
Description I would like to suggest introducing advanced AI-powered DAX optimization and performance monitoring capabilities directly into Power BI. As Power BI solutions become more complex, developers often spend significant time identifying inefficient DAX measures, optimizing queries, troubleshooting slow visuals, and improving report performance. An AI-powered optimization assistant could help developers automatically identify performance bottlenecks, recommend optimized DAX expressions, detect unnecessary calculations, and suggest improvements to data models. Key Proposed Features AI-Powered DAX Optimization: Automatically analyze DAX measures and recommend optimized expressions. Performance Monitoring: Identify slow-running queries, visuals, and inefficient calculations. Smart Recommendations: Provide actionable suggestions to improve report performance. DAX Explanation: Explain complex DAX expressions in simple language. Automated Error Detection: Identify potential DAX errors and recommend corrections. Query Optimization: Recommend improvements for Power Query and data model performance. Performance Insights Dashboard: Provide a centralized view of report performance and optimization opportunities. Business Value These capabilities could significantly reduce development time, improve report responsiveness, simplify troubleshooting, and help Power BI developers build more scalable and efficient analytics solutions. Expected Impact This enhancement would benefit Power BI developers, data analysts, BI engineers, and organizations working with large and complex datasets. Bringing AI-powered DAX optimization and performance monitoring directly into Power BI would make analytics development smarter, faster, and more accessible.
Add a run-level failed jobs view to the new Monitoring hub
The legacy Monitoring hub allows users to filter individual pipeline runs by Status = Failed within a selected period. In the new Monitoring hub, pipelines with an earlier failure does not appear if their latest run succeeded as the document says "The new Monitoring hub provides a table view of your pipeline items and their recent execution health. " Please add a run-level view or an “Any failed run within the selected period” filter. This would help users quickly identify failed jobs without opening the Run history of every pipelineEnhance Microsoft Fabric Learning with Real-World Projects and Hands-On Practice
I would like to suggest introducing more hands-on learning resources, real-world projects, and practical exercises across Microsoft Fabric. It would be beneficial to have: More end-to-end Microsoft Fabric projects. Advanced SQL, PySpark, and Data Engineering challenges. Real-world Power BI and Direct Lake scenarios. More DP-600, DP-700, and DP-800 exam preparation resources. Interactive exercises with step-by-step solutions. Dedicated learning paths for beginners and experienced professionals. These improvements would help community members strengthen their practical skills, prepare for Microsoft certifications, and become industry-ready. Thank you to the Microsoft Fabric team for continuously improving the community and learning experience.
Restore PNG snapshot attachments in Power BI report subscriptions
Microsoft recently migrated Power BI report subscriptions to a new email delivery platform. As part of this change, report snapshots are no longer delivered as separate PNG attachments and are only embedded in the email body. Why this matters: Many organizations relied on PNG attachments for: Archiving and auditing reports Forwarding snapshots to external systems Document management systems Automated workflows and integrations Saving report snapshots without requiring access to Power BI Weekly and monthly management reporting Embedded images inside the email body are not an equivalent replacement because they cannot be processed as easily by automated systems and are more difficult to store and reuse. Business impact Organizations using Power BI Pro without Premium or Fabric capacity currently have no alternative way to receive report snapshots as image attachments. Restoring this capability would help many existing customers continue using established reporting and automation processes without additional licensing costs.
Add a built-in “Allow Direct Manager Access” option for RLS
Hello, Please consider adding a built-in RLS option in Power BI / Fabric to allow direct manager access based on the existing organizational hierarchy in Microsoft Entra ID / Azure AD. This is a very common business scenario. Today, customers usually need to build custom manager-to-employee mapping tables or ETL processes just to support manager access to direct reports. A simple option such as “Allow Direct Manager Access” or “Include direct reports” in RLS setup would help reduce custom development and make security easier to manage consistently. Ideally, the feature would: * use trusted Microsoft identity hierarchy data * be secure and auditable * support manager access to direct reports * remain optional for organizations that do not want it Thank you for considering this enhancement.
Synchronize Open Item Tabs Across Microsoft Fabric Browser Tabs
Description When working in Microsoft Fabric, I often have multiple browser tabs open at the same time. Each browser tab appears to maintain its own state of recently opened Fabric items. For example, if I have many items open and close some of them in one browser tab, those items can still remain open in my other Fabric browser tabs. As a result, I repeatedly have to clean up the opened items in each browser tab individually, or close all Fabric browser tabs and start again. This significantly disrupts the user experience, especially for users who regularly work across multiple Fabric items and browser tabs. Suggested Improvement It would be helpful if Microsoft Fabric could synchronize the state of opened/closed items across browser tabs. If an item is closed in one Fabric browser tab, ideally that state should be reflected in the other open Fabric browser tabs as well. Additionally, please consider whether Fabric needs to automatically retain recently opened items when the user has already closed them. If an item is needed again, users can access it through the available navigation. User Impact The current experience can lead to: Repeatedly cleaning up the same opened items across multiple browser tabs. Interruptions when trying to open another Fabric item from navigation or a shared link. Having to close existing browser tabs and restart the working session simply to get back to a manageable state. Additional friction for users who frequently work with multiple Fabric artifacts simultaneously. Synchronizing the open-item state across browser tabs, or providing greater control over whether recently opened items are retained, would make the Fabric experience significantly smoother and more productive.
Display the Business Names in Power BI report when using ODBC connection to connect to Datasphere.
Currently we are only able to see the technical names displayed in Power BI when the Datasphere report is exposed to Power BI using the ODBC connection. It would be better if we have the option to display the Business Names from Datasphere Graphical views to make sure the renaming on the same can be ignored in Power BI .
Allow multi-column conditions /output in Power BI Activator rules (Power BI visual-based alerts)
Description: When I create an Activator alert from a Power BI report visual, the rule can only evaluate the single column or measure it was created from, and the alert can only reference that same value. This blocks common governance and monitoring scenarios. Example scenario: I wanted an alert for Dev workspaces that sit on a billable (Premium/Fabric) capacity. That needs a condition on both Workspace Name (contains “Dev”) and Capacity/Billing type (not blank). Activator can’t combine the two in one rule, so I had to build the alert in Power Automate with a DAX query instead. Limitations: A condition can use only one column or measure, with no AND/OR across several attributes. The alert message or action can include only that same column. I can’t add related details like workspace name, dataset link, or owner. There’s no way to run a DAX query as the rule logic. Requested improvements: Conditions across multiple columns/measures (AND/OR). Selectable output fields, so the Teams or email action can include several columns, and dynamic links. Optionally, the ability to define the trigger with a DAX query, as the Power Automate “Run a query against a dataset” action does. Impact: Without this, governance and monitoring alerts need a separate Power Automate flow, which is harder to build and maintain than a native Activator rule.📉 How Would You Investigate a 20% Drop in Revenue?
A data analyst shouldn’t stop at identifying what happened. The real questions are: Where did the decline occur? → Why did it happen? → What caused it? → What should we do next? By analyzing regions, products, customers, time periods, and key business metrics, raw data can reveal the root cause behind the numbers. Good data analysis turns numbers into decisions. 📊 #DataAnalysis #BusinessIntelligence #PowerBI #MicrosoftFabric #DataAnalyticsBuilt a free tool to inventory & risk-rate legacy SSIS packages before a Fabric migration
Hi all, Sharing something I built that might save some of you the painful "open every .dtsx in SSDT one by one" phase of an SSIS → Fabric migration. The problem it addresses: most teams sitting on a legacy SSIS estate have dozens to hundreds of undocumented packages and no clear starting point. Before any actual migration work, someone has to answer: what does each package do, which components map cleanly to Fabric, and which need a full rewrite? What it does: Parses .dtsx package XML and extracts control flow tasks, data flow components, connection managers, variables, and precedence logic Maps each component against a Fabric equivalent — Data Flow Task → Dataflow Gen2, Execute SQL Task → Script/Stored Procedure Activity, Script Task → Notebook Activity, Foreach Loop → ForEach Activity, and so on Gives each package a Low/Medium/High risk rating based on concrete signals (Script Task usage, Fuzzy Lookup, deprecated CDC/Attunity components, nesting depth, dynamic connection strings) Flags every component individually as auto-mappable or needs-manual-redesign, not just the package as a whole Across a batch of packages, produces a portfolio rollup: risk tier counts, the blockers showing up across the most packages, deprecated components flagged separately, and a suggested migration order What it's built as: a Claude Skill (Anthropic's Claude AI), with the actual XML parsing done by a plain Python script with zero dependencies — not an LLM guessing at package structure. It's designed to run fully offline, no live Azure/Fabric API access assumed, though it flags anywhere that access would improve accuracy (resolving a dynamic connection string, for example). What it deliberately doesn't do yet: this covers the Inventory/Classify phase only. It won't draft actual Fabric pipeline JSON or claim a package is production-ready — every future draft artifact gets an explicit DRAFT/NEEDS REVIEW label. I'd rather it under-claim than over-claim. Repo's on GitHub with a sample package and example report included, so you can see the actual output before running it against your own packages: https://github.com/HBBH11/ssis-fabric-migration-assistant Genuinely interested in feedback from people who've done these migrations for real — particularly whether the risk heuristics hold up against messier packages than my test case, and whether the Fabric equivalence mappings match what you've found in practice. Happy to take suggestions on what a Phase 2 (draft pipeline generation) should prioritize too.
