Microsoft.Web sites/virtualNetworkConnections 2019-08-01

Template format

To create a Microsoft.Web/sites/virtualNetworkConnections resource, add the following JSON to the resources section of your template.

  "name": "string",
  "type": "Microsoft.Web/sites/virtualNetworkConnections",
  "apiVersion": "2019-08-01",
  "kind": "string",
  "properties": {
    "vnetResourceId": "string",
    "certBlob": "string",
    "dnsServers": "string",
    "isSwift": "boolean"
  "resources": []

Property values

The following tables describe the values you need to set in the schema.

Microsoft.Web/sites/virtualNetworkConnections object


In Bicep, type and apiVersion are specified in the first line of the resource declaration. Use the format <type>@<apiVersion>. Don't set those properties in the resource body.

Name Type Required Value
name string Yes Name of an existing Virtual Network.
type enum Yes For JSON -virtualNetworkConnections

See Set name and type for child resources.
apiVersion enum Yes For JSON - 2019-08-01
kind string No Kind of resource.
properties object Yes VnetInfo resource specific properties - VnetInfoProperties object
resources array No gateways

VnetInfoProperties object

Name Type Required Value
vnetResourceId string No The Virtual Network's resource ID.
certBlob string No A certificate file (.cer) blob containing the public key of the private key used to authenticate a Point-To-Site VPN connection.
dnsServers string No DNS servers to be used by this Virtual Network. This should be a comma-separated list of IP addresses.
isSwift boolean No Flag that is used to denote if this is VNET injection