At present whenever I am refreshing the data or applying change & that is resulting into data reload, I can view that data is loading however not able to view what time it STARTED, for how long it is running(Duration) etc.   Showing the Start time, Duration would be useful information to see in PBI Desktop refresh. ... View more

There should be an option to copy the cell data when we see any visual's data by clicking on more option > Show as a table. Currently there is no option to copy the data. In the chart visuals we can not copy the dimension values. So, when we go to Show as a table option it does not allow to copy the data. ... View more

Similar to Managed VNET integration, also allow Customer VNET integration. Both for Spark and Python workloads.   Would unblock the requirement of PLS. ... View more

Currently, Microsoft Fabric deployment pipelines do not support Fabric Data Agents, which limits our ability to fully automate deployments of the Fabric Data Agents We have also reached out to Microsoft support regarding this issue. Currently its not in the plan, It would be helpful is this feature is enabled.  ... View more

In Power BI, when using a slicer with "Select All" enabled, newly added values are not automatically selected. This causes confusion and requires manual maintenance, especially in dynamic datasets. It would be very helpful to have an option like "Always include new values" or "Dynamic Select All" so that slicers can automatically reflect all current values without user intervention. This would improve usability and reduce the risk of missing data in reports. ... View more

Fabric DirectLake method with D365 FnO table requires multi columns (for eg, CustID + DataAreaID) as Power BI semantic model relationship, is this possible? Customer - Assa Abloy  ... View more

I am requesting that capacity admins be able to set multiple notificaiton levels for when CU usage its a threshold. Right now we can set one threshold, but it would be helpful if we could set 2 or 3. Getting a notification at 50%, then at 65%, then at 80% would be helpful.  ... View more

1) Problem & Goal IoT Hub emits non-telemetry events (for example, device twin change events and digital twin change events). Today, when those land in Fabric Event Streams, operators still have to manually wire model context into the Fabric Digital Twin. We want this to be automatic: whenever IoT Hub sends a twin-related event, Fabric should (a) create or update the Digital Twin in the Digital Twin Builder, and (b) map reported properties onto the twin instance.   Out-of-the-box for DTDL/Plug-and-Play; extensible to other digital twin standards. This enables operators to click an “interesting event” (e.g., an alarm) and immediately review the twin’s configuration/state as-of that event, then run graph queries (GQL) in Kusto to understand blast radius and impact paths. IoT Hub supports routing these event types; Event Streams already integrates those sources and routes to Fabric destinations. 2) User Scenarios Scenario 1: Operator reviews an alarm with Digital Twin context An operator is monitoring a fleet of refrigeration units across multiple retail stores. During normal operations, temperature sensors and compressor controllers send telemetry to IoT Hub. One evening, an alarm event is triggered because the temperature in one of the refrigerated cases exceeds its safety threshold. The event is routed through Event Streams into Fabric. From the event card, the operator clicks “Open twin at event time.” The Digital Twin Builder opens a snapshot of the twin representing that refrigeration case. The operator sees: Reported properties such as last measured temperature, compressor cycle count, and defrost configuration. Desired properties (e.g., target temperature range) for comparison. Device metadata (firmware version, component models) tied to the DTDL model. By reviewing this historical snapshot, the operator determines that the configuration was correct, but that the compressor reported longer duty cycles than expected. They then use graph queries (GQL in Kusto) to determine the blast radius, checking which other refrigeration cases depend on the same power supply or share the same controller vendor. Scenario 2: Integrator onboards Plug and Play (PnP) devices automatically An integrator is tasked with connecting a new set of HVAC controllers with published DTDL models. The devices report configuration and operational data (airflow rates, fan speeds, filter status) as reported properties to IoT Hub. As soon as the devices connect, IoT Hub issues digital twin change events. Event Streams forwards these to the Digital Twin Builder, which automatically: Creates twin instances for each HVAC controller. Maps reported properties to the appropriate DTDL properties without manual mapping. Establishes relationships between HVAC controllers and their associated rooms/zones. The integrator verifies in Fabric that the twins are present and complete. No manual schema mapping was needed. They also test by raising the fan speed in a controller and confirming that the updated reported property appears immediately in the twin. Later, when building a system dashboard, the integrator queries across all HVAC twins to check which units are overdue for filter replacement. This is possible because reported properties were consistently mapped and stored as part of the digital twin. ... View more

Hello everyone,  I had some fun working on two projects and thought I share this idea, I was working on a copilot agent that can access and read from power bi semantic model and the other one was a Q&A visual in a power bi report and at that time I wished that if there was visual that integrate copilot studio agent with power bi like  just like Q&A but more of interactive human language like the Copilot experience but fucos on the exact dataset, not sure if this planned but I would love to see it happen. ... View more

1) Summary When connecting Azure IoT Hub to EventStreams, incoming telemetry often has heterogeneous schemas across device types and firmware versions. This idea proposes a Schema Validator with an optional Catch-All Designer and "Digital Twin"–aware validation. The validator enforces known schemas at ingest time, highlights nonconforming payloads live as events arrive, and gives designers a guided tool to reconcile unknown/invalid payloads into versioned schemas. 2) Problem & Why Now Heterogeneous telemetry: Multiple device types, firmware versions, and vendor payloads result in inconsistent data shapes. Hidden drift: Schemas drift over time; without validation, breaking changes surface late (downstream parse errors, bad analytics). Slow developer loop: Missing/invalid fields discovered hours/days later via failed jobs. No single source of truth: Current flows lack a managed registry binding data models to devices/twins. Impact: Increased MTTR for ingest issues, brittle pipelines, and higher integration cost for OEMs and system integrators.   3) User Scenarios Scenario 1: Developer Onboarding New Device A system integrator connects a new OEM device. The device emits telemetry with fields not yet modeled. The Schema Validator routes unknown payloads to the Catch-All queue. The Designer tool clusters these payloads, allowing the integrator to: Infer a candidate schema. Bind it to a digital twin model. Promote it as a new version. This shortens onboarding time and prevents breaking downstream jobs. Scenario 2: Schema Drift During Rollout An existing device fleet receives a firmware update. Telemetry changes: field names differ and a new property is added. The validator flags these as invalid. In the Catch-All Designer, the operator compares the differences, creates a new schema version, and maps the rollout population to the updated version. Because the Catch-All stores payloads even after live data expires, errors can still be fixed retroactively. Scenario 3: Live Debugging of Integration During integration testing, a developer uses "Live Stream Data in EventStreams". As telemetry arrives, invalid fields are highlighted inline with validation diagnostics. This instant feedback allows the developer to correct mappings without waiting for batch jobs to fail. ... View more

Rationale Currently, while designing transformations and actions in EventStreams Fabric, the tool queries static or cached data. Operators can refresh manually to see new rows, but this does not reflect real-world telemetry scenarios where data may arrive irregularly and suddenly. Operators need visibility into this changing data context as it happens. Introducing Live Stream Data into EventStreams Fabric provides a continuous data feed view, allowing operators to design and test transformations on evolving data, ensuring readiness for real-time operational use cases. Scope This idea introduces the ability to: Display a live data preview viewer inside the design environment, with raw data without applying a schema. Continuously update rows in real time as telemetry data arrives. Allow an operator to select a particular row and either: Apply an existing schema to it, or Ask the system to auto-infer a schema for new transformations. This capability does not replace existing refresh and batch query functionality; it augments it with real-time interactivity for scenarios requiring immediate insight. User Scenarios Scenario 1: Emergency Telemetry A firetruck sends regular telemetry (engine temp, fuel, GPS). During a live drill, new alarm signals appear. Operators use the live preview to detect new fields, select them, and quickly apply schema inference. Scenario 2: IoT Device Rollout During onboarding of new devices, unexpected fields arrive in telemetry (e.g., new firmware versions or error codes). Operators select rows in the live feed, trigger auto-schema inference, and extend the transformation pipeline on the fly. Scenario 3: Business Monitoring In a retail environment, live telemetry streams from devices (POS systems, sensors) are monitored. When special events occur (e.g., promotional triggers), operators test new actions against these events directly in the live feed preview. Benefits Faster design of new data conditions without waiting for refresh cycles. Improved schema agility when unanticipated telemetry arrives. Debugging: Enhanced operator confidence by visually validating live events during transformation design. ... View more

Currently complext type (json, struct) are supported in Onelake endpoint but not in SQL endpoint which prevents these important payload data types to be explored or used in Power BI. In big data world such fields are very common as many data generated through IoT are partially parsed in individual columns and raw json payload is left for future use or as on need basis. Before parquet - we use to store them as MapType which make them easy to further use. Adding this feature will do both - parsing those field easy for end user and also migration of existing data possible. ... View more

It would be amazing if users would be notified in the notifications (the small ring icon) when an outage or degradated mode is happening. ... View more

I'd like to be able to specify the default expected number format for numeric columns (US / EU formatted decimal fields in files). When the decimal format can be passed to the openrowset statement like with date format CSV data can be import directly in the right datatypes, even when sometimes the decimal format is US and sometimes EU format (point vs comma.   Setting a default on session level works for the most, but in mixed cases (same within one file, but different between files), passing the right format to be expected would solve this problem.      US Decimal Format  Decimal Separator: Period (.) Thousands Separator: Comma (,) Example: $300.10 is three hundred and ten cents. 12,345.678. EU Decimal Format  Decimal Separator: Comma (,) Thousands Separator: Period (.) or space ( ) Example: €300,10 is three hundred euros and ten cents. 12.345.678 or 12 345 678 ... View more

Please extend the Excel export from visuals up to more than 150.000 rows. It is very frustrating to create every time a workaround to do this. 95% of the users in our company want to export data to excel. ... View more

Currently, Git integration for warehouses in Microsoft Fabric does not support service principals. This limitation makes it challenging to implement secure, automated, and scalable CI/CD pipelines and automation solutions. Using user based authentication introduces risks and operational overhead, particularly when managing long term processes, rotating credentials, or ensuring compliance with enterprise security policies. Service principal support would allow for: More secure authentication aligned with enterprise identity and access management practices. Reliable automation of CI/CD workflows without dependency on individual user accounts. Improved governance and auditability. etc. References: https://community.fabric.microsoft.com/t5/Fabric-platform/Unable-to-Deploy-Warehouse-via-Fabric-API-Automation/td-p/4784277 https://learn.microsoft.com/en-us/fabric/data-warehouse/service-principals#limitations Without service principal support, warehouse Git integration remains inconsistent and less reliable for CI/CD automation. Adding this capability would significantly improve adoption in enterprise environments and strengthen trust in Git enabled workflows.   ... View more

I have a pipeline that uses parameters.   I would love being able to use variable library to set the default value of a parameter. ... View more

If you have some measures based on choice of user un a slicer (like "Show today"/"Show another day") then you can make visualisations based o user choice.  What, if you want base on this choice bookmarks, as well?  Scenario:  User change something in a slicer -> measures are recalculated, and bookmark is changed as well (to show/hide sth).    This is why we need slicer with functionality od changing bookmarks. ... View more

Clearly the number of Notebooks/Pipelines that are going to be open is going to be higher than the number of Workspaces   Therefore it would be far more logical to have these in the vertical list and the workspaces in the horizontal list   ALSO - you should just be able to click the Workspace name and it takes you back to where you were - rather than having to click to expand then click the folder then click the sib folder ... View more