Is your feature request related to a problem? Please describe.
We are using Terraform to create KeyVaults (KV) and add secrets to it.
The networking we have to use for the KV is pretty strict so that pretty much nothing leaves the network of the KV. But since we have that option enabled, we can't just start a Terraform Script in the Cloudshell from anywhere, we always have to use a jumphost or any server from inside the network itself which is annoying since all you do is start the script in the cloudshell.
As another option, we have to manually grab our current external azure cloudshell IP and add it to the networking firewall, so we can quickly add the secrets and then remove that IP again.
Describe the solution you'd like
A really easy solution would be to have the same checkbox option as the Azure CosmosDB, "Allow access from azure portal".
Describe alternatives you've considered
See above
Additional context
Is your feature request related to a problem? Please describe.
We are using Terraform to create KeyVaults (KV) and add secrets to it.
The networking we have to use for the KV is pretty strict so that pretty much nothing leaves the network of the KV. But since we have that option enabled, we can't just start a Terraform Script in the Cloudshell from anywhere, we always have to use a jumphost or any server from inside the network itself which is annoying since all you do is start the script in the cloudshell.
As another option, we have to manually grab our current external azure cloudshell IP and add it to the networking firewall, so we can quickly add the secrets and then remove that IP again.
Describe the solution you'd like
A really easy solution would be to have the same checkbox option as the Azure CosmosDB, "Allow access from azure portal".
Describe alternatives you've considered
See above
Additional context