Microsoft.Network routeTables/routes 2020-11-01

The routeTables/routes resource type can be deployed to: Resource groups.

To learn about resource group deployments, see Bicep or ARM template.

Template format

To create a Microsoft.Network/routeTables/routes resource, add the following Bicep or JSON to your template.

resource symbolicname 'Microsoft.Network/routeTables/routes@2020-11-01' = {
  name: 'string'
  parent: parentSymbolicName
  properties: {
    addressPrefix: 'string'
    hasBgpOverride: bool
    nextHopIpAddress: 'string'
    nextHopType: 'string'
  }
}

Property values

routeTables/routes

Name Description Value
type The resource type

For Bicep, set this value in the resource declaration.
'Microsoft.Network/routeTables/routes'
apiVersion The resource api version

For Bicep, set this value in the resource declaration.
'2020-11-01'
name The resource name

See how to set names and types for child resources in Bicep or JSON ARM templates.
string (required)
parent In Bicep, you can specify the parent resource for a child resource. You only need to add this property when the child resource is declared outside of the parent resource.

For more information, see Child resource outside parent resource.
parentSymbolicName
properties Route resource. RoutePropertiesFormat

RoutePropertiesFormat

Name Description Value
addressPrefix The destination CIDR to which the route applies. string
hasBgpOverride A value indicating whether this route overrides overlapping BGP routes regardless of LPM. bool
nextHopIpAddress The IP address packets should be forwarded to. Next hop values are only allowed in routes where the next hop type is VirtualAppliance. string
nextHopType The type of Azure hop the packet should be sent to. 'Internet'
'None'
'VirtualAppliance'
'VirtualNetworkGateway'
'VnetLocal'

Quickstart templates

The following quickstart templates deploy this resource type.

Template Description
VNS3 network appliance for cloud connectivity and security.

Deploy to Azure
VNS3 is a software only virtual appliance that provides the combined features and functions of a security appliance, application delivery controller and unified threat management device at the cloud application edge. Key benefits, on top of cloud networking, always on end to end encryption, federate data centres, cloud regions, cloud providers, and/or containers, creating one unified address space, attestable control over encryption keys, meshed network manageable at scale, reliable HA in the cloud, isolate sensitive applications (fast low cost Network Segmentation), segmentation within applications, Analysis of all data in motion in the cloud. Key network functions; virtual router, switch, firewall, vpn concentrator, multicast distributor, with plugins for WAF, NIDS, caching, proxy, load balancers and other layer 4 thru 7 network functions, VNS3 doesn't require new knowledge or training to implement, so you can integrate with existing network equipment.