Allow users to manually alter the default outbound timeout of 4 minutes or create an ARM version of the classic reserved IPs.
Currently, there is no way to configure the outbound timeout for TCP connections, which is set at 4 minutes and unalterable. Some processes and connections may lay dormant beyond this 4-minute restriction (e.g. complex multi-database query connections). Users should be able to either alter the 4-minute restriction per VM instance, or there should be an ARM version of the classic reserved IPs which bypasses the NAT process used for outbound TCP connections (and such an IP would not be subject to the restriction.