Error: Keyvault already exists. about purviewlab HOT 1 CLOSED

Hi @hfleitas , the template generates a random string using the Azure Bicep guid function with the resource group name as an input. This random string is then used as part of the prefix for the deployed resources. For example, pvlab-{randomString}-keyvault.

Note: If you are deploying to the same resource group more than once, the guid function will generate the same random string. This is generally not an issue if the pre-existing resources have been deleted, but in the case of Azure Key Vault, it will typically perform a "soft delete" which then causes a conflict of "VaultAlreadyExists" when the template attempts to deploy a second time.

To solve this issue, you can either deploy to a new resource group OR purge the soft-deleted key vault. See these instructions on how to purge a soft-deleted key vault.

from purviewlab.