Two-Tier Encrypted Offline Root PKI in Azure Key Vault & Managed HSM

By Seamus McBride · Principal Cloud, Security, PKI & DPKI Architect · November 2026

Most enterprise PKI modernisations stall for the same reason: teams lift legacy Active Directory Certificate Services (AD CS) straight into cloud VMs, leave root keys reachable over the network, and store static service credentials in CI/CD pipelines. In regulated banking and defence environments, that fails audit before day one.

1. The Two-Tier Trust Boundary

A production-grade cloud PKI separates the root of trust from daily certificate issuance:

[Tier 1: Air-Gapped Offline Root CA]  -- (Dual-control ceremony) -->  [CRL / AIA Static Store]
                 |
         (Signs Sub-CA Cert)
                 v
[Tier 2: HSM-Backed Issuing CA (Azure Managed HSM / Thales)]
                 |
     (Managed Identity · Zero Secrets)
                 v
[ACME / EST / SCEP Automation] --> Workloads, Devices, mTLS, Entra ID

2. Prove Recovery Before Production: 36 Automated Acceptance Tests

A PKI design on slides is worthless until you prove it survives renewal, rollback, and CA loss. My 4-module PKI modernisation lab validates every build against 36 automated acceptance tests before sign-off:

Need this architecture reviewed or built for Q1 2027?
Available from January 2027 for Principal PKI/DPKI architecture contracts (B2B Ltd / Outside IR35) or 5–10 day fixed-scope readiness sprints. View my 2026 CV (PDF) or request access to the Controlled DPKI Briefing.