Update to module for storing passwords/secrets in Azure Key Vault along with meta data in an Azure Table
Updated a module I've been tinkering around with. The module's primary purpose is store and retrieve secrets (passwords) in an Azure Key Vault and corresponding metadata (like URLs, usernames, etc): TooManySecrets (yes, like Sneakers)
Still a bit early, but making progress:
- In PowerShell Gallery
- On GitHub
Take a look and let me know what ya think.
Posted Jan 20, 2020, 10:30 PM UTC
403
I have very limited experience in Azure. Can someone explain how Azure Key Vault compares to something like Azure Automation? I'm mainly looking for a way to store/retrieve a PS Credential object without exposing the password to the user.
The Key Vault is a secure repository. It's a place you can keep things protected, limit access to specific people or apps, and they can retrieve values dynamically.
Azure Automation is primarily about... automation. Its steps and run books can be configured to utilize key Vault values that are stored and shared locally, but it does have a local secure repository for its creds (assets).
They can work together such that your creds/secrets are stored in Key Vault and AzA pulls from there, then as the creds change you can have a process update the Vault without having to touch AzA.
Why you would use one over the other, if you have an account that is for a specific task and rarely changes you could easily store that as an AzA asset. If you had something that changed frequently and lots of different tasks and resources needed, key Vault would be better. And then a myriad of options that follow best practices between.
Oh okay, thank you!