Need recommendations for Fabric integration with Azure DevOps Repos

Hi DineshKalyankar ,

Having worked on several Fabric deployments with Azure DevOps, I can share some recommendations for your setup:

For version control of Fabric assets in Azure DevOps, here's what I'd suggest:

General best practices:

• Use a Git-based repo structure with separate folders for different component types (notebooks, pipelines, etc.)
• Implement branch policies requiring pull requests and code reviews before merging to main
• Consider organizing by workspaces and then by component type within each workspace

Component-specific recommendations:

• Notebooks: These work well with git. Store as .ipynb files
• Semantic Models: Export as .bim files for versioning
• Pipelines/Dataflows: These can be exported to JSON/YAML format
• Power BI Reports/Dashboards: Use PBIX files (though you'll need to manually download/upload)
• Lakehouse/Warehouse: This is where you'll face the biggest challenges

For Lakehouse and Warehouse: You're right that these are problematic. The schema/definition can be version-controlled, but the actual data cannot be effectively managed through DevOps. This is a known limitation.

Workable approaches for Lakehouse/Warehouse:

1. Version control the DDL scripts that create tables/views
2. For Lakehouse, consider using Spark notebooks with code that defines the schema/tables and commit those
3. Use database projects (.sqlproj) for more structured SQL components
4. Implement CI/CD pipelines that deploy schema changes through automation

For objects that can't be effectively version-controlled:

• Document them thoroughly in a wiki or markdown files in your repo
• Consider implementing a change management process outside of DevOps
• Use feature flags where possible to control rollout of changes

One approach that's worked for my team is creating a deployment framework using PowerShell/Python scripts that interact with the Fabric REST APIs to automate deployments of components that don't work natively with git.

Hope this helps with your implementation! Feel free to ask if you need more specifics on any particular component.

If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.