Composite Model - personal vs. shared cloud connection

Hey collinq  , 

This issue happens in composite models in Microsoft Power BI when using DirectQuery to another semantic model (also called DirectQuery for Power BI datasets).

Why It Works with Personal Cloud Connection

When you use a Personal Cloud Connection, Power BI uses your own credentials and permissions to access the upstream semantic model. Since you likely have full access to that dataset, the visuals work correctly.

Why It Breaks with Shared Cloud Connection

With a Shared Cloud Connection, Power BI does not use your personal credentials. Instead, it relies on the connection identity configured in the workspace. If that shared connection does not have the required permissions to access the upstream semantic model, the DirectQuery visuals fail and appear broken.

Common reasons include:

1. Missing Build Permission - Users or the shared connection must have Build permission on the source semantic model.
2. Dataset Access Not Granted - The shared connection identity may not have access to the published semantic model used for DirectQuery.
3. Cross-Workspace Permissions - If the source semantic model is in another workspace, the shared connection must be allowed to access it.
4. Tenant / Admin Settings - Admin settings such as Allow live connections to Power BI datasets must be enabled.

Recommended Fix

Check the following steps:

1. Go to the source semantic model used in DirectQuery.
2. Open Manage Permissions.
3. Grant Build permission to the users or group that will use the shared cloud connection.
4. Ensure the semantic model is certified or promoted if used across workspaces.
5. Reconfigure the shared cloud connection and refresh the composite model.

If this explanation helped, please mark it as the solution so others can find it easily.

If it helped, a quick Kudos is always appreciated it highlights useful answers for the community.

Thanks for being part of the discussion!!!