Is there a Difference how we do Global Vnet peering in Bicep

[say2merohit]

Is there a difference in how we do Global Vnet peering in Bicep I am not able to do a Global Vnet Peering
Subscriptions are different but tenant is same

[brwilkinson]

There is no difference between Global Peering and Peering within the same region.

They both share the same template and features:

• You Peer in both directions
• In order to facilitate the reverse peering, you use a Bicep Module to provide the scope of the partner SUB/RG in order to run the deployment.

[brwilkinson]

if your spoke is deployed via Bicep, then you create the resource in the Bicep file.

If your hub is deployed via a different team or via Portal Etc., then yes you simply reference it as 'existing'.

Then you need to ensure that you have whatever RBAC permission in order to deploy into the Hub resource group, in order to create the reverse peering.

[say2merohit]

These are two hubs we are trying to connect one is Canada and other in is south central ... access should not be the problem ...let me see based on your suggestion what can we do...

[brwilkinson]

https://github.com/brwilkinson/AzureDeploymentFramework/blob/dev/ADF/bicep/VNET.bicep

[say2merohit]

Last thing do we still deploy peering using new-azresourcegroup deployment how we are gonna know which subscription do I need to run it under ?

[brwilkinson]

https://github.com/brwilkinson/AzureDeploymentFramework/blob/07085f5333874b08f1ff38301a6a17f74030621f/ADF/bicep/VNET.bicep#L135

When you reference the existing VNET you set the scope that includes the Subscription and Resource Group.

Definitely check out the Learn Module for Bicep, they are really great. The number of modules is growing weekly...

Learning Path
https://docs.microsoft.com/en-us/learn/paths/bicep-deploy/

This concept is covered in this module:

https://docs.microsoft.com/en-us/learn/modules/child-extension-bicep-templates/6-work-with-existing-resources