Semantic Model data source type not appearing in Lakehouse shortcut

[lava_]

We would like to create a shortcut in a Lakehouse that points to a semantic model in a workspace. We have enabled all of the settings necessary to get this going and have the correct Fabric license for the workspace (see below). After configuring all of that, the semantic model does not appear in the data source option under OneLake.

It seems as though we have not successfully integrated the semantic model with OneLake, but I'm not sure what we're missing or have done wrong. Has anyone ran into this issue and could provide guidance? Thank you!

Steps completed so far:

- The workspace where the lakehouse and semantic model live is on a Power BI Premium capacity

- I have admin permissions to this workspace

- The semantic model is an import semantic model - (it uses a dataflow, so not sure if that's impacting anything?)

- In our admin portal, we have enabled "Semantic models can export data to OneLake"

- On the semantic model, we have enabled "Large semantic model storage format" as well as "OneLake Integration"

- We then refreshed the semantic model

- In the Lakehouse and within the Tables, I went to add a shortcut, selected Microsoft OneLake, and then only Lakehouse and Warehouse data source types were listed

- I also tried searching for the semantic model, and it didn't appear

[v-mdharahman]

Hi @lava_ ,

Thanks for reaching out to the Microsoft fabric community forum.

It looks like you are trying to create a shortcut in a Lakehouse that points to a Semantic Model in a Microsoft Fabric workspace. However, even after enabling all the necessary settings, the semantic model does not appear in the OneLake data source options. This indicates that OneLake integration with the semantic model may not be working as expected. As you already mentioned the steps you have done so far, you can still check if OneLake Integration is Fully Activated or check If the Dataflow Source is causing the issue as your semantic model is built on a Dataflow, this could potentially impact OneLake integration. Also check if the specific workspace has OneLake integration activated even though the tenant setting is enabled. If possible, try moving the semantic model to another workspace that supports OneLake integration and test again. Let us know if you try these steps and whether the issue still exists.

I would also take a moment to thank @Akash_Varuna, for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.

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.

[lava_]

Hi @v-mdharahman, thank you for your response. 

You mentioned checking if the specific workspace has OneLake integration activated. What's the specific setting that I should be checking? At the tenant level, are there any organization-wide policies or security settings that may be overriding the OneLake integration setting?

As for the dataflow, I thought initially that might be causing the issue (the semantic model uses a gen 1 dataflow), but I tested the Lakehouse shortcut using a semantic model that just uses an excel spreadsheet as its source, and it still didn't work. 

Thank you!

[v-mdharahman · Accepted solution]

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.

[lava_]

Thank you so much, @v-mdharahman. We'll take a look at your suggestions and let you know if we have any questions.

[v-mdharahman]

Hi @lava_,

As we haven’t heard back from you, so just following up to our previous message. I'd like to confirm if you've successfully resolved this issue or if you need further help.

If yes, you are welcome to share your workaround and mark it as a solution so that other users can benefit as well. If you find a reply particularly helpful to you, you can also mark it as a solution.

If you still have any questions or need more support, please feel free to let us know. We are more than happy to continue to help you.
Thank you for your patience and look forward to hearing from you.

[Akash_Varuna]

Hi @lava_ I suppose you have already enabled Fabric for that workspace right ? if not then the semantic model will not appear

[lava_]

Hi @Akash_Varuna , yes, we have Fabric enabled for that workspace. I saw in a different post for a similar-ish issue that there may be other organization-wide policies or security settings that may be overriding the OneLake integration setting. I'm going to look into that because I don't see why else this isn't working for us.