Terraforming Our Tenant: Self-Serving Apps as Code
summary
NBIM codifies Azure AD app management with Terraform plus custom modules and API scripts, targeting 600 applications and using YAML-based templates for human-friendly configs. Each app uses a separate state per app and a reusable import flow so teams can switch gradually after a six-month pilot. The build trades Terraform plan-level dependency mapping for isolation, requires Graph API handling and provider pinning, and yields concrete gains: halved support tickets and reusable pipelines for ongoing self-service.
AI-written summary · about
chapters (9)
- 0:00Introduction and speaker intro
- 2:27About NBIM and the speaker
- 4:30Our Azure AD tenant challenges
- 8:45Overcoming the Brownfield problem
- 11:28Terraform design principles
- 17:31Migration and user workflow
- 21:25Reality check and costs
- 23:30Tangible benefits achieved
- 25:16Summary and closing
related talks
50mTerraform 101: Building Repeatable, Secure Azure Infrastructure
46mFull Spectrum Terraform — Choosing and Combining Azure Providers Like a Pro
37mTerraform & CI/CD
50mFrom Code to Compliance: Enforcing Azure Security with Terraform and...
54mInfrastructure as Code with Terraform on Azure
43mDemystifying Terraform - "Hardcore" to Core Infrastructure... Tool
01h 04mIaC Forged in Code: ARM/Bicep vs Terraform vs Pulumi
34mTerraform: A Novel About Modules, Providers, Security, and Pain