ef571d1e1d
Adding Microsoft SECURITY.MD |
||
---|---|---|
AKVStorageAccountRotation | ||
AKVStorageAccountRotationHttp | ||
ARM-Templates | ||
.deployment | ||
.funcignore | ||
.gitignore | ||
CHANGELOG.md | ||
CONTRIBUTING.md | ||
LICENSE.md | ||
Project-Template-Instructions.md | ||
README.md | ||
SECURITY.md | ||
host.json | ||
profile.ps1 | ||
proxies.json | ||
requirements.psd1 |
README.md
KeyVault-Secrets-Rotation-StorageAccount-PowerShell
Functions regenerate individual key (alternating between two keys) in Storage Account and add regenerated key to Key Vault as new version of the same secret.
Features
This project framework provides the following features:
-
Rotation function for StorageAccount key triggered by Event Grid (AKVStorageAccountRotation)
-
Rotation function for Storage Account key triggered by HTTP call (AKVStorageAccountRotationHttp)
-
ARM template for function deployment with secret deployment (optional)
-
ARM template for adding storage account key to existing function with secret deployment (optional)
Getting Started
Functions require following information stored in secret as tags:
- $secret.Tags["ValidityPeriodDays"] - number of days, it defines expiration date for new secret
- $secret.Tags["CredentialId"] - Storage Account credential id (i.e. key1/key2)
- $secret.Tags["ProviderAddress"] - Storage Account Resource Id
You can create new secret with above tags and Storage Account key as value or add those tags to existing secret with Storage Account key. For automated rotation expiry date will also be required - key vault triggers 'SecretNearExpiry' event 30 days before expiry.
There are two available functions performing rotation:
- AKVStorageAccountRotation - event triggered function, performs storage account key rotation triggered by Key Vault events. In this setup Near Expiry event is used which is published 30 days before expiration
- AKVStorageAccountRotationHttp - on-demand function with KeyVaultName and Secret name as parameters
Functions are using Function App identity to access Key Vault and existing secret "CredentialId" tag with storage account key id (key1/key2) and "ProviderAddress" with Storage Account Resource Id.
Installation
ARM templates available:
- Secrets rotation Azure Function and configuration deployment template - it creates and deploys function app and function code, creates necessary permissions, Key Vault event subscription for Near Expiry Event for individual secret (secret name can be provided as parameter), and deploys secret with Storage Account key (optional)
- Add event subscription to existing Azure Function deployment template - function can be used for multiple services for rotation. This template creates new event subscription for secret, necessary permissions to existing function and deploys secret with Storage Account key(optional).
Demo
You can find example for Storage Account rotation in tutorial below: Automate the rotation of a secret for resources that have two sets of authentication credentials
Youtube: https://youtu.be/qcdVbXJ7e-4
This project was generated using this template. You can find instructions here