User Profile
IvyAraujo
Frequent Visitor
Joined 1 year ago
User Widgets
Contributions
Unable to Disable 'Manage OneLake Data Access' in Lakehouse – Impact on Direct Lake Semantic Models
We’re encountering a similar issue to this thread, where the "Manage OneLake data access" setting was enabled in a DEV Lakehouse. Currently, there appears to be no option to disable this setting once enabled, and this is impacting semantic models configured with Direct Lake storage mode. Options we've considered based on the thread recommendations: Rebuild the Lakehouse with the setting disabled. Switch the semantic model storage mode from Direct Lake to DirectQuery. Challenges: Option 1: Rebuilding the Lakehouse is a significant undertaking due to the numerous tables and views involved. According to Microsoft, for now, there is no UI or API to disable OneSecurity "Manage OneLake Data Access" feature once enabled in a lakehouse. Option 2: We attempted to change the semantic model storage mode via: Model > Semantic Model > Properties > Direct Lake Behavior from "Direct Lake Only" to "DirectQuery Only". However, the impacted tables still show an exclamation mark, and under Model > Table > Properties > Storage Mode, the tables remain set to Direct Lake, with the option to switch to DirectQuery greyed out. Is rebuilding the semantic model the most viable solution? Another potential option we considered was rolling back the Lakehouse to a previous version, before the "Manage OneLake Data Access" setting was enabled. However, Git does not appear to track changes related to the "Manage OneLake Data Access" configuration. Here's what we observed: Created the Lakehouse with OneLake Data Access disabled and committed it to DevOps. We then enabled OneLake Data Access in the Lakehouse. Upon attempting to commit again, the Lakehouse showed as "Synced", indicating no detectable change. This suggests that rolling back via version control might not a feasible solution, as the change is not captured in the Git history. Is there any plan from Microsoft to introduce functionality that allows disabling the "Manage OneLake Data Access" setting in Lakehouses? If so, could you please share whether there is a targeted release timeline or quarter for this feature? At present, the limited control over this preview feature can create challenges for data developers, particularly if changes to this setting are not captured by version control, making rollback scenarios unfeasible. Providing greater flexibility and management options around this setting would be highly beneficial to the data community. Many thanks!
