A colleague came to me with an interesting request:
We want to put Key Vault behind a firewall, but when we do that it means that Azure Data Factory can no longer access the secrets. Is there a way to whitelist the IP addresses for a given Azure Data Centre?
The short answer is: Yes.
By default, the following option is enabled on Azure Key Vault under the Firewalls and virtual networks blade.
For most users, having unrestricted access from external networks to a resource that holds secrets, certificates and other sensitive information is a big red flag.
If we choose to only allow access from Selected Networks we get the following options opening up for us:
Note that trusted Microsoft services is not an extensive list and does not include Azure Data Factory.
Therefore we need to whitelist a series of IP Addresses in the firewall rules. The list of IP Addresses are published by Microsoft and are updated on a weekly basis. The IP addresses are published in an XML document, which isn’t always the best format when one needs to update firewalls in Azure.
To update the Firewall in Azure, we’re going to use PowerShell to shred the XML and extract the IP ranges for a given region. Then, we’re going to use the updated Azure PowerShell module to register the IP ranges against the Key Vault.
Using the last command, we can check that the IP ranges have been registered successfully. You should see something like:
There we have it, explicit IP whitelisting of Azure Data Centres so we can lock down Azure resources, only opening up access when we need to.
Key Vault is currently limited to 127 firewall rules. If you are adding a region with more than 127 IP ranges, you might have an issue…