When we download secrets from Key Vault today, the firewall rule prevents the Agent from connecting to the vault. It seems very tedious to add the entire public Agent Pool IP range to the KV firewall rule since it's constantly changing. It would be very useful to have a setup similar to the implementation in SqlAzureDacpacDeployment@1.
Task name
No response
Describe your feature request here
When we download secrets from Key Vault today, the firewall rule prevents the Agent from connecting to the vault. It seems very tedious to add the entire public Agent Pool IP range to the KV firewall rule since it's constantly changing. It would be very useful to have a setup similar to the implementation in SqlAzureDacpacDeployment@1.