Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Don't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.

Reply
APG
Frequent Visitor

Fabric - Missing attached lakehouse when deploying with deployment pipelines

Hi everyone,

 

I am currently working in a BI project based on Fabric. We are using notebooks to import, transform and refine data that will be later modeled in semantic models.

 

Our scenario:

  • we set up three workspaces (dev, test and prod)
  • dev workspace is connected to a git repository
  • we built a deployment pipeline to deploy notebooks from dev environment to test environment (and later to prod)
  • In dev environment each notebook has one lakehouse connected

Our issue:

when we deploy the notebooks to test environment, only a few of them are deployed with the lakehouse attached. All the other ones are deployed without any lakehouse attached; as a consequence we are not able to create deployment rules to switch default lakehouses from dev lakehouses to test lakehouses.

 

Regards,

 

APG

1 ACCEPTED SOLUTION
APG
Frequent Visitor

Thank you for your reply; in my case none of the steps provided solved the issue.

 

After many checks on my notebooks I finally discovered that all the notebooks that "lost" the attached default lakehouse (during the deployment), had an empty cell at the end as a last cell.

Example:

APG_0-1722371126523.png

Removing these last empty cells solved the issue: now all my notebooks are deployed with the default lakehouse attached.

View solution in original post

2 REPLIES 2
Anonymous
Not applicable

Hi @APG ,

You can follow the steps below to troubleshoot and resolve the issue:

  1. Ensure that Lakehouse is properly bound in the development and test environments. Sometimes the deployment pipeline may not recognise the Lakehouse as the same object if the Lakehouse is added after the initial workspace allocation .
  2. Try unallocating and reassigning workspaces in the deployment pipeline. This will help ensure that the lake warehouse is correctly recognised as one object.

If the above steps do not help you resolve the issue, as a temporary solution you might need to manually attach the lakehouses in the test environment after deployment. It can help you move forward while the underlying issue is resolved.

 

Best Regards,

Ada Wang

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

 

APG
Frequent Visitor

Thank you for your reply; in my case none of the steps provided solved the issue.

 

After many checks on my notebooks I finally discovered that all the notebooks that "lost" the attached default lakehouse (during the deployment), had an empty cell at the end as a last cell.

Example:

APG_0-1722371126523.png

Removing these last empty cells solved the issue: now all my notebooks are deployed with the default lakehouse attached.

Helpful resources

Announcements
Las Vegas 2025

Join us at the Microsoft Fabric Community Conference

March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Prices go up Feb. 11th.

JanFabricDE_carousel

Fabric Monthly Update - January 2025

Explore the power of Python Notebooks in Fabric!

JanFabricDW_carousel

Fabric Monthly Update - January 2025

Unlock the latest Fabric Data Warehouse upgrades!

JanFabricDF_carousel

Fabric Monthly Update - January 2025

Take your data replication to the next level with Fabric's latest updates!