Use this thread to ask any questions you might have about this lesson: #1.3 RLS, OLS, CLS, File-level access control 👇

Current my notebook is connected with default lakehouse and I am able to do all operations. But I have a use case where I need my notebook to connect with any lakehouse dynamically using some configuration. Is this possible? How can I get it done?

Hey Microsoft Fabric folks, now you can 𝐝𝐲𝐧𝐚𝐦𝐢𝐜𝐚𝐥𝐥𝐲 𝐬𝐞𝐭 𝐲𝐨𝐮𝐫 𝐝𝐞𝐟𝐚𝐮𝐥𝐭 𝐥𝐚𝐤𝐞𝐡𝐨𝐮𝐬𝐞 in Microsoft Fabric notebooks—it's now generally available and makes managing environments easy! This can be done even across workspaces using variable library values, so no more manual UI Lakehouse attachment needed, when switching dev/test/prod. Here's how to set it up - super easy: • First, create a 𝐕𝐚𝐫𝐢𝐚𝐛𝐥𝐞 𝐋𝐢𝐛𝐫𝐚𝐫𝐲 in your workspace (e.g., name it "myVL"). • Add string variables like: - LHname → your lakehouse name - LHid → lakehouse ID (needed only for cross-workspace) - WorkspaceId → target workspace ID (needed only for cross-workspace) • In your notebook, make the 𝐯𝐞𝐫𝐲 𝐟𝐢𝐫𝐬𝐭 𝐜𝐞𝐥𝐥 a 𝐏𝐲𝐒𝐩𝐚𝐫𝐤 cell and add this code: %%configure { "defaultLakehouse": { "name": { "variableName": "$(/**/myVL/LHname)" }, "id": { "variableName": "$(/**/myVL/LHid)" }, "workspaceId": { "variableName": "$(/**/myVL/WorkspaceId)" } } } • Run the cell (it may ask to restart the session—just say yes). That's all! Your notebook now automatically uses the lakehouse from your variables. Drop the id/workspaceId parts if it's in the same workspace. Perfect for reusable notebooks and automated pipelines. Who's already using this? Drop your thoughts below! https://l1nk.dev/wHVON Full details: https://lnkd.in/gShwbfwH #MicrosoftFabric #DataEngineering #Lakehouse #Notebooks #VariableLibrary

Hi everyone, Excited to share that I have cleared DP 700 exam.Thanks @Will Needham