Microsoft.Web serverfarms/virtualNetworkConnections/routes 2019-08-01

The serverfarms/virtualNetworkConnections/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.Web/serverfarms/virtualNetworkConnections/routes resource, add the following Bicep or JSON to your template.

resource symbolicname 'Microsoft.Web/serverfarms/virtualNetworkConnections/routes@2019-08-01' = {
  name: 'string'
  kind: 'string'
  properties: {
    endAddress: 'string'
    routeType: 'string'
    startAddress: 'string'
  }
}

Property values

serverfarms/virtualNetworkConnections/routes

Name Description Value
type The resource type

For Bicep, set this value in the resource declaration.
'Microsoft.Web/serverfarms/virtualNetworkConnections/routes'
apiVersion The resource api version

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

See how to set names and types for child resources in Bicep or JSON ARM templates.
string (required)
kind string
properties VnetRouteProperties

VnetRouteProperties

Name Description Value
endAddress The ending address for this route. If the start address is specified in CIDR notation, this must be omitted. string
routeType The type of route this is:
DEFAULT - By default, every app has routes to the local address ranges specified by RFC1918
INHERITED - Routes inherited from the real Virtual Network routes
STATIC - Static route set on the app only

These values will be used for syncing an app's routes with those from a Virtual Network.
'DEFAULT'
'INHERITED'
'STATIC'
startAddress The starting address for this route. This may also include a CIDR notation, in which case the end address must not be specified. string