Closed tom-stones closed 6 years ago
@MikhailTryakhov This looks like it could be an automapper issue, could you assign to the appropriate network folks
Yes, it was a mapping issue. Opened PR with fix: https://github.com/Azure/azure-powershell/pull/7585
PR has been merged, the fix will be available in the next release (November, 7th, I believe)
Description
Upgraded to AzureRm module 6.10.0 and AzureRm.Network module 6.9.0
I have a Vnet that is peered with another Vnet.
When I use Get-AzureRmVirtualNetworkPeering the returned object does not show the address range for the remote vnet.
If I use the -Verbose -Debug switches I can see the remote vnet address range in the underlying REST response.
Script/Steps for Reproduction