Forum Discussion
How to test fabric CI/CD Azure DEV ops ?
Hi kkoc3 ,
Thanks for reaching out to the Microsoft fabric community forum.For disaster recovery testing in Fabric with Azure DevOps, it’s best to avoid running tests in your Dev or Prod environments. Instead, create a dedicated sandbox workspace for example, DR-Validation-Workspace and target your pipeline deployments there. This isolated environment allows you to validate the full recovery process end-to-end without risking disruption to active workloads.
I hope this information helps. Please do let us know if you have any further queries.
Thank you
Super UserHi kkoc3,
So far we've given examples of CI/CD frameworks, and BC/DR frameworks that have been validated bu the Fabric CAT team.
What specific answers are you still looking for?
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.
Hi,
I'm exploring how to effectively test our CI/CD processes, especially in scenarios that go beyond standard BCDR tooling.
Our CI/CD setup is quite similar to what you've described in your organization. Now, consider a scenario where someone accidentally deletes key assets in your Fabric environment — such as pipelines, dataflows, notebooks, etc. You're tasked with restoring everything.
I'm interested in understanding how you would approach this recovery. What processes or strategies would you follow to bring everything back?
I'm not looking for tools or features like geo-replication or region failover this isn't about BCDR tooling.
Instead, I'm focused on processes and approaches that help validate the resilience and recoverability of your CI/CD setup.
This is just one scenario — I’m looking to explore a few others as well. The goal is to build a framework for testing and validating CI/CD robustness in real-world failure situations.
Does that make sense?
Hi kkoc3 ,
Thanks for reaching out to the Microsoft fabric community forum.For disaster recovery testing in Fabric with Azure DevOps, it’s best to avoid running tests in your Dev or Prod environments. Instead, create a dedicated sandbox workspace for example, DR-Validation-Workspace and target your pipeline deployments there. This isolated environment allows you to validate the full recovery process end-to-end without risking disruption to active workloads.
I hope this information helps. Please do let us know if you have any further queries.
Thank you