I recently came across an issue while working with colleagues on a shared demo environment, which required notification of the entire group should anyone change the local admin password or redeploys said environment with a password of their own. This challenge prompted me to begin investigating Azure Key Vault as a potential solution to address this. Recently, the PowerShell Team announced the general availability of their SecretManagement and SecretStore modules which helps users manage secrets through a common set of cmdlets to interface with the vaults. Administrators can utilise this extensible model, where local and remote vaults can be registered and unregistered for use in accessing and retrieving secrets.
I have recently created a blog post detailing the steps required to harness PowerShell SecretManagement modules in the hopes that others would find the solution helpful.
As always, our team grateful when the community shares input in helping us create technical articles, demo videos and interviews. Active conversations also take place on Twitter via the #AzOps hashtag. Feel free to reach out with any of your questions as our team is always happy to help.
- This article was written for the Monthly TechNet UK IT Pro Newsletter – sign up today!
- Deploy Windows Server
- Perform post-installation configuration of Windows Server
- Select Windows Server editions, servicing options, and activation