Problem Overview
Storing secret values directly in tools creates operational risk (leaks, insecure sharing, and manual secret rotation). WOODY.IO supports Key Vault references so it can store a reference instead of the secret value, in both Connections and Notifications.
Solution
Use @KeyVault(...) references wherever supported so WOODY.IO never stores the secret content, only the reference.
Configuration
- In any supported password/secret field set: @KeyVault(<KeyVaultIdentifier>;<SecretName>)
- Ensure <KeyVaultIdentifier> is the WOODY.IO Key Vault configuration identifier (not the Azure Key Vault name).
Click here to read more about Key Vault References in WOODY.IO.
If you have any further questions, please feel free to Contact Us.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article