Change a key vault tenant ID after a subscription move
This article has been updated to use the new Azure PowerShell Az module. To learn more about the new Az module and AzureRM compatibility, see Introducing the new Azure PowerShell Az module. For installation instructions, see Install Azure PowerShell.
Q: My subscription was moved from tenant A to tenant B. How do I change the tenant ID for my existing key vault and set correct ACLs for principals in tenant B?
When you create a new key vault in a subscription, it is automatically tied to the default Azure Active Directory tenant ID for that subscription. All access policy entries are also tied to this tenant ID. When you move your Azure subscription from tenant A to tenant B, your existing key vaults are inaccessible by the principals (users and applications) in tenant B. To fix this issue, you need to:
- Change the tenant ID associated with all existing key vaults in this subscription to tenant B.
- Remove all existing access policy entries.
- Add new access policy entries that are associated with tenant B.
For example, if you have key vault 'myvault' in a subscription that has been moved from tenant A to tenant B, here's how to change the tenant ID for this key vault and remove old access policies.
Select-AzSubscription -SubscriptionId YourSubscriptionID $vaultResourceId = (Get-AzKeyVault -VaultName myvault).ResourceId $vault = Get-AzResource –ResourceId $vaultResourceId -ExpandProperties $vault.Properties.TenantId = (Get-AzContext).Tenant.TenantId $vault.Properties.AccessPolicies = @() Set-AzResource -ResourceId $vaultResourceId -Properties $vault.Properties
Because this vault was in tenant A before the move, the original value of $vault.Properties.TenantId is tenant A, while (Get-AzContext).Tenant.TenantId is tenant B.
Now that your vault is associated with the correct tenant ID and old access policy entries are removed, set new access policy entries with Set-AzKeyVaultAccessPolicy.
If you have questions about Azure Key Vault, visit the Azure Key Vault Forums.
We’d love to hear your thoughts. Choose the type you’d like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.