Power BI OneLake Integration

[wojciech]

Hi All,

I'm trying to us semantic model OneLake integration. I have enabled relevant tenant setting (see below):

Then I went to configure dataset iteself that is hosted in Premium (P1) workspace. I have enabled 'large semantic model storage format',  however OneLake integration is still grayed out with the following error:

That error doesn't make sense as OneLake integration is enabled at tenant level.

Has anyone come across a similar issue by any chance?

Thank you,

WJ

[nilendraFabric]

Hello @wojciech 

Ensure you have sufficient permissions for the semantic model, specifically "Model Contributor" permissions. This is required to access and modify settings related to OneLake integration

Check for any errors in calculated columns or tables within your semantic model.

After enabling OneLake integration and ensuring all prerequisites are met, trigger a manual refresh of the dataset. This step is necessary for changes to take effect and for data to appear in OneLake

https://databear.com/onelake-integration-power-bi/

https://learn.microsoft.com/en-us/power-bi/enterprise/onelake-integration-overview

Please see if this helps.

Accept the solution if this answers your query

[wojciech]

Thanks @nilendraFabric ,

I aprreciate your response. Yes, I have followed MS docs to set it up, I have all the permissions I need, but it doesn't wotk.
Intrestingly enough, I have followed the same steps in a diffrent tenant and it all works fine.

I will raise a support cal with Microsoft.

Thanks for you help.

WJ

[v-hashadapu · Accepted solution]

Hi @wojciech, thank you for reaching out to the Microsoft Fabric Community Forum.

If the setup works in a different tenant but not in the current one, then this might be a tenant-specific issue rather than a configuration mistake. Please check the following before raising a support ticket:

1. Some organization-wide policies or security settings may be overriding the OneLake integration setting, even if it appears enabled.
2. Ensure that the semantic model and OneLake storage are in the same region, as mismatched regions can sometimes cause unexpected behaviour.
3. Some features depend on specific Azure AD roles or licensing conditions that might differ between tenants.
4. If none of the above help, then yes raising a support ticket is the best course of action. You can provide them with all the troubleshooting steps you've already taken, which will help them understand the issue better and provide a resolution. They might be able to identify something specific about your tenant setup or provide a solution that isn't immediately obvious. 
   
   Below is the link to create Microsoft Support ticket:
   How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

Thank you @nilendraFabric  for your prompt and appropriate response.

If this helps, please consider marking it 'Accept as Solution' so others with similar queries may find it more easily. If not, please share the details.
Thank you.