Azure Infrastructure as Code built entirely with Azure Verified Modules (AVM) and Terraform. Every deployment is designed around private networking — services communicate over private endpoints, clusters run as private clusters, and public access is disabled wherever possible.

A fully private AKS environment where the Kubernetes API server is only reachable through a private endpoint, all egress traffic is forced through Azure Firewall, and container images are pulled from a private ACR over a private endpoint — nothing is exposed to the public internet. Based on the sg-aks-workshop reference architecture.

Key Components:

A fully private Azure Red Hat OpenShift (ARO) cluster where both the API server and ingress are set to Private visibility — nothing is exposed to the public internet. The cluster uses managed identities with platform workload identity federation (no service principal), and all egress is routed through a NAT Gateway with a static public IP.

Key Components:

A network-isolated Azure Machine Learning workspace where every supporting service — Key Vault, Storage, Container Registry — is locked behind private endpoints. The ML workspace itself uses managed VNet isolation (AllowInternetOutbound mode), so compute instances and clusters never sit on a public network.

Key Components:

See azuremachinelearning-terraform/README.md for full details.

A simple GPU VM for PyTorch development and Jupyter Notebook — no complex networking, just a VNet + NSG + public IP. Designed for remote ML experimentation from VS Code.

Key Components:

See pytorchlab-terraform/README.md for full details.

A network-isolated Microsoft Foundry (AI Foundry) deployment ready to run hosted agents — AI Services account, Foundry project, account- + project-level Capability Hosts, container registry, Key Vault (Bring-Your-Own), and Azure Monitor Private Link Scope — all locked behind private endpoints with public access disabled and local auth turned off across every backing service. The AI account uses VNet-injected agent networking, and a private Container Apps Environment is wired into the MCP subnet for custom tool servers. Default region: swedencentral.

Key Components:

Companion test harnesses and code projects:

• mcp-server/ — source for the multi-auth MCP container that runs in the private Container Apps Environment. Includes a pinned Dockerfile, a build_and_push.sh script targeting the private ACR, and the FastMCP Python server (add, time tools + an OAuth-protected resource metadata endpoint). The container app itself is provisioned by mcp.tf via the AVM container-app module.
• hosted-agent-test/ — end-to-end workflow for building a hosted-agent container image, pushing to the private ACR, registering a hosted agent version that consumes the private MCP server, and invoking it via the Responses API with App Insights tracing.
• ampls-test/ — REST-level probe that proves the App Insights private ingestion path end-to-end (validates AMPLS Phase E-1 → E-2 → E-3 rollout from inside and outside the VNet).
• private-mcp-test/ — SDK tests for agents calling AI Search and private MCP servers over the Data Proxy.

• Terraform >= 1.9
• Azure CLI (authenticated via az login)
• WireGuard tools (wg command) — for VPN key generation and client config
• An Azure subscription with sufficient permissions

Each project deploys a WireGuard VPN gateway. You need a server key pair and a client key pair before running terraform apply.

# Generate server key pair
wg genkey > server.key
wg pubkey < server.key > server.pub
# Generate client key pair
wg genkey > client.key
wg pubkey < client.key > client.pub

Pass the keys as environment variables so Terraform can configure the VPN gateway:

export TF_VAR_wireguard_server_private_key=$(cat server.key)
export TF_VAR_wireguard_client_public_key=$(cat client.pub)

cd <project-folder>/
terraform init
terraform plan -out=tfplan
terraform apply tfplan

After terraform apply completes, generate the WireGuard client config using the helper script:

./generate-wg0-conf.sh client.key server.key

This reads Terraform outputs (public IP, VNet CIDR) and produces a wg0.conf file. Use it with WireGuard client to connect to newly created environment.

Once connected, you can resolve private DNS zones and reach all private endpoints from your local machine.