Azure Firewall May 2020 updates

Two new key features are now available in Azure Firewall – [forced tunnelling](https://docs.microsoft.com/en-us/azure/firewall/forced-tunneling) and [SQL FQDN filtering](https://docs.microsoft.com/en-us/azure/firewall/sql-fqdn-filtering). Additionally, we’re increasing the limit for [multiple public IP addresses](https://docs.microsoft.com/en-us/azure/firewall/overview#multiple-public-ip-addresses) from 100 to 250 for both DNAT and SNAT. This feature will be available to Azure Firewall customers by default, so there’s no need to sign up. Use these features to achieve these scenarios: * Configure a default route (0.0.0.0/0) on the AzureFirewallSubnet or publish a default route to the firewall over BGP, to send all traffic to on-premises or nearby NVA. * Filter outbound SQL traffic using application rules. Support is for SQL proxy mode only. Redirect mode support is tentatively planned for later in 2020\. * Use up to 250 public IP addresses with Azure Firewall for both DNAT and SNAT. These features are included in the Azure Firewall standard SKU, so there is no change in the price. [Learn more about multiple public IP](https://docs.microsoft.com/en-us/azure/firewall/overview#multiple-public-ip-addresses) [Learn more about SQL filtering](https://docs.microsoft.com/en-us/azure/firewall/sql-fqdn-filtering) [Learn more about forced tunnelling](https://docs.microsoft.com/en-us/azure/firewall/forced-tunneling) * Security