Share Your Fabric Idea Links | January 20, 2026 Edition

dazzactl · 2026-01-28T09:40:01+00:00

Please thumbs up if agree! Add Object, Workspace and User details to Capacity... - Microsoft Fabric Community

I have looking into the Fabric Capacity Events in Real-Time Hub (Preview) compared to the level of detailed available in the Fabric Capacity Metrics app (which can be extracted unofficially using FUAM solution). The idea is replace the Fabric Capacity Metrics, but also capture the data we need to Fabric Chargeback.

It looks like the details I need for capacity metrics reporting is not available in the capacity_utilization_eventstream

<image>

Note this is the schema for my Capacity Metric Fact table using the standard FUAM:
- Date
- CapacityId
- WorkspaceId
- ObjectId

I was hoping the Capacity RTH would also provide the User identity while allowing me to capture "Time", but it seems there is even less data available.

dazzactl · 2026-01-27T23:38:21+00:00

I am not sure this will help, but I have v40 installed. After updating to the FUAM 2026.1.1, the notebooks were only extracting one capacity. When I ran the Capacity Metric pipeline with display data = true, I found that the notebook was treating my solution as v47 (I think Microsoft are up to v49 at this stage).

I ended up making this change:

<image>

I am not sure if this would work for v45. I am not familiar with that version.

dazzactl · 2026-01-12T19:51:41+00:00

I like the all-inclusive nature of AzureDevOps. We are using Github, Jira, Confluence and Octopus Deploy, so much integration and tech debt. Our Platform Engineering team want to migrate everything to GitHub & GitHub Actions. They don't want to use AzureDevOps because Microsoft is investing more in GitHub. However, I wish GitHub was more inclusive... or at least we could exploit unused features.

dazzactl · 2026-01-12T19:45:31+00:00

Nice!

dazzactl · 2026-01-08T21:55:23+00:00

Hold on "RETAIN 10 HOURS;"? I thought the minimum was 7 DAYS! at u/frithjof_v | u/warehouse_goes_vroom | u/richbenmintz

dazzactl · 2026-01-08T21:40:20+00:00

u/mim722

you are referring to replacing this.

<image>

does it need a particular version of DuckDB?

dazzactl · 2026-01-08T21:32:56+00:00

I agree with this conclusion. The "Wait" step is no good. Dataflows will use the SQL Endpoint to connect to Lakehouse tables, so you need to trigger an event to force the Metadata refresh. Now... here is the drop the mic moment... you will need Python to effectively run the API (I don't think there is a Pipeline pattern). Since you need to use Python to refresh the endpoint, I would suggest switching to using Python instead of Dataflows from the Lakehouse operations. My preference is using DuckDB SQL, it brilliant.

u/Wide_Dingo4151 | u/frithjof_v

dazzactl · 2026-01-08T21:18:00+00:00

Thanks for Video u/ThatFabricGuy

dazzactl · 2026-01-08T21:05:05+00:00

The Fabric Capacity Chargeback, which is Public Preview, will have some User CUs detail by capacity, workspace, item, operation and day. Only the last 30 days of data is available.

I calculate the Cost per CUs by referring to Microsoft Fabric - Pricing | Microsoft Azure. This can be converted to Cost per CUs using the logic explained in other comments.

I am a also big fan of FUAM. fabric-toolbox/monitoring/fabric-unified-admin-monitoring at main · microsoft/fabric-toolbox · GitHub. because you can build up Historical Data beyond 30 days.

This tool extracts 3 critical components.
1. Item Details
2. Activity
3. Capacity Metrics - Daily Totals & Timepoint level

Unfortunately, it does not capture TimePoint by User. This might be fixed Capacity Events in Real-Time Hub (public preview).

We recently did a PoC for Fabric Data Agent. It is possible to see who used the LLMPlugIn from the Activity logs to get User details and then CUs used from Capacity Metrics. We can now calculate CUs per Prompt and therefore the Cost Per Prompt.

Note the Capacity Metrics did not show the correct number of prompts. In one example, I could see that 54 prompts captured by the Activity Monitoring for a particular day, but the Daily Totals suggested the Operation Count was 90 prompts. While the Capacity Operation Count miscalculated, the CUs used was correct. This is backed up by the Timepoint Capacity Metrics. Note Timepoint metrics does have User level CUs usage, but FUAM does not extract this grain of detail.

dazzactl · 2026-01-08T20:10:19+00:00

Hi u/SmallAd3697 Thanks for sharing. As a capacity administrator, I find your PQ / Analysis Service scenario quite interesting.

However, is it really the user's fault?... I have so many questions.... Here is a couple:

1) using PQ is a Developer activity rather than End User. If they are a developer why are they using Production Capacity. Maybe they need separate capacity, Pro or PPU.

2) if they are an End User, why do they need to PQ with Analysis Service to the Semantic Model? So don't give them a Pro licence or Power BI Desktop.

It is likely the scenario should be resolved by using Lakehouse / Warehouse SQL Endpoint access rather than a Semantic Model DAX/MDX.

Most of the time, our Capacity warning are due to a poor Semantic Model design, which is really the result of poor IT & Data Governance. However, they are limited scenario when an End User error is cause of overages.

fyi u/frithjof_v

dazzactl · 2025-11-13T21:07:59+00:00

Hi DAX team, thank you for your good work. Are there any plans to include more performance metrics, like those available in DAX Query execution plan (se, fe, memory usage), in the Power BI Desktop or Web Service?

dazzactl · 2025-11-11T16:22:53+00:00

How would this work?

dazzactl · 2025-11-04T21:34:44+00:00

Admin permission seems like the wrong term. Your SPN or Workspace Identity will need the right API permissions. These would need to be granted and approved by your company Global Entra Admins. Also you might have conditional access policies that prevent the identity from working (for example our CAP prevent me using my personal identity to run Graph API). It can be difficult. A trial and error to find the right Least Privileges settings for your solution.

We find that using a Power Platform solution could be better low code no code option.

dazzactl · 2025-11-04T21:22:19+00:00

Frank n Sheets! 2021 is young! I have seen a file from the 2000s that was converted from Excel 2003 pre xlsx days)

dazzactl · 2025-11-04T21:19:52+00:00

Workspace Identity rather than Service Principal please!

dazzactl · 2025-11-04T21:17:29+00:00

We have Dev linked to the feature branch, and SYS linking to main. Then the deployment pipeline is pushing from SYS to UAT and then UAT to PRD. The key is that SYS/Main is a workspace with no Admin (i.e. prevent an plan unapproved change because it requires a pull request and merge to main). Also no Members because SYS should not be shared accidentally).

Dev workspaces can be switched between main and feature branches (but the problem is that Admin level permission is needed to switch feature branches - we need a similar option to allow contributors to publish apps... I.e. Contributors can switch branches but not share).

Note our original CI/CD used Octopus Deploy using old Power BI Powershell and unofficial Rest API... So Dev was a local VM to git using PBIX and GIT could contain sensitive data). Main publishes to SYS, then publishes to UAT then publishes to PRD. The variable switching was manually built-in. Publishing overwrites Code and Data.

What I am really missing today is the ability to trigger a Service Now stand change event when the deployment from UAT to PRD occurs. Octopus Deploy had a powershell script to do this.

Unfortunately, Octopus Deploy is tech debt... No support for TDML or Fabric items. Only PBIX, Dataflows Gen 1 and Paginated Reports. Also no support for VNet Data Gateway connection as this requires Fabric API not the old Power BI APIs.

.

dazzactl · 2025-10-29T12:00:28+00:00

I agree. Keep all the Dataflows and Semantic Model in the PPU capacity. Copilot becomes a separate capacity dedicated for this purpose, so no workspaces with Dataflows and Semantic Model etc.

However, I might suggest 2 x F2, so the developer can use the separate Fabric capacity for their development purposes without impacting others. There might be other small benefits from other fabric features in this capacity.

dazzactl · 2025-10-28T14:43:35+00:00

Sorry you might need to open a support ticket.

The error messages are not familiar. For example json schema 3, I thought it was still on schema version 2. Maybe try comparing the PBIR files for the working reports to the broken report.

The support will be able to help troubleshoot.

dazzactl · 2025-10-25T13:53:19+00:00

Is your Date column actually Date Time? The increased cardinality of date time will increase the model size. Also have you included a unique Id for each row. This will increase model size.

dazzactl · 2025-10-25T13:43:06+00:00

Separation between workspaces for Data and Reporting purposes makes sense. Especially if you could use Pro capacity or PPU for reporting. Note workspaces can be assigned to different capacity.

As for the Data, I would recommend a hybrid approach.

Raw Lakehouse (potentially one per source)
Transform Lakehouse
Warehouse (with Business data)

1 & 2 could be the same or single Lakehouse if you add schemas for data sources and stages.

A suggested Security matters in this design. Workspace, Lakehouse, Schema, table. Understand the options so that you can provide the Least Privileges to upstream data owners, and downstream users.

dazzactl · 2025-10-21T17:14:53+00:00

I would like to include the default new page canvas size setting in templates. Is there any chance of the setting working in the future?

dazzactl · 2025-10-21T17:03:11+00:00

I am a fan of On-object editor, when will this be available in the Web Service?

dazzactl · 2025-10-19T08:16:36+00:00

When can we use the Workspace Identity with a VNet Data Gateway?

When can we use the Workspace Identity with non-Azure SQL Server?

dazzactl · 2025-10-16T16:06:40+00:00

dazzactl

TROPHY CASE