Sync Direction

[smpa01]

I can see the direction of sync (git integration) is from fabric to dev ops and this is fantastic.

I have cloned the dev ops repo to my local and I  want to know if I update a file locally 

@ Dataflow/PROD/CoA_bronze.Dataflow/mashup.pq and push to the dev ops repo, how does it sync back to the workspace?

I have not tried it and don't want to without understanding any downstream effecct it must have or is it only recommended to have the dev ops synced only from workspace and not from the local clone at all?

[andrewsommer · Accepted solution]

It won’t auto sync, you must manually pull it from devops.

Our engineering team messed with this for a bit and ended up deciding it wasn’t worth pursuing.  Seems like Microsoft wants us managing source-of-truth via the Fabric workspace and using the Git repo primarily for tracking and deployment, not as a full bidirectional sync platform.

Please mark this post as solution if it helps you. Appreciate Kudos.

[KevinChant · Accepted solution]

I can help with this.

You can change it locally and then sync it with your repository in Azure DevOps.

If it is the same branch go into your Fabric workspace, hit refresh and then go into source control to approve the updates.

If it is a different branch you will have to do a pull request beforehand.

I hope this helps?

[v-csrikanth]

Hi @smpa01 

Thank you for being part of the Microsoft Fabric Community.

As highlighted by @burakkaragoz @KevinChant @andrewsommer , the proposed approach appears to effectively addressed your requirements. Could you please confirm if your issue has been resolved?
If you are still facing any challenges, kindly provide further details, and we will be happy to assist you.

Best Regards,
Community Support Team _ C Srikanth.

[burakkaragoz · Accepted solution]

Hi @smpa01 ,

Currently, Fabric’s Git integration supports one-way sync only—from Fabric to Azure DevOps. This means:

• Changes made in Fabric (e.g., to a Dataflow) are pushed to the DevOps repo.
• Changes made locally and pushed to DevOps will not sync back into Fabric.

So if you update mashup.pq locally and push it to the DevOps repo, those changes will not reflect in the Fabric workspace unless you manually re-import or reapply them in Fabric.

For now, it’s recommended to treat the DevOps repo as a backup and version control mechanism, not a deployment source.

Let me know if you want to explore safe ways to test local edits or simulate a reverse sync.

[KevinChant · Accepted solution]

I can help with this.

You can change it locally and then sync it with your repository in Azure DevOps.

If it is the same branch go into your Fabric workspace, hit refresh and then go into source control to approve the updates.

If it is a different branch you will have to do a pull request beforehand.

I hope this helps?

[andrewsommer · Accepted solution]

It won’t auto sync, you must manually pull it from devops.

Our engineering team messed with this for a bit and ended up deciding it wasn’t worth pursuing.  Seems like Microsoft wants us managing source-of-truth via the Fabric workspace and using the Git repo primarily for tracking and deployment, not as a full bidirectional sync platform.

Please mark this post as solution if it helps you. Appreciate Kudos.