Semantic Model data source type not appearing in Lakehouse shortcut

Hi lava_,

Thanks for your follow-up.

Here are the steps to check if OneLake integration is enabled at both the workspace level and tenant level and whether any security settings might be affecting it.

On Workspace Level : 

While there’s no direct toggle in workspace settings for OneLake integration, please ensure: The workspace is in Power BI Premium capacity which you’ve confirmed earlier. Also the semantic model has OneLake Integration enabled which you’ve already set. Check if no custom security policies are restricting OneLake access.

To check workspace details in Power BI Service, go to Admin Portal then Workspaces. Find your workspace and verify that it’s assigned to a Premium capacity. Also ensure there are no custom restrictions on OneLake integration for this workspace.

On Tenant Level : 

There could be organization-wide settings or security policies affecting OneLake access. So to verify tenant settings in Power BI Admin Portal, go to Tenant Settings. Then look for OneLake Integration and confirm if the "Semantic models can export data to OneLake" is enabled or not. Also make sure there are no restrictive security policies blocking OneLake (such as Information Protection rules).

If your organization uses Microsoft Purview or Fabric Security Policies, check with your admin to see if any data security restrictions are applied.

Since you’ve already tested a semantic model without a Dataflow and still don’t see the shortcut option, try testing in a different workspace to see if it’s a workspace-specific issue. Also check if another user in your organization can see the semantic model in OneLake so that we can understand there is no permission-related issues.

If I misunderstand your needs or you still have problems on it, please feel free to let us know.  

Best Regards,
Hammad.
Community Support Team

If this post helps then please mark it as a solution, so that other members find it more quickly.

Thank you.