Microsoft Azure

Using Azure PowerShell for easier Microsoft Azure VNet peering between resource groups


I was recently working on a setup where I had 2 Azure resource groups and could not get the virtual networks (VNets) to peer between them. I had Azure AD Domain Services in one resource group and a bunch of session host servers in another resource group. The portal kept throwing this error message when attempting to create a peering:

Failed to add virtual network peering
Failed to add virtual network peering ‘name of peering’. Error: error

Not very helpful right? If you see a nondescript error message like this while attempting to peer you can get around the issue using Azure PowerShell. PowerShell also gives you more descriptive error messages which can be clues to help you troubleshoot what’s wrong.

1. First make sure to have Azure PowerShell installed locally or on a jump box. It is a set of cmdlets for PowerShell that will help you manage Azure ARM resources. You can read more on it here:
Windows 10 comes with PowerShell already so just open up an elevated PowerShell window and type:

Install-Module AzureRM -AllowClobber

It will tell you:

You are installing the modules from an untrusted repository. If you trust this repository, change
its InstallationPolicy value by running the Set-PSRepository cmdlet.
Are you sure you want to install the modules from 'PSGallery'?

Just press “A” for Yes to All. Now load the AzureRM module for Resource Manager remote management by typing in:

Import-Module AzureRM

Now you can type in:

Get-Module AzureRM -list | Select-Object Name,Version,Path

and it will output the Azure PowerShell version installed like this:

I also like to manage Azure AD so I usually also do:
Install-Module AzureAD
Import-Module AzureAD

2. Now log into your Azure subscription from PowerShell. Type:


and a login box will popup. Just follow the prompts. Then PowerShell will show you the account you are logged in with:

3. Now for the VNet peering. You need to create 2 variables to store your VNet info in. My vnet2 is where my Azure ADDS VNet is in this example. My resource group is also specified here at the end:

$vnet2 = Get-AzureRmVirtualNetwork -Name Azure-AD-DS-vnet -ResourceGroupName RG_Azure_AD_Domain_Services

now do the same for where you other VNet is. This is where my session hosts are in this example:
$vnet1 = Get-AzureRmVirtualNetwork -Name OtherRG-tenant-01-vnet -ResourceGroupName OtherRG-tenant-01

and it should look something like this as you type them in:

4. Now type the following to create your first peer. Pro tip, just press tab after the cmdlet and it will automatically add each switch as you go, no need to even type the first letter of the switch:

Add-AzureRmVirtualNetworkPeering -Name AD-to-OtherRG -VirtualNetwork $vnet2 -RemoteVirtualNetworkId $

Then do it again but the other way so you have 2 way communication:

Add-AzureRmVirtualNetworkPeering -Name OtherRG-to-AD -VirtualNetwork $vnet1 -RemoteVirtualNetworkId $

and you’re done! It should look something like this as you create each peer:

and your Azure Portal should say it’s Connected under Peering Status:

Hope this helps! Please leave a comment below if you have any questions.

About Jason Samuel

Jason Samuel lives in Houston, TX with a primary focus on strategic advisory and architecture of end-user computing, security, enterprise mobility, virtualization, and cloud technologies from Citrix, Microsoft, & VMware. He also has an extensive background in web architecture and networking over his 20+ year career in IT. He is an Author, Speaker, and Local User Group Community Leader. He is certified in several technologies and is 1 of 63 people globally that is a recipient of the prestigious Citrix Technology Professional (CTP) award. He is 1 of 42 people in the world that has been awarded as a VMware EUC Champion and VMware vExpert. He is a featured author on DABCC which provides the latest IT Community News on Cloud, Data Center, Desktop, Mobility, Security, Storage, & Virtualization. In his spare time Jason enjoys writing how-to articles and evangelizing the technologies he works with. Disclaimer: The content and opinions expressed in articles and posts are his own and are by no means associated with his employer.

Recommended for you

Leave a Reply

Your email address will not be published. Required fields are marked *