Microsoft.Network virtualHubs/bgpConnections 2020-05-01

The virtualHubs/bgpConnections 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/virtualHubs/bgpConnections resource, add the following Bicep or JSON to your template.

resource symbolicname 'Microsoft.Network/virtualHubs/bgpConnections@2020-05-01' = {
  name: 'string'
  properties: {
    peerAsn: int
    peerIp: 'string'
  }
}

Property values

virtualHubs/bgpConnections

Name Description Value
type The resource type

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

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

See how to set names and types for child resources in Bicep or JSON ARM templates.
string (required)
properties Properties of the bgp connection. BgpConnectionProperties

BgpConnectionProperties

Name Description Value
peerAsn Peer ASN. int
peerIp Peer IP. string

Quickstart templates

The following quickstart templates deploy this resource type.

Template Description
Create a Route Server in a New Subnet

Deploy to Azure
This template deploys a Route Server into a subnet named routeserversubnet.
Azure Route Server in BGP peering with Quagga

Deploy to Azure
This template deploys a Router Server and Ubuntu VM with Quagga. Two external BGP sessions are established between the Router Server and Quagga. Installation and configuration of Quagga is executed by Azure custom script extension for linux