Deployment pipeline Fabric: same workspace id and name in different workspaces

[Nikos83]

Hi, we use deployment pipelines in Microsoft Fabric.

We have separate workspaces for dev, tst, and production.

When we transfer a notebook from dev to tst using a deployment pipeline within Microsoft Fabric, we notice that the notebook has the same workspace ID and workspace name in both environments. I didn't expect this.

Code executed in our DEV workspace:

import sempy.fabric as fabric

fabric.resolve_workspace_name()

MDDP_dev

fabric.resolve_workspace_id()a'

7fe06c7a-3446-440f-b4b8-78089d937a4a

And same code executed in tst workspace:

MDDP_dev

7fe06c7a-3446-440f-b4b8-78089d937a4a

This seems like a bug to me. Presumably, the metadata of the corresponding notebook was copied along from the dev workspace to the tst workspace. Has anyone else seen this same issue?

[janlolling]

There is also an change of the workspace id if you connect your workbook with a lake house. In this case the id is also different

[Anonymous]

Hi @Nikos83 ,

Thanks for using Fabric Community and reporting this issue. This looks like a bug.
At this time, we are reaching out to the internal team to get some help on this .
We will update you once we hear back from them.

[Anonymous]

Hi @Nikos83 ,

Apologize for the issue you are facing. The best course of action is to open a support ticket and have our support team take a closer look at it.

Please reach out to our support team so they can do a more thorough investigation on why this it is happening: Link 

After creating a Support ticket please provide the ticket number as it would help us to track for more information.

Hope this helps. Please let us know if you have any other queries.

[Anonymous]

Hi @Nikos83 ,

We haven’t heard from you on the last response and was just checking back to see if you got a chance to open a support ticket.
After creating a Support ticket please provide the ticket number as it would help us to track for more information.

Thanks