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

Enhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.

Reply
jsatow
Frequent Visitor

Metadata showing as changed on notebook between stages

jsatow_0-1733497855837.pngjsatow_1-1733497862521.png

 

Hi, some backstory first.  We were getting our workspaces set up and did things a little out of order.  Long story short, I had to copy things from Prod back to dev.  Then ran a deployment pipeline from dev to test.  Then test to prod again.   Of course i had to create data pipelines to copy data between lakehouses since deployment pipelines copy over empty lakehouses.  I am not sure if this is relevant to my question or not but wanted to provide some background. 

 

Anyways, each workspace (dev, test, and prod) only has a lakehouse and a notebook.   As you can see from the pictures, it shows differences between the notebooks in dev and prod. Upon opening the differences you can see its just metadata.  If you click deploy, it will say its all synced up and show the green checkmark. However, after running the notebook once, it will go back to saying the metadata is changed.  I can see the affected metadata has to do with default notebooks but I can't discern the problem. From what i can tell, both notebooks have the properly set default lakehouses in their respective workspaces.

 

If anyone has any ideas how to fix this, that would be appreciated. Thank you 🙂

1 ACCEPTED SOLUTION
Anonymous
Not applicable

Hi @jsatow 

 

The behavior seems related to the following note in Notebook in deployment pipelines.

vjingzhanmsft_0-1733725138839.png

 

I remeber before this change, the default lakehouse of the notebook after deployment is still bound to the lakehouse in the source stage unless modified by a deployment rule.

 

Best Regards,
Jing
If this post helps, please Accept it as Solution to help other members find it. Appreciate your Kudos!

View solution in original post

1 REPLY 1
Anonymous
Not applicable

Hi @jsatow 

 

The behavior seems related to the following note in Notebook in deployment pipelines.

vjingzhanmsft_0-1733725138839.png

 

I remeber before this change, the default lakehouse of the notebook after deployment is still bound to the lakehouse in the source stage unless modified by a deployment rule.

 

Best Regards,
Jing
If this post helps, please Accept it as Solution to help other members find it. Appreciate your Kudos!

Helpful resources

Announcements
Fabric July 2025 Monthly Update Carousel

Fabric Monthly Update - July 2025

Check out the July 2025 Fabric update to learn about new features.

August 2025 community update carousel

Fabric Community Update - August 2025

Find out what's new and trending in the Fabric community.