Vault not found in subscription fix while Azure Subscription has many vaults #609
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ix the issue with vault could not be found in the subscription. This happens when the subscription has too many vaults and they do not fit into the returning payload of az api
santhoshb-msft
added
enhancement
santhoshb-msft
approved these changes
Dec 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While using this repo to deploy my Azure Marketplace offers, I faced an error: The Vault '{vaultname}' not found within subscription.
After investigating a bit, I found that
az keyvault set-policy --name $KeyVault --object-id $WebAppNamePortalId --secret-permissions get list --key-permissions get list --output $azCliOutputin Deploy.ps1 has some kind of a paging by default and if your Azure Subscription has many vaults, you newly created might not be returned. This leads toThe Vault '{vaultname}' not found within subscription.error and unpredictable behavior of the solution.I found an easy fix for this issue by adding a filter by the resource group.
Hope that it will be helpful to somebody.