Dear Product Group,   I would like to see more documentation and/or a data entry screen for options that are commonly used for on-premises connections.  For instance, "trust server certificate" used to be a check box in ADF, linked services dialog box.   Now, I have to use AI to find the right configuration file to enter the name of the server to trust as a tag value.  Please see image below for AI information plus configuration file entry.   Sincerely   John Miner Data Platform MVP   configuration file:                         ai search:         ... View more

Add support for JDBC connection to a spark session using simba a driver. Livy API is not scalable for submitting multiple spark sql queries for workloads like dbt. ... View more

It would be benefiicial to add the option to provide examples queries in Data Agents with sematic models as data source, the same way as it is done for the Lakehouse/Warehouse data sources. ... View more

We have three security permissions on the on-premises data gateway: Admin, Connection creator and Connection creator with sharing. We would request for an API to retrieve the user's security permissions from the "Manage Users" section of the on-premises data gateway.  ... View more

Within Power Bi Service all bookmarks are viewable to end users via the bookmarks button and "show more bookmarks". Need ability to hide specified bookmarks like we do with filters.    ... View more

Currently, when creating Table or Matrix visuals in Power BI, columns and rows do not automatically adjust to fit the visual container size. This requires manual resizing, which is time-consuming and often leads to distorted layouts when data changes or grows. Proposed Enhancement: Add an option for dynamic auto-adjustment of column widths and row heights based on the visual’s container size. Ensure this feature works responsively when data updates or when the report is viewed on different screen sizes. Allow users to toggle between manual and auto-adjust modes for flexibility. Benefits: Saves time by eliminating repetitive manual adjustments. Improves readability and consistency across dashboards. Enhances user experience for responsive layouts ... View more

Currently, in Power BI, if you filter out a row in a matrix visual, its values are excluded from totals and other calculations. This creates challenges when you want to hide certain rows (e.g., blanks or intermediate categories) for presentation purposes but still keep their contribution to totals. Proposed Enhancement: Add an option in matrix visuals to hide rows without removing their data from aggregations. Allow users to mark rows as “hidden” while totals and grand totals remain accurate. Optionally, provide a toggle for “Adjust layout automatically” so the matrix resizes and recalculates visual space when rows are hidden. Benefits: Cleaner reports without losing data integrity. Better control over presentation for executive dashboards. Avoid complex DAX workarounds (BLANK() measures, conditional formatting). ... View more

In Lakehouse, there are many tables under dbo. Some are linked to dataflows, some are just created via SQL, Excel, ... etc. I want to know the source of each table in lakehouse. Because at the end in lakehouse, there will be so many table, and it will be convienent which is coming from where. ... View more

The automatically generated title page it not useful for me.  I have created a page to act as a title and want to remove the auto generated one. ... View more

Hi,   I would like to see the option to stick the Canvas Background image to the top. Usually, we create backgrounds for reports that already include specific elements, like the logo, slicer bar, menu bar, that kind of thing. Which really works as long as you create the background to the same size of the canvas:   If I want to create a page that is very long (for reasons), I don't want to create a new background, and I really don't want to use the stretch option which kills the way it looks:   Fit would be great (Changing the color to my actual color in the image), but now it's in the middle of my report, and I want it to stay at the top.  Any ideas or solutions would be welcome ... View more

Preview feature options are showing in local language set in laptop instead of showing the options in the language set in application level in Power BI desktop. This needs to be changed the preview features must be shown in language which is set by customer in Power BI desktop instead of considering the languag used in local machine. ... View more

For the reports using Visualize your data quickly from Power Apps/ Dynamics 365 apps feature should be able change the visual type. ... View more

Introduce an “Export Visual Data as Rendered” option that guarantees the exported dataset matches the visual exactly, including all applied filters, measures, and formatting. ... View more

The Specific Workflow: This request is about the "Publish" workflow from the Power BI Desktop application when a developer overwrites an existing dataset in the Power BI Service. The Business Goal for Enterprise Governance: As analytics leaders, we work to enforce strong governance by using secure, non-personal identities (Service Principals) for data source credentials. This is a best practice for ensuring security, compliance (e.g., SOX), and operational stability in our finance analytics environment. The Current Challenge: The current behavior in this specific workflow creates a significant challenge for this governance model. When a developer clicks "Publish" from Power BI Desktop to update an existing dataset, the service: Assigns dataset ownership to the human "publisher" (the user logged into Power BI Desktop). This ownership change often leads to the invalidation of the existing data source credentials, even if they were correctly configured to use a Service Principal. This then requires the developer to manually go to the Service, "take over" the dataset, and re-enter credentials. The Impact on Enterprise Adoption: This behavior creates friction for teams trying to follow best practices: Hinders Automation: A single manual publish from Desktop can disrupt scheduled refresh chains that rely on the Service Principal, causing data non aggiornati. Creates Compliance Friction: It inadvertently encourages developers to use their personal credentials (which are not invalidated on publish), simply to avoid this issue. This undermines the goal of using secure, governed Service Principals. Adds Operational Overhead: It adds a manual, error-prone step to what should be a simple update process. Suggested Enhancement: We would welcome a mechanism to decouple the Power BI Desktop publisher from the ownership of the data source credentials. Ideally, when a user clicks "Publish" from Power BI Desktop to an existing dataset, the service should: Detect that functional credentials (especially for a Service Principal) are already set. Preserve these existing credentials by default, allowing them to remain active. The publisher's identity should not automatically override the credential ownership. The Service Principal should remain the owner of its credentials. This enhancement would be a major step forward in aligning the core Power BI Desktop workflow with the enterprise-grade security and governance practices that Microsoft also champions. ... View more

Driving global climate action with data, AI & Microsoft Fabric Organizations worldwide face pressure to cut emissions, adopt clean energy, and meet ESG standards — but sustainability data remains siloed, inconsistent, and hard to audit.    Idea A universal AI-powered Sustainability & Carbon Intelligence Hub built on Microsoft Fabric to automate environmental data collection, tracking, intelligence, and ESG reporting. Key Capabilities Automated Carbon Footprint Calculation Scope 1, 2, 3 emissions from energy, transport, supply chain & operations. Satellite + IoT Emission Monitoring Satellite Earth-observation + sensor data for real-time carbon and air-quality analytics. AI Emission Forecasting & Reduction Planning Predict emissions, recommend sustainable actions, simulate reduction pathways. ESG Reporting Automation Compliance-ready reporting for GRI, CDP, ISO, EU CSRD & global frameworks.    Global Use Cases Multinational enterprises Government climate & environmental authorities ESG auditors & sustainability consultants Smart cities & renewable energy programs NGOs & academic research institutions   Impact Reduce carbon emissions Increase climate transparency Accelerate sustainable business transformation Promote circular economy practices Use AI responsibly for global climate goals   Microsoft Fabric Capabilities Used OneLake for unified sustainability data lake Data Engineering pipelines for satellite + IoT data Real-Time Hub for pollution monitoring streams AI models for carbon forecasting & recommendations Power BI ESG dashboards & audit reports Fabric governance for compliance & security Vision Make sustainability measurable, actionable, and accountable — at a global scale. ... View more

Idea A built-in Fabric feature where users can enable Data Quality Watch for any dataset, with automated monitoring — no code required. 🔧 Key Capabilities 📊 Quality Rules — Auto & Custom Missing values detection Duplicate record checks Data type & schema drift detection Out-of-range / threshold alerts Primary key & foreign key validity Distribution shift detection Nulls in key business fields (e.g., CustomerID, Amount) Option to add custom rules using DAX or Power Query UI 📈 Data Quality Score A model-wide 0–100 score calculated based on: Completeness ✅ Accuracy ✅ Consistency ✅ Validity ✅ Timeliness / Freshness ✅ Display score trend over time Highlight areas with most impact on score    Automated Insights Copilot explains findings: "Column email has 8% invalid values — common typo patterns detected like .con, missing @." "Sales amount shows extreme values, likely data input error." Real-Time Alerts Email / Teams notification Power BI alert integration Fabric event triggers for pipeline correction Example alert: "Customer table completeness dropped to 94%. Null customer IDs detected in last batch."    Wizard Setup User clicks: Enable Data Quality → Select Rules → Schedule → Save No coding, just UI dropdowns: Frequency: hourly / daily / per refresh / live Sensitivity levels   Self-Learning Rules System suggests rules based on historical data patterns: "Phone number pattern inconsistent" "New values seen in Country column — check validity"    Auto-Fix Recommendations Not just alerts — intelligent suggestions: Issue Recommendation Missing product names Fill using lookup table Outlier sales values Flag for review Wrong date format Standardize automatically   Output A Power BI-like dashboard showing: Data quality score Trend line Failed rule summary Affected tables & rows Suggested fixes Last check & next schedule   Benefits Problem Today Feature Fix Manual data quality scripts One-click automated quality checks Hard to detect silent data issues Alerts + score + trend Late discovery of bad data Freshness & schema drift monitoring Tech-heavy validation Low-code, business-friendly UI   Future Enhancements ✅ ML-based anomaly detection at refresh ✅ Data quality benchmarking by industry template ✅ Export rules as YAML / JSON ✅ Integration with Fabric Data Pipeline error handling ✅ Score impact synced to Lineage View & Workspace Health   LinkedIn-Ready Caption Building reliable analytics starts with clean data. Fabric needs a Low-Code Data Quality Monitor that gives every dataset a Health Score, auto-detects errors, alerts users in real-time, and recommends fixes. Data quality shouldn't require scripts — it should be as easy as turning on Power BI refresh. ... View more

When adding columns to a Matrix I always want the headings to align above the numbers ( i.e. to the right ).    This should be the default in my view Per bottom visual of screenshot   ... View more

Power BI Workspace Application Audience Limit Increase   Customers that support reports for many lines of business within a single workspace would significantly benefit from an increase in Application Audiences from the current 25 to at least 50 (or more 🙂 ). Please.   Thank you! S Dot ... View more

Power BI is unexpectedly and erroneously forcing a CAST operation on specific numeric keys (NUMBER(19,0) / Whole Number), converting them to BIGINT within the generated SQL sent to Snowflake.   We have already opeend a support ticket on this.  Below is the contents of that ticket.   Summary:  We initially connected over a Teams meeting and discussed your use of Snowflake as a data source, which you connected to Power BI Desktop via the Snowflake connector.  Power BI is applying a CAST operation on specific numeric keys (NUMBER(19,0) / Whole Number), converting them to BIGINT within the generated SQL sent to Snowflake.  You have three columns: "CARRIER_KEY_BIGINT," "CARRIER_KEY_NUM19," and "CARRIER_KEY_VARCHAR." The data type for "CARRIER_KEY_BIGINT" and "CARRIER_KEY_NUM19" is set to "Whole number," while "CARRIER_KEY_VARCHAR" is set to "Text."  When a 19-digit number is entered in each column, the "CARRIER_KEY_VARCHAR" column displays the data correctly, but the "CARRIER_KEY_BIGINT" and "CARRIER_KEY_NUM19" columns round off the last three digits.  We reproduced the issue on our end by pulling data from SSMS (Data source), and when the data type is "Whole number," the last three digits are also rounded off.  Our Engineering team has confirmed that this is expected behavior. ... View more