Eventhouses now support Git Integration, which is a great step forward. But when you look at what actually gets pushed to Git, there is an immediate version control concern: the entire Eventhouse definition is stored as one large .kql file. From a DataOps perspective, this is not ideal. Large monolithic files are difficult to review, hard to merge across teams, and almost always produce noisy diffs. When you look at more mature version controlled artifacts in Fabric, such as Power BI’s move to TMDL or the PBIR format, the direction is clear: break complex assets into smaller, structured, independent files. TMDL separates tables, measures, relationships, expressions, and roles into their own files. PBIR moved away from the single report.json and now stores each page and visual independently. This level of granularity makes teamwork easier, improves change tracking, and strengthens DevOps workflows. Eventhouse should follow the same pattern. Instead of one large script, the service could output a clean directory structure that separates tables, policies, ingestion settings, functions, and materialized views. This would: Make merges safer and easier Let team members work on different components without conflicts Improve the clarity of version history Support more consistent automation and testing patterns If Fabric adopted a multi file structure for Eventhouse artifacts, it would enable stronger collaboration across Power BI and data engineering teams and make Eventhouse a first class citizen in real DataOps workflows. ... View more

TLDR: use Github copilot inside Fabric instead of requiring a separate copilot capacity   My organisation already has existing Github copilot accounts, we use it in VS code, Visual Studio, SSMS (now with version 22!) and Github too of course. It would seem to make logical sense to be able to also use it inside Fabric and integrate all this together rather than requiring a separate copilot capacity in Fabric.   I know using the VS code extensions this is possible (well for some stuff), but ideally it would/should be the same in the Fabric web portal. ... View more

Recently, organizations can create organization-wide themes. For consultants working with Multiple organizations, will be nice to able to create theme from uploading logo and/or branding materials of organizations to create themes.   ... View more

Currently, when retrieving gateway data source connection details via the Power BI/Fabric REST API, the Azure Key Vault reference name configured for credentials is not included in the API response. This creates challenges for administrators who need to programmatically manage gateway connections that use Azure Key Vault for credentials. It is needed to move the connection to a new gateway cluster when the 1000 connection limit hits.   Current Behavior When calling the following API endpoints: - `GET https://api.powerbi.com/v1.0/myorg/gateways/{gatewayId}/datasources/{datasourceId}` - `GET https://api.fabric.microsoft.com/v1/admin/gateways/{gatewayId}/datasources/{datasourceId}`   The response includes: json {   "id": "datasource-id",   "gatewayId": "gateway-id",   "datasourceType": "Sql",   "connectionDetails": "{\"server\":\"localhost\\\\SQLEXPRESS\",\"database\":\"demodb\"}",   "credentialType": "Basic",   "credentialDetails": {     "privacyLevel": "Organizational",     "useEndUserOAuth2Credentials": false   },   "datasourceName": "gateway-demo-conn" }     Missing Information: When the data source credentials are configured to use an Azure Key Vault reference (e.g., "DemoKeyVaultReference"), this information is not exposed in the API response.   Requested Enhancement Include Azure Key Vault reference details in the API response when applicable, such as:   json {   "id": "datasource-id",   "gatewayId": "gateway-id",   "datasourceType": "Sql",   "connectionDetails": "{\"server\":\"localhost\\\\SQLEXPRESS\",\"database\":\"demodb\"}",   "credentialType": "Basic",   "credentialDetails": {     "privacyLevel": "Organizational",     "useEndUserOAuth2Credentials": false,     "keyVaultReference": {       "referenceName": "DemoKeyVaultReference",       "keyVaultUrl": "https://mykeyvault.vault.azure.net/secrets/sql-password",       "isKeyVaultReference": true     }   },   "datasourceName": "gateway-demo-conn" }   ... View more

Currently, when using Copy Job to transfer Snowflake data into MS Fabric Lakehouse, we can use the variable library to parameterize the Snowflake connection but cannot parameterize the target Snowflake database. This issue arises when switching the Snowflake source system between DEV and PROD environments using the variable library, as these environments may have different database names.   Suggestion: Add this as a parameter in the Copy Job using a variable library to swap the database based on environments OR add a parameter to the Snowflake connection for the database (currently only includes the "warehouse" parameter). ... View more

Measures are linked to specific tables and called as such. Why should a measure name be unique throughout the semantic model? With larger semantic models you inevitably run into naming conflicts. ... View more

Currently, only users with Pro or PPU licenses can create workspaces even if they already have access to a dedicated capacity. This can be challenging for organizations that invest in capacity to unlock advanced features and better performance.   What we’re suggesting:   Let users who have capacity access also create workspaces. This change would make capacity ownership truly meaningful by allowing full workspace management. It’s a more logical, seamless experience for enterprise customers. ... View more

Until yesterday, the Data Agent Test pane had an inline “Details” section that exposed the generated SQL for Warehouse/Lakehouse steps. Now the only path is “Download diagnostics,” which produces a JSON I have to open and parse to find the SQL it generated for my test promt. That adds multiple clicks and context-switches per prompt and has greatly slowed down development.    Impact: - Slows the tight dev loop (prompt → inspect SQL → adjust → re-test) because have to find SQL in diagnostic file instead of directly below my prompt/answer in the test pane - Makes authoring and curating example queries more cumbersome. - Discourages rapid experimentation when training the Data Agent on domain data. - Increases overhead during multi-step plans, where I need to see the SQL per step quickly.   Basically, when we're not getting the data we're expecting, I was previously able to easily identify the issue by quickly inpecting the SQL and then adding updated example queries to the data source examples section. This would fix the issue and was fast. Removing the generated SQL in the test pane has now slowed down development significantly.   Request: 1) Restore the inline Details / “Show SQL” panel in the Test pane for Warehouse/Lakehouse SQL endpoint calls. 2) Alternatively, add a “Developer mode” toggle that shows tool calls (with generated SQL) inline—no download required.   ... View more

The introduction of the .pbip file format for Power BI reports has been a really useful for CI/CD practices in my organization. As our analytics capabilities and catalog grows, we want to make use of Fabric Deployment Pipelines but have run into a roadblock. I was a bit dumbfounded when I discovered that deploying reports from one workspace to another converts them back to .pbix format. I'm forced now instead to set up separate Dev + QA branches in one repository when I would have preferred the deployment pipeline UX with separate repositories for each workspace. I've seen mentioned in other forum posts that .pbip support is coming, but I don't know whether or not that is officially the case. It would be really useful in my current situation as a chemical engineer working to build out data literacy and analytics capabilities for a global R&D team. Thank you! ... View more

There should be the possibility to use Swiss number formatting in Fabric with Semantic Models in Direct Lake ... View more

Hello, On the NPM package powerbi-client@2.23.9 I see some Architecture Quality Policy warnings on the following.  Age older than 1825 days because: Found component older than 5 years, see bold arced dependencies:   powerbi-client@2.23.9      http-post-message@0.2.3 powerbi-client@2.23.9      powerbi-router@0.1.5               route-recognizer@0.1.11 powerbi-client@2.23.9       http-post-message@0.2.3            es6-promise@3.3.1       powerbi-router@0.1.5            es6-promise@3.3.1 deduped       window-post-message-proxy@0.2.9            es6-promise@3.3.1 deduped powerbi-client@2.23.9       powerbi-router@0.1.5   ... View more

We have issues where Power Quary requires realoding the dataset every time we need to work on it. Ideally, once the data is loaded, we should be abel to work on it without having to reaload it repeatedly. Please investigate this behaviour, as it impact workflow efficiency and incraeses processing time. ... View more

The Lineage View is currently not very useful (apart from a large number of items that are created by connections, etc.), because I call up or reference tables from other lakehouses/warehouses in views/stored procedures, but these are not then displayed in the Lineage View. The warehousen still stands alone. Access to other artifacts should also be displayed via SPs. ... View more

For the Azure Maps Visual in PowerBI - can we have it default to the Satellite overlay rather than Grayscale. Every time I switch to Satellite view and publish - it reverts back to Grayscale. Grayscale is nice but prefer Satellite.    Here's what other forusm have told me:  Short answer: No — not currently. Power BI’s Azure Maps visual does not allow you to set “Satellite” (or any basemap) as the permanent default. It always reloads using the default Road/Grayscale basemap when the report renders. However… there are a few workarounds depending on how you’re publishing the report. Current State (Limitations) Microsoft's Azure Maps visual has: No property in Visual Settings No Format → Map settings option No JSON theme capability No report-level or visual-level configuration that locks the basemap to Satellite This is why your report keeps snapping back to Grayscale even though you pick Satellite manually. This is expected behavior (unfortunately) and affects: Power BI Desktop Power BI Service Power BI embedded ... View more

Is there a way to generate an email send in a pipeline to a corporate account and attach a CSV file? What alternatives do I have to send a CSV that is in a lakehouse by email? Thank you very much! ... View more

Now onedrive/sharepoint refresh, identify the pbix file by File ID instead of File Name. It really causes a lot of issues. When people incorrectly update the file, the file ID lost quietly and intentionally!!! Then all the connection of the reports have to redo...that's really rediculous! This solution is more of a non-technical or user-friendly way, but using a invisible identifier - file ID to identify the file. In the Onedrive/sharepoint, of course file names are not able to duplicate, so naturally it should and it's also available to identify by file name.   Besides, the break of the connection can't be found until developer realise the new function doesn't work, because the model is still able to update data.     ... View more

Hello,   Currently, Microsoft Fabric does not provide a way to temporarily pause data syncing for Mirrored Databases while keeping the mirror relationship intact. The only available option is to delete the mirror, which removes all metadata and requires a full re-ingestion if the mirror needs to be re-established later.   A Pause / Resume capability would provide significant benefits:   Key Benefits   Cost Control: Allows organizations to temporarily halt ingestion during periods of low usage or while performing maintenance. Operational Flexibility: Pausing sync prevents unnecessary data transfers when source systems are under heavy load. Data Quality & Governance: Enables teams to stop ingestion while upstream data issues are being corrected without losing the mirror configuration. No Loss of Configuration: Keeps the mirror relationship, schema mapping, and settings intact, avoiding the need to recreate the mirror.   Requested Features:   A Pause button that stops all incremental sync operations without deleting the mirror. A Resume option that continues syncing from the last successful checkpoint. Optional schedule-based pausing (e.g., pause nightly or weekends). Clear UI indicators of paused status and last sync time. This enhancement would bring Mirroring more in line with other Fabric ingestion patterns that already support manual or scheduled refresh control. Thank you for considering this feature. ... View more

Hi there.   I love the new cards. It takes a bit to figure them out, but when you do, they are incredibly powerful.  Recently, I discovered that changing the color of Divider and the Reference Label Background has no affect. I originally had conditional formatting but removed it, and the color stayed the same. Changing them to any color has no affect. Divider     Reference Label BG   With Conditional Formatting   Conditional Formatting Remvoed   New Color Applied   ... View more

It would be helpful to be able to chose which side the column subtotals (or totals) show on the matrix table so that you can always see them as you scroll have to scroll horizontally through the column fields. Or have them be similar to when you have row totals and have to scroll virtically, the row totals are always visible. I have tables where the grand total per row (column totals) is the primary data point they want to see but they still want to be able to scroll the the fiscal years (column variables).  ... View more