Notebook can't access lakehouse after deployment pipeline

[GammaRamma]

Hello, I've deployed a schema enabled lakehouse as well as several pipelines and notebooks which are linked to it from my dev workspace to my test workspace. When I open the new notebooks in my test workspace, they are successfully linked to the new lakehouse in my test workspace. So far everything seems good. 

However, when I try to access the lakehouse via the notebook, i get this error: 

Artifact not found: `CIUSSSMCQ-ET-DRI - DATALAKE - TEST`.`lkh_bronze_octopusDri_intDiff`. 

You can clearly see in the capture that the lakehouse is set as default but the notebook cannot find it.

I've tried with a new notebook. Same problem. I've tried the same thing with other lakehouses that I deployed and get the same problem. I've tried redeploying the lakehouses and notebooks again. Nothings works. 

Any help would be appreciated! Thanks

[v-saisrao-msft]

Hi @GammaRamma,

We haven’t heard back from you in a while. If your issue has been resolved, Mark the relevant response as the solution to help fellow community members.
If you still need support, let us know if you still need assistance.

Thank you.

[v-saisrao-msft]

Hi @GammaRamma,

checking in to see if your issue has been resolved. If the response provided was helpful, kindly mark the helpful reply as solution so that others with the same issue can benefit.
let us know if you still need assistance.

Thank You.

[v-saisrao-msft]

Hi @GammaRamma,

I hope you had a chance to review the solution shared earlier. If it addressed your question, Consider accepting the helpful reply as solution it helps others find answers more quickly.
If you're still facing the issue, feel free to reply, and we’ll be happy to assist further.

Thank You.

[burakkaragoz]

Hi @GammaRamma ,

This issue usually happens when the notebook appears to be linked to the lakehouse, but the internal reference to the artifact doesn't update properly during deployment.

Here are a few things you can try:

1. Manually reselect the lakehouse in the notebook from the dropdown at the top. Even if it looks correct, reselecting it can refresh the binding.

2. Check the lakehouse name carefully — even a small mismatch (like an extra space or different casing) can cause the "Artifact not found" error.

3. Make sure the lakehouse schema and tables were actually deployed to the test workspace. Sometimes the lakehouse gets created but the schema objects don’t come through.

4. Try running %sql SHOW TABLES in the notebook to confirm if the lakehouse is accessible at all.

5. If nothing works, try removing and re-adding the lakehouse to the notebook manually. That usually clears any stale references.

Let me know if you want help testing it step by step.

If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.

This response was assisted by AI for translation and formatting purposes.

[GammaRamma]

Thank you for your answer @burakkaragoz.

1. Reselecting doesn't work

2. I'm not naming the lakehouse, it's the default, so it can't be the name

3. Everything was deployed, the test workspace was empty before

4. SHOW TABLES gives me the same artifact not found error

5. Removing and readding the lakehouse does not fix the error

I've tried with a new notebook. Same problem. I've tried the same thing with other lakehouses that I deployed and get the same problem. I've tried redeploying the lakehouses and notebooks again. Nothings works. 

[v-saisrao-msft]

Hi @GammaRamma,

Use fabric deployment pipeline while deploying and use deployment rules as shown in the below screenshots.

Change the destination lakehouse using from and to options.

Then click on save and deploy

Thank you.

[GammaRamma]

Hi @v-saisrao-msft thank you for your reply. I have tried to map the notebook to the test lakehouse directly and redeploying but I still get the same error. 

The error seems to be due to the way the lakehouses from the dev workspace are created in the test workspace by the deployment pipeline. These lakehouses are unusable by all notebooks in the test workspace. Something in them is broken when they are created by the deployment pipeline in the test workspace.

[v-saisrao-msft]

Hi @GammaRamma,

Could you please check if you enabled the lakehouse schema option while creating the notebook, since it's currently in preview?

Thank you.

[GammaRamma]

Hi @v-saisrao-msft,

All of our lakehouses are schema enabled, which is still in preview. I don't know of any options for schema enabling while creating the notebook.

[v-saisrao-msft]

Hi @GammaRamma,

Since your issue is still not resolved, I recommend raising a support ticket with Microsoft, as this requires deeper investigation. You can submit a ticket using the link below:

How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

Thank you.

[v-saisrao-msft]

Hi @GammaRamma,

Thank you for reaching out to the Microsoft Fabric Forum Community.

Remove the notebook, then re-add the lakehouse to it and run your query again. Also, check for any unsupported special characters which are not supported.

Below is the link for your reference:

Lakehouse schemas (Preview) - Microsoft Fabric | Microsoft Learn

Thank you.