Forum Discussion
Microsoft Fabric Capacity Metrics Semantic Model Error
Hi gallen , Thank you for reaching out to the Microsoft Community Forum.
GilbertQ is correct about the capacity ID, because an incorrect or incomplete one can block the connection. But even with the right ID, the main issue is usually that the FabricMetrics connection in Power BI Service isn’t authenticated properly. The app must connect using an account that has access to the Fabric capacity; otherwise, the model can’t process.
To fix this, go to the workspace where the app is installed, open Datasets + Dataflows -> Capacity Metrics Semantic Model -> Settings and under Data source credentials, re enter your credentials using OAuth2 with a Fabric admin or capacity admin account. Then save and refresh the dataset. Service principals aren’t supported for this semantic model yet, so it must use a user account with Fabric access.
Thanks for the feedback.
We copied and pasted our capacity ID. So, I think we are good there.
Found the Settings and reentered my credentials. This time we got a different error:
Error fetching data for this visual
Expression.Error: The column 'Column1' of the table wasn't found.. Column1. Microsoft.Data.Mashup.ErrorCode = 10224. Detail = Column1. . The exception was raised by the IDbCommand interface.
Underlying Error: QueryUserError
Activity ID: 7a0a593e-8cdd-4760-8cb4-488027e579ca
Correlation ID: 743c35fb-be2d-3be6-9a6c-c53867322df6
Request ID: 7bafa754-33f2-45c3-948e-9809f228042a
Time: Wed Nov 12 2025 14:51:10 GMT-0500 (Eastern Standard Time)
Service version: 13.0.27090.32
Client version: 2511.2.26716-train
Cluster URI: https://wabi-us-north-central-j-primary-redirect.analysis.windows.net/
Hi gallen , Thank you for reaching out to the Microsoft Community Forum.
The new error means the query is running, but the service isn’t returning the table the semantic model expects. When Power Query says Column1 is missing, it’s usually because the monitoring API responded with an unexpected shape, often an empty result or an HTML/error payload. That typically happens when the credentials used don’t actually have permission to read the capacity metrics or when the Capacity ID parameter has hidden characters or formatting that makes the API call return something different.
Try re-authenticating the dataset with a confirmed Fabric or capacity admin account, then look at the Power Query preview for the step right before the one that references Column1. If you see HTML or an error message instead of real data, that confirms it’s an authentication/permission issue. Also, double check the Capacity ID in a plain text editor to ensure it’s only the GUID with no braces or extra spaces.
If the query still returns an unexpected shape, Create a Microsoft Support ticket share the Activity ID and Correlation ID with Microsoft support so they can trace the backend response.
Below is the link to help create Microsoft Support ticket:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn