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)
Hi Anonymous
When we sync from a Git repo to a new workspace, we create all the artifacts that were present in the original workspace. So, if the you dont have permission to do this, it will fail. Please try from an account which has permissions to create artifacts and connections.
So in this screenshot, I cannot even choose a Lakehouse / Warehouse within the workspace as origin for the Dataflow Gen 2.
For the above sentence:
I believe this is again due to permission issue as the you have logged in as “guest user” and dont have the required permissions to access the lakehouse/warehouse.
So try with a different account which has permissions and let me know if the issue still persists.
Hope this helps.
Hi @sebastianriemer
We haven’t heard from you on the last response and was just checking back to see if your query got resolved. Otherwise, will respond back with the more details and we will try to help.
Thanks