Fabric Data Agent error user, help!

Daan_vanRiel​ 

Per Microsoft's docs, Read access on the underlying Power BI semantic model should be enough for a user to work with a Fabric Data Agent — workspace access isn't a stated requirement. Since this user can already open the semantic model and its reports, and RLS is behaving correctly for them, I don't think we're looking at a basic model-permission gap.

So before touching anything permanent, here's the plan:

1. Don't jump to granting Workspace Viewer. If we do add it and that resolves the issue, that's useful diagnostic signal — it'd point to an item-level access problem rather than a semantic-model one. But it should be a test, not a fix we leave in place.
2. Reproduce it in Fabric directly first. Have the user ask a simple question there, outside of Copilot. If it fails in Fabric too, we know this isn't a Microsoft 365 Copilot-specific problem.
3. Republish the Data Agent once we've confirmed the semantic model and agent config are up to date — just to rule out a stale publish.
4. Pull the Data Agent's diagnostics/run details to see exactly where it's failing: auth, semantic model access, query generation, DAX execution, or RLS.
5. Check Fabric capacity and service health around the exact time of failure, in case it's environmental rather than permissions-related.
6. Log the details so we have them ready for Microsoft Support if needed: timestamp, user UPN, Data Agent ID, semantic model ID, the exact question asked, and any Request/Activity/Correlation ID.

Bottom line: the user's setup looks correct per Microsoft's documented model. The right next step is controlled diagnostic testing — not assuming Workspace Viewer is a required fix.

If this helps, ✓ Mark as Kudos | Help Other