With routes in Azure, you can change the default any to any routing within Azure to meet your needs.

The following screenshot shows the Azure service you need to look for when you want to implement an Azure route:

With routes, you can basically redirect traffic from one subnet to another location. The following screenshot shows the current offerings of that Azure service:

Within the setup part of this chapter, I will explain how to configure a custom route:

• Virtual network gateway: The traffic will be forwarded to another Azure gateway. This option can be used if you maybe want to send traffic via another gateway or route to its target. Or you have redirected all traffic to a Virtual Appliance and want specific traffic to bypass the appliance.
• Virtual network: Transfers traffic directly into another VNet. That could be used to transfer traffic from one VNet to another which can't be reached directly.
• Internet: Traffic will be send directly into the Internet.
• Virtual appliance: The traffic will be sent to a third-party virtual network device hosted in your Azure environment. That can be a Barracuda Next Generation Firewall or a Cisco Nexus device, for example.
• None: Traffic will be dropped and will not be routed.