Variable Libraries & Best Practices
Environment-specific configurations; avoiding hardcoded values to improve maintainability.
Event
Activities tracked
4
๐ฏ The Problem: Someone overwrote the production report. Again. No one knows what changed. There's no way to roll back. Manual deployments at 11 PM on Friday - because that's when "no one is using the system." ๐ก This Evening: We'll bring professional DevOps to Fabric. Git integration, deployment pipelines, variable libraries - the practices that make BI enterprise-ready. โฑ๏ธ Save yourself: The 3 AM "we broke production" calls. Proper CI/CD means confident deployments, every time. What you'll learn: ๐ท๏ธ Sensitivity Labels - Data classification and protection\, and WHY labels flow with the data\, not the container (data stays protected when copied) ๐ Microsoft Purview - Unified governance across Azure and Fabric\, and WHY Purview is the governance control plane (one place for all policies) ๐ Git Integration - Source control for Fabric items\, and WHY Git enables collaboration and rollback (version history for everything!) ๐ Deployment Pipelines - Dev โ Test โ Prod promotion\, and WHY pipelines beat manual deployments (one click\, no errors) ๐ Variable Libraries - Environment-specific configurations\, and WHY hardcoded values kill maintainability (connection strings\, paths) DevOps Flow: Developer โ Git Commit โ PR Review โ Merge โ Deployment Pipeline โ DEV โ TEST โ PROD (each with its own Variables) Who should attend: Developers adopting DevOps for BI, Platform teams building CI/CD, Security teams implementing governance Agenda:
Sessions & talks
Showing 1โ4 of 4 ยท Newest first
Environment-specific configurations; avoiding hardcoded values to improve maintainability.
Dev โ Test โ Prod promotion; pipelines beat manual deployments.
Source control for Fabric items; collaboration and rollback via version history.
Data classification and protection; why labels flow with the data and governance via Microsoft Purview.