Episode Details

Modern cloud platforms don't fail because Azure isn't powerful enough—they fail because governance, automation, and developer experience weren't designed to scale together. In this episode of the M365 FM Podcast, host Mirko Peters explores how Azure Bicep evolves from a simple Infrastructure as Code language into the foundation of enterprise platform engineering. Rather than focusing on syntax, this deep dive examines the architectural principles that allow organizations to build Azure Landing Zones, governance models, subscription strategies, reusable modules, and self-service platforms that enable teams to innovate without sacrificing security or compliance. The episode challenges one of the biggest assumptions in enterprise IT: that tighter control automatically creates better governance. Instead, you'll discover why modern cloud platforms succeed by making the governed path the easiest path. From subscription vending and management groups to policy-as-code, FinOps, observability, and platform engineering, this episode provides a blueprint for designing Azure environments that remain agile as organizations grow.

WHY LANDING ZONES ARE REALLY GOVERNANCE MODELS
Azure Landing Zones are often presented as technical architectures, but they're much more than networking diagrams and subscription hierarchies. Every decision encoded in a Bicep module determines who can deploy infrastructure, who owns resources, how quickly teams can provision environments, and how governance flows across the organization. The episode explains why successful cloud platforms move away from gatekeeper governance toward enablement, replacing manual approvals with automated guardrails that empower teams while maintaining security and compliance. 

BUILDING FOR AGILITY, NOT CONTROL
Many enterprises unintentionally create Shadow IT by making official infrastructure too slow to consume. Instead of preventing risk, excessive governance often encourages developers to work around official processes. Topics include:

• Subscription vending
• Self-service infrastructure
• Platform engineering
• Developer experience
• Shadow IT
• Governance as Code
• Automation
• Azure Landing Zones
• Organizational agility
• Cloud operating models

You'll learn why reducing friction often improves security more effectively than adding additional approval processes.

SCALING AZURE WITH REUSABLE BICEP MODULES
As organizations grow, infrastructure cannot rely on copy-and-paste templates. Reusable, versioned Bicep modules become the building blocks for enterprise platforms. The discussion explores:

• Azure Verified Modules (AVM)
• Module registries
• Semantic versioning
• Infrastructure contracts
• Composition patterns
• Parameter design
• Shared variables
• Resource modules
• Solution modules
• Version control

Rather than maintaining hundreds of custom templates, organizations can publish standardized modules that continuously evolve while maintaining compatibility across teams.

MANAGEMENT GROUPS, POLICY & PLATFORM GOVERNANCE
Governance begins long before a resource is deployed. This episode explains how Management Groups, Azure Policy, RBAC, and Policy Initiatives combine to create scalable governance models that automatically enforce organizational standards. Instead of treating policies as deployment blockers, you'll discover how audit-first strategies, policy-as-code, and automated compliance enable organizations to maintain security without slowing down innovation. 

PLATFORM ENGINEERING AND THE GOLDEN PATH
The role of central IT is changing. Rather than acting as infrastructure gatekeepers, platform teams increasingly operate as internal product teams. The episode explores how self-service infrastructure, golden paths, reusable te