We are trying to link VNets from multiple subscriptions across our existing expressroute, following the instructions in https://azure.microsoft.com/en-us/documentation/articles/expressroute-howto-linkvnet-classic/.
The VNets I want to link have been created in the new portal with resource manager. When I run this command (obviously with my servicekey and vnetname values)
New-AzureDedicatedCircuitLink–servicekey "&&&&&&&&&&&&&&&&&&&&&&&&&&"–VnetName'SalesVNET1'
I get BadRequest: The specified virtual network name 'MYNETWORKNAME' is not valid or could not be found.
The circuit owner has definitely created the Authorization (and I can see the Authorization if I do a get-azureauthorizeddeidcatedcircuit)
Do I need to do this a different way or use a different command for VNets created with resource manager in the portal??