Forum Discussion
Syncing a Azure DevOps git repo into another empty workspace fails
Sorry for the misunderstanding. The user mentioned does have the right to create artifacts within the workspace. The inability of choosing the data destination indeed is a behaviour which differs between "Guest user" and native user within our customers Microsoft environment.
I have contacted Microsoft Support and had a meeting, where they confirmed this is a bug and needs to be addressed internally.
As a workaround the suggest to use Dataflow (Gen 1) and I am currently figuring out how to get the data from a Dataflow into my Lakehouse (Hint: I use a Dataflow Gen2 to ingest the data from Dataflow Gen1, paradoxly this seems to work)
Sorry for the misunderstanding. The user mentioned does have the right to create artifacts within the workspace. The inability of choosing the data destination indeed is a behaviour which differs between "Guest user" and native user within our customers Microsoft environment.
I have contacted Microsoft Support and had a meeting, where they confirmed this is a bug and needs to be addressed internally.
As a workaround the suggest to use Dataflow (Gen 1) and I am currently figuring out how to get the data from a Dataflow into my Lakehouse (Hint: I use a Dataflow Gen2 to ingest the data from Dataflow Gen1, paradoxly this seems to work)
Hi Anonymous
Thanks for providing the workaround here. Please continue using Fabric Community for any help regarding your queries.