Infrastructure as Code, DevOps & the Future of Azure with Maik van der Gaag [MVP]

What does it really take to build secure, scalable, and automated cloud environments in Microsoft Azure? In this episode of M365 FM, Mirko Peters sits down with Microsoft Azure MVP Maik van der Gaag to explore Infrastructure as Code, DevOps culture, Terraform, Bicep, GitHub, Azure automation, cloud governance, and the growing impact of AI on modern platform engineering. Drawing from more than 15 years of experience helping organizations modernize their technology landscapes, Maik shares practical lessons from real-world cloud transformations, enterprise Azure deployments, and large-scale automation projects. The conversation starts with Maik's journey from traditional software development and SharePoint projects into Azure cloud architecture, eventually becoming CTO at 3fifty and later Head of Technology for the Microsoft business at Data Balance. Along the way, he reflects on building technical communities, organizing user groups, and what he has learned from years of helping professionals navigate the rapidly changing cloud landscape.

THE STATE OF AZURE, CLOUD & HYBRID INFRASTRUCTURE

As organizations continue to evaluate cloud-first strategies, Maik discusses the shift he is seeing toward hybrid cloud and sovereign cloud models. While many organizations remain committed to Microsoft Azure, others are balancing public cloud investments with private datacenters and local infrastructure. The discussion explores how geopolitical concerns, compliance requirements, and business continuity planning are influencing modern cloud architecture decisions. Key takeaways:

• Why hybrid cloud is growing again
• The rise of sovereign cloud discussions
• Azure versus on-premises infrastructure
• Cloud transformation challenges
• Enterprise cloud strategy trends
• Security considerations for modern workloadsINFRASTRUCTURE AS CODE EXPLAINED

 Infrastructure as Code (IaC) has become one of the most important practices in cloud engineering. Maik breaks down the concept in simple terms, explaining how infrastructure can be represented as code, version-controlled, automated, and deployed consistently across environments. Rather than manually creating virtual machines, databases, networking components, and cloud resources, organizations can define their entire environment through reusable code. This approach reduces human error, improves consistency, accelerates deployments, and creates repeatable infrastructure patterns across development, testing, and production environments. Topics covered:

• What Infrastructure as Code actually means
• Why manual deployments create problems
• Reducing configuration drift
• Version control for infrastructure
• Automation and repeatability
• Cost savings through standardizationTERRAFORM VS BICEP

One of the most practical parts of the discussion focuses on Terraform and Microsoft Bicep. Maik explains the strengths and weaknesses of both approaches and why the right choice depends heavily on organizational requirements. While Bicep offers a streamlined Azure-focused experience and serves as an abstraction layer for ARM templates, Terraform provides multi-cloud flexibility across Azure, AWS, Google Cloud, Cloudflare, and many other platforms. The conversation also explores state management, extensibility, and the growing capabilities of modern Infrastructure as Code tooling. Key takeaways:

• Terraform vs Bicep
• ARM templates and Azure deployments
• State management concepts
• Multi-cloud infrastructure strategies
• Infrastructure extensibility
• Choosing the right tool for your organizationDEVOPS IS NOT A TOOL

One of the strongest messages from this episode is Maik's belief that DevOps is fundamentally about culture, processes, and collaboration rather than technology alone. Many organizations mistakenly focus on tools while ignoring the organizational changes required to achieve DevOps success. Maik explains why successful DevOps teams combine developers, operations professionals, security experts, and business stakeholders into integrated teams focused on delivering value. The discussion also covers Azure DevOps, GitHub Enterprise, GitOps, DevSecOps, and how organizations can build more effective engineering cultures. 

Topics discussed:

• DevOps as culture versus technology
• Why organizations struggle with DevOps
• Azure DevOps vs GitHub
• GitOps explained
• DevSecOps principles
• Building self-organizing teamsSECURITY, GOVERNANCE & SECRETS MANAGEMENT

Security remains a recurring theme throughout the conversation. Maik highlights one of the most common mistakes organizations make when moving to Azure: assuming cloud environments are automatically secure. The episode explores identity management, Microsoft Entra ID, MFA, Key Vault, managed identities, federated credentials, GitHub Actions, governance strategies, and best practices for protecting enterprise cloud environments.

Key takeaways:

• Azure sec...