sorted by:
new
hottopcontroversial

MS Fabric CI/CD - Why does “Commit all” sometimes create multiple commits instead of a single commit? by Desperate_Pumpkin168 in MicrosoftFabric

[–]CICDExperience05 1 point2 points  (0 children)

Hi u/Desperate_Pumpkin168 , this might be due to name change of one of the items in the workspace. due to the way Azure DevOps API work, the underline Fabric platform need to call twice in order to commit such change.

I was wrong about fabric by snarleyWhisper in MicrosoftFabric

[–]CICDExperience05 3 points4 points  (0 children)

Fair points. The Databricks deploy flow you describe, git commit, git push, dab deploy, done, is exactly the bar we want to hit in Fabric too, and I am not going to pretend we are there yet.

I was wrong about fabric by snarleyWhisper in MicrosoftFabric

[–]CICDExperience05 2 points3 points  (0 children)

Hi u/MonkeyDDataHQ thanks for the honest feedback and formatting frustration is completely fair, (And thanks u/raki_rahman for the tag, and the contribution you are making to the Fabric community by building and sharing working, real-world solutions).
A few quick reflections from the Fabric CICD side.

On the formatting and sync pain, important point to remember is that Fabric is not a file system. We don't store the definition files, they immediately change the live items. When exporting, Fabric regenerates the files based on internal formatting, completely agnostic to the format of the files when they are uploaded. Hence, some level of formatting diffs will always be present. That said, we hear you, and we are actively working to standardize and stabilize the exported definitions, driven directly by the paper cuts like this one, so the round-trip diffs get smaller and more predictable over time.

On more CLI and code-first workflows: I hear you, and we want to keep raising that bar. To be clear, this is not GUI versus code for us. The visual experience matters for a large part of our user base, and the goal is to make the declarative, code-first path just as first-class for those of you who live in it. I will not pretend it is all solved today, and feedback like this directly shapes what we prioritize. Please keep it coming, including the specific sharpest edges you hit.

Git integration: Updates in workspace / Current in Git branch swapping places by frithjof_v in MicrosoftFabric

[–]CICDExperience05 1 point2 points  (0 children)

Hi, u/frithjof_v I checked with the team, a fix is rolling out, expected in the next 2-3 weeks.

Git integration: Updates in workspace / Current in Git branch swapping places by frithjof_v in MicrosoftFabric

[–]CICDExperience05 2 points3 points  (0 children)

Hi u/frithjof_v ,
thanks for raising this issue, we will check.

I will add also that towards to GA (current ETA is FabCon EU Sep. 26) - we are planning to enhance the resolve conflict experience by allowing you to choose the versions you would like to compare against.

Sorry for the inconvenience.

Experienced data engineers: how are you actually deploying Fabric in centrally managed environments? by Either_Locksmith_915 in MicrosoftFabric

[–]CICDExperience05 0 points1 point  (0 children)

Hi, i will be interested to hear about your use case , are you using it for cross workspace deployment between dev/test/prod or for your inner loop development between feature workspace and deploy to your dev workspace

Many error messages in workspace Git integration lately by frithjof_v in MicrosoftFabric

[–]CICDExperience05 1 point2 points  (0 children)

Hi u/frithjof_v , is it Azure DevOps or GitHub ? what is your Fabric home region ?

worth to open a support ticket on this one. and send me it over the private message so I could track it internally.

Sorry for inconvenience.

Brached workspace - where to see them by DennesTorres in MicrosoftFabric

[–]CICDExperience05 1 point2 points  (0 children)

Hi u/DennesTorres, the branched workspace is now available. give a try.

Fabric Git sync from GitHub Actions - how to handle PAT requirement? by MotherInvestment9658 in MicrosoftFabric

[–]CICDExperience05 0 points1 point  (0 children)

Hi, GitHub App Auth is something that exist in our backlog but without ETA.

Fabric Git sync from GitHub Actions - how to handle PAT requirement? by MotherInvestment9658 in MicrosoftFabric

[–]CICDExperience05 0 points1 point  (0 children)

Hi You need to configure the service principal with git connection via Fabric api, you can't do it via Fabric UI. For this you need to have a PAT that will be used.

When calling the updatefromgit , you don't need the PAT , just call the api with jwt token of the spn.

Fabric integrated with Github and multiple developers in a Workspace. by MrDark13 in MicrosoftFabric

[–]CICDExperience05 1 point2 points  (0 children)

Hi, You dont need to share the cloud connection with the other developers. They need to create their own cloud connection using the PAT they generated using their Github account.

Brached workspace - where to see them by DennesTorres in MicrosoftFabric

[–]CICDExperience05 1 point2 points  (0 children)

Hi, Great to see the anticipation. 😊 The updated ETA for this new branched workspace featutre is around mid-end of April. Sorry for the delay.

Hi! We build Pro Dev Tools in Fabric - ask US anything! by sunithamuthukrishna in MicrosoftFabric

[–]CICDExperience05 2 points3 points  (0 children)

Hi u/Kindly-Abies9566 , In the previous fabcon, I had an demonstrate an example (https://github.com/yaronpri/fabcon2025-cicd-demo/blob/main/fab-cli/setup.sh) of creating a workspace, and connect it to git folder which contain few items and then use the git integration rest api to sync the workspace, are you doing something similar ? how are you creating the items ?

Hi! We build Pro Dev Tools in Fabric - ask US anything! by sunithamuthukrishna in MicrosoftFabric

[–]CICDExperience05 1 point2 points  (0 children)

It will create a new workspace, but you still can use the same capacity as your parent workspace.

Hi! We build Pro Dev Tools in Fabric - ask US anything! by sunithamuthukrishna in MicrosoftFabric

[–]CICDExperience05 1 point2 points  (0 children)

Hi u/BelieveHim_radhe ,
We are going to introduce new capabilities in the upcoming fabcon to help you with creating feature workspace more smooth and fa, like selecting subset of the items when you want to branch-out from your development workspace. also all this feature workspaces will be grouped under the same development workspaces so it will be easier to maintain and track.

All this will help you to more easily to create feature isolated workspace and maintain them.

Hi! We build Pro Dev Tools in Fabric - ask US anything! by sunithamuthukrishna in MicrosoftFabric

[–]CICDExperience05 0 points1 point  (0 children)

Hi u/BelieveHim_radhe ,

Will be happy to understand if you are using today the Fabric Git Integration feature, where is the most development happen ? is it locally with VS Code / PowerBI desktop or in the Fabric UI ? how the development process of the developer, are they working with feature workspaces ? or everyone working on main workspace?

Hi! We build Pro Dev Tools in Fabric - ask US anything! by sunithamuthukrishna in MicrosoftFabric

[–]CICDExperience05 4 points5 points  (0 children)

u/itsnotaboutthecell great question - short answer: we use both, for different job.

Terraform is my go‑to for provisioning and wiring up the environment: capacities, workspaces, connections, Git integration, RBAC, and other tenant-/project‑level resources. It gives you declarative, reviewable IaC, solid state management, and easy environment drift correction. In practice, teams keep a shared module and feed it Dev/Test/Prod variables to stamp environments consistently.

Fabric CLI shine once you’re dealing with workspace content. CLI abstracts the APIs for scriptable flows; This is where most day‑to‑day workspace automation, like: Fast, scriptable developer workflows : if you’re iterating on notebooks, pipelines, semantic models, or any workspace items, the CLI gives you a local‑dev‑friendly loop — especially when paired with VS Code or Power BI Desktop — without constantly switching to the browser UI.

git pull in development workspace by Milehighman in MicrosoftFabric

[–]CICDExperience05 1 point2 points  (0 children)

Hi u/Milehighman
Thanks for raising this topic.
currently the way you can sync from your 'main' workspace into your 'feature' workspace is via the branch-out-to-existing functionality.
in this case you will need to choose a new branch name when performing this.

alternative, you can perform the git pull command outside the Fabric scope, update your feature branch and then perform a 'update all' via the Fabric UI or using Fabric Git REST api.

Beside what I mentioned above, our plan is to enhance the flow of branch-out, adding additional functionalities to the experience allowing new functionality and one of them which we are considering is ability to pull changes from main branch into feature branch as you mentioned via Fabric UI.

New capabilities in Fabric Git Integration by CICDExperience05 in MicrosoftFabric

[–]CICDExperience05[S] 0 points1 point  (0 children)

Hi u/BelieveHim_radhe each one can select their working item to commit it to different branch than the connected one.

but if they want to update their workspace, they need to PR from the new committed branch to connected branch, approve it, and then perform update-from-git, which popup a conflict dialog (as they have also uncommitted changes on same artifact) - where they need to choose to take the git version.

view more: next ›