Hub Spoke Peering

[Parlax]

Hi,

I'm currently trying to get a Hub Spoke model working. The example from Azure is one big main.bicep file which deploys everything at once. Since we'll be having multiple projects I'm trying to create different Bicep files for the Hub and the Spokes.
This way we can have a vnetSpoke.bicep file in every project folder. Each project will be in it's own ResourceGroup.

In the vnetSpoke.bicep file I've created a reference to the existing vnetHub which resides in it's own ResourceGroup.

resource vnetHub 'Microsoft.Network/virtualNetworks@2021-02-01' existing = {
  name: 'vnet-hub'
  scope: resourceGroup('rg-hub')
}

Where the problem starts is when I try to create the peering. Once I deploy the template it will search in the rg-spoke ResourceGroup for the hub-vnet.

My peering looks as follows:

resource peerHubSpoke 'Microsoft.Network/virtualNetworks/virtualNetworkPeerings@2021-02-01' = {
  name: '${vnetHub.name}/peer-hub-to-spoke'
  properties: {
    allowVirtualNetworkAccess: true
    allowForwardedTraffic: true
    allowGatewayTransit: false
    useRemoteGateways: false
    remoteVirtualNetwork: {
      id: vnetSpoke.id
    }
  }
}

Is there a way for me to define that this peering has to be made in a different Resource Group?
I look forward to your ideas for this!

[brwilkinson]

You will need to generate the Peering in both directions.

Here is a sample:

https://github.com/brwilkinson/AzureDeploymentFramework/blob/60f2a6721034bacc441ad42a6c4701afaffe99f4/ADF/bicep/VNET.bicep#L133

Since you want to run the reverse Peering from the Hub, you can do that by using the Module with the scope set to the other resource group.

[Parlax]

Hey brwilkinson,

This worked like a charm!
I will 100% be using the documentation you've written on ADF. Very interesting stuff!