Skip to content
This repository has been archived by the owner on May 12, 2024. It is now read-only.

Key vaults need to be created using Azure defaults and not "purge protection" enabled #103

Closed
robsmi-msfte opened this issue Sep 8, 2021 · 1 comment · Fixed by #104
Closed
Assignees

Comments

@robsmi-msfte
Copy link
Contributor

The AVD blueprint 'Keyvault.json' artifact current creates a key vault with the "purge protection" setting enabled. This is not the Azure default. The problem is that once this key vault is created, purge protection cannot be disabled, and that key vault will be in soft delete state until the retention period expires.

@robsmi-msfte robsmi-msfte self-assigned this Sep 8, 2021
@robsmi-msfte robsmi-msfte linked a pull request Sep 8, 2021 that will close this issue
Merged
@robsmi-msfte
Copy link
Contributor Author

Edited the 'keyvault.json' artifact and removed the lines that set "soft delete" and "purge protection" settings. Now the key vault is created using Azure defaults. Also the key vault API versions were updated in the artifact file.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant