No More Spec-ulation: AI Agent Teams Building Production-Grade IaC

We want this session to end with code another engineer can read, test, and use.

In the past year, Copilot CLI became generally available, skills and MCP spread across Copilot surfaces, and Squad reached 1.0. Martin and Haflidi show how native GitHub Copilot CLI features and Squad work together on an existing AKS Terraform codebase. The outcome is a reusable infrastructure module, documented and tested around a clear contract, with a consumption example for an existing Azure landing zone. The primary path uses private Corp networking and pre-provisioned platform services, not a new public standalone environment.

We start with the files and decisions that shape the work. Native Plan mode makes the proposed change visible before implementation. Reviewed files, instructions, skills, and MCP lookups focus the agent. Squad adds roles, routing, ownership, handoffs, and repository-backed decisions. Three narrow agent profiles in the repository are a coder, a validator, and a separate reviewer. The validator has no edit tool, but its shell can still write files; instructions and native approval prompts enforce its command list. They narrow lanes without pretending they are sandboxes. Parallel work stays bounded; humans review changes.

Code qualification comes first. The live session shows genuine new Copilot CLI execution with Squad selected from a disclosed clean checkpoint, not the first-ever implementation. Both speakers narrate the decisions live. We'll inspect the plan, follow a handoff, read a meaningful failed check, and discuss the repair. We'll also use diff and review tools, resume with decisions intact, and explain model, context, and usage controls. Worktrees, recovery, bounded automation, and cloud delegation stay in a concise reference section.

You'll leave able to choose an appropriate CLI or Squad workflow, define a module boundary, and connect an agent's claim to evidence. You'll also know why passing local tests, a reviewed Terraform plan, and observed Azure behavior are different milestones.

Public code and examples stay separate from private inputs, identities, backend/state, and secrets. The October 5 Azure validation is cited only as sanitized, revision-bound evidence, not reusable environment data.

Revolutionizing workload deployments in Azure DevOps & GitHub Actions within Private Network.

In this session, we are going to explore the different ways of how to deploy your Infrastructure within a private and secure network. We'll have a look at some new, fresh and exciting ways to host/inject your Azure DevOps Agents and Github Action Runners directly within your own virtual network. Whether it's deploying your Infrastructure as Code, accessing your Terraform state files or pushing web applications to App Environments, these agents can communicate safely with your workloads behind Azure's private endpoints and firewalls.

I'll go over and quickly compare the "old" way of hosting your Self-Hosted Agents within a Virtual machine scale set (VMSS) or Container Instances/Apps to the new ways that are out there. We will have deeper look at a new and fresh Microsoft product called MDP or Managed DevOps Pools. MDP will enable you to use fully Azure managed Infrastructure and managed Images as well as bringing your own custom images if needed for deploying self-hosted agents within Azure DevOps while being injected into your own virtual network. In addition we will also have a quick look at a new feature available of using Github-Hosted Agents that can now be injected into your own virtual network, both of these features make it possible to communicate safely with services that are behind private endpoints and/or resource firewalls, like Storage Account & Key Vault Firewall to mention few, leaving you with less amount of administration over custom images, virtual machine scale sets and infrastructure for those hosted agents allowing you to focus on something else.

Introduction to Azure Managed DevOps Pools

Microsoft recently introduced a new product called Managed DevOps Pools (MDP). MDP is the next evolution of Virtual Machine Scale Set (VMSS) and is entirely hosted by Microsoft, in this session I'm going to give you a quick overview of the product, mention some key benefits, and show you how to get started with a small demo.

I'm dreaming of a secure deployments.

Welcome to this festive video session, where I will guide you on how to build your own winter wonderland of code deployment, with secure infrastructure inside a cozy private network in Azure using the latest and greatest technology and scalable and almost non-costly self-hosted agents running in Azure for GitHub and Azure DevOps.

We will have a blast exploring the demos as I explain the various scenarios, and of course, you will not be left empty-handed as I will share the code and tutorials as a gift to you so you can try this out in your own environment.

Azure Governance with Azure Enterprise Policy As Code.

Azure Governance is a set of capabilities that help you control and protect your applications and resources in Azure. One of the key components of Azure Governance is Azure Policy, which allows you to define and apply policies for your cloud resources to help you ensure that your cloud environment follows the rules and best practices that you set for your organization. In this technical session, you will learn how to get started with the Azure Enterprise Policy As Code Framework (EPAC), which is a solution that helps you deploy and manage Azure Policies using code. You will also learn how Azure Enterprise Policy As Code (EPAC) can support your Azure Governance strategy and make it easier to implement and maintain policies at scale.