Constantin Hager
Microsoft Cloud & Infrastructure Specialist focused on automation
📋 Biography
I'm a systems engineer specializing in infrastructure, automation, and cloud technologies, with a strong focus on building reliable, maintainable, and scalable environments. My work centers on Infrastructure as Code, where I leverage Terraform, ARM Templates, and modern DevOps tooling to streamline provisioning, standardize deployments, and reduce operational complexity. With a background in SQL Server administration, I'm using extensive automation practices with dbatools. Across projects, I'm advocating for clean automation patterns, reproducible environments, and cloud‑ready architectures. My approach blends hands‑on engineering with a DevOps mindset, ensuring that infrastructure, applications, and data services integrate seamlessly in modern cloud environments. I organize the PowerShell User Group Inn‑Salzach in Germany, where we meet once a month to discuss PowerShell and share knowledge within the community.
✨ High-Impact Contributions 2
As a Managed Service Provider, whether we're designing a new Entra ID tenant or taking over an existing one, we’re often faced with the same challenge: understanding what’s already in place and where to begin. By the end of the project, we need a clear picture of the tenant’s security posture and a roadmap for what to tackle next. Continuous reporting is also essential, so the customer always knows the current state of their environment. Maester a PowerShell-based security test automation framework built on Pester ships with ready-to-use tests and generates rich, visual reports that make it easy to spot misconfigurations. It integrates seamlessly with GitHub Actions, Azure DevOps, and Azure Automation, enabling us to run it across environments and deliver actionable insights to our customers. In this session, I’ll walk you through how we deploy Maester in an Entra ID tenant, run it via GitHub Actions, and extend it with a self written custom test.
Inconsistent Visual Studio Code setups across teams and devices often leads to chaos, not just in formatting, but in how code is written, linted, and reviewed. When everyone brings their own Visual Studio Code configuration, even meaningful logic changes can lead to style-related diffs: mismatched braces, inconsistent quotes, or unexpected newlines. In this session, you'll learn how to build a standardized, portable VSCode environment for PowerShell development using DevContainers. Whether you're on a work laptop, personal machine, or even a tablet, your dev setup stays consistent. And with GitHub Codespaces, you can run that same environment in the browser.