Skip to content

[Bug / Issue]: Key Vault name is already taken #3265

Open
@david-haver02862

Description

@david-haver02862

Jumpstart Solution

  • Jumpstart ArcBox
  • Jumpstart LocalBox
  • Jumpstart Agora
  • A specific Jumpstart scenario
  • Jumpstart Drops
  • Something else

What happened?

I am trying to deploy the Azure Arch Just Start for IT Pros (https://jumpstart.azure.com/azure_jumpstart_arcbox/ITPro) but the deployment fails because the Key Vault name is not unique. I have opened MS Support case # 2506270040003352 on this and support engineer is not able to help fix this. Can someone fix the template?

We need a URL from you

https://jumpstart.azure.com/azure_jumpstart_arcbox/ITPro

Deployment Method

Azure Portal

Relevant log output.

{"code":"DeploymentFailed","target":"/subscriptions/954f361d-4e4b-417e-b158-87a4dba0d758/resourceGroups/AzureArcBox-RG/providers/Microsoft.Resources/deployments/mgmtArtifactsAndPolicyDeployment","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.","details":[{"code":"ResourceDeploymentFailure","target":"/subscriptions/954f361d-4e4b-417e-b158-87a4dba0d758/resourceGroups/AzureArcBox-RG/providers/Microsoft.Resources/deployments/keyVaultDeployment","message":"The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'.","details":[{"code":"DeploymentFailed","target":"/subscriptions/954f361d-4e4b-417e-b158-87a4dba0d758/resourceGroups/AzureArcBox-RG/providers/Microsoft.Resources/deployments/keyVaultDeployment","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.","details":[{"code":"VaultAlreadyExists","message":"The vault name 'arcboxwfkkyotfk2bri' is already in use. Vault names are globally unique so it is possible that the name is already taken. If you are sure that the vault name was not taken then it is possible that a vault with the same name was recently deleted but not purged after being placed in a recoverable state. If the vault is in a recoverable state then the vault will need to be purged before reusing the name. For more information about VaultAlreadyExists, soft delete and purging a vault follow this link https://go.microsoft.com/fwlink/?linkid=2147740."}]}]}]}

Code of Conduct and Licensing

  • I agree to follow this project's Code of Conduct and Licensing terms.

Metadata

Metadata

Assignees

Labels

Bug-IssueIt either shouldn't be doing this or needs an investigationNeeds-AttentionThis work item needs to be reviewed by a member of the core team

Type

Projects

Status

No status

Relationships

None yet

Development

No branches or pull requests

Issue actions