Managing and Rotating Secrets with Azure Key Vault, Managed Services, and some automation – Part 1
Secret rotation is not a new problem. In cloud-based environments many services implement secret-based authentication schemes. For many organizations, these secrets must be rotated on a regular schedule. In addition to the actual problem of rotating the access keys, there exists a problem of how these newly rotated credentials are propagated to all the applications and systems that utilize them. In this multi-part blog series, I will discuss a solution that, through automation, addresses both the scheduled rotation and dependency notification/update requirements.
