Hybrid use of Terraform for infrastructure andAnsible for configuration is common on Azure, but the two toolsare often joined only by ad hoc scripts and fragile handoffs in CIpipelines. Runbook Mesh proposes a small MCP based controlplane that treats Terraform and Ansible as one coordinatedchange unit rather than two independent stages. Azure DevOpstriggers an MCP server that drives a deployment state machine:it receives Terraform plans and apply results, derives a dynamicAnsible inventory from Terraform outputs, and orchestratesconfiguration playbooks with drain, cordon, and health checksfor VM scale sets, AKS nodes, and virtual machines. TheMCP enforces simple invariants on ordering, handoff safety,and rollback reachability, and packages each deployment intoa witness bundle containing plan digests, state and inventoryhashes, play outcomes, and Azure Resource Graph snapshots.The result is an Azure native pattern where infrastructure andconfiguration share a single timeline, a defined rollback path, anda tamper evident change ledger suited to regulated environments.