We have a VNET in Subscription A that has global peering to a Virtual HUB in Subscription B. We want to understand from the context of subscription A which HUB in subscription B is connected. Is there a way to understand which subscription ID, resource group name, and hub name the peering belongs to? The data from the peering list API contains values different from those of the real HUB data. in the peering list API we receive a subscription id which do not correspond to any subscription we have in our organization - see below. thanks.

@Rina Frusman , Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well. I understand that you would like to know why there is a different subscription displayed for the vHUB VNET Connection. Note that the vWAN vHub is deployed into a managed Subscription owned by Microsoft. I understand, this should be visible to the customers during control plane operations (such as GET which you seem to be doing). I shall pass on this feedback to the concerned Product Team. Kindly let us know if this helps or you need further assistance on this issue. Thanks, Kapil Please don’t forget to close the thread by clicking " Accept the answer " wherever the information provided helps you, as this can be beneficial to other community members.

Global Peering between Virtual Network to Virtual Hub

Accepted answer

KapilAnanth-MSFT 48,081 Reputation points Microsoft Employee

2024-09-26T10:17:49.27+00:00

@Rina Frusman ,

Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.

I understand that you would like to know why there is a different subscription displayed for the vHUB VNET Connection.

Note that the vWAN vHub is deployed into a managed Subscription owned by Microsoft.

I understand, this should be visible to the customers during control plane operations (such as GET which you seem to be doing).

I shall pass on this feedback to the concerned Product Team.

Kindly let us know if this helps or you need further assistance on this issue.

Thanks,

Kapil

Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members.
Please sign in to rate this answer.

1 person found this answer helpful.
Rina Frusman 20 Reputation points

2024-09-26T13:00:19.74+00:00

Thanks for the prompt reply! I be happy to get an update on this matter if possible.

KapilAnanth-MSFT 48,081 Reputation points Microsoft Employee

2024-09-30T15:01:34.75+00:00

Sure @Rina Frusman ,

Should I receive an update internally, I shall update this thread as well.

Cheers,

Kapil

KapilAnanth-MSFT 48,081 Reputation points Microsoft Employee

2024-10-01T07:32:21.0633333+00:00

@Rina Frusman ,

I just got an update from the Product Team that this is the current behavior.

Further, they also confirmed they will consider documenting this and look at whether or not we want to mask this in the future.

Currently, the recommended approach is to use Hub Virtual Network Connections - Get - REST API (Azure Virtual WAN) | Microsoft Learn from the vWAN side and parse the connection body for the "remoteVirtualNetwork" parameter.

Additionally, if you feel this should be implemented and needs more traction, I recommend you raise a feedback item in Azure Feedback Hub.

All the feedback shared in these forums are monitored and reviewed by the Microsoft engineering teams responsible for building Azure

Thanks,

Kapil

Please Accept an answer if correct.

Original posters help the community find answers faster by identifying the correct answer.

Rina Frusman 20 Reputation points

2024-10-20T09:45:39.6833333+00:00

Hi, Thank you very much for this answer.

can a VNET be "globally" peered to 2 different VWANs at the same time.

can a VENT be globally peered with 2 peering configuration to the same VWAN (for example to route 2 different subnets to 2 different WANs/Route tables? i am asking to better understand the architecture and see if the solution provided via the API is beneficial for our case..

another question, will you consider to add the actual customer subscription information from the VNET level in such cases? even as part of a new/other field in the API?

KapilAnanth-MSFT 48,081 Reputation points Microsoft Employee

2024-10-21T12:06:04.6366667+00:00

@Rina Frusman , You are welcome and we are glad to assist :)

To address your query #1 and #2,

A virtual network can only be connected to one virtual hub at a time

See : Connect a virtual network to a Virtual WAN hub

It does not matter if the vHUBs are in the same vWAN, or different vWAN - You will not be able to peer a single VNET to 2 or more vWANs(vHubs).

Wrt, "will you consider to add the actual customer subscription information from the VNET level in such cases? even as part of a new/other field in the API?"

This feedback has been passed to the Product team

They are currently reviewing this - please follow the Azure Updates to stay up to date with official product features and changes

Thanks,

Kapil

Please Accept an answer if correct.

Original posters help the community find answers faster by identifying the correct answer.

Rina Frusman 20 Reputation points

2024-10-22T10:27:24.1066667+00:00

Thank you very much, this was helpful!

KapilAnanth-MSFT 48,081 Reputation points Microsoft Employee

2024-10-22T10:30:25.2033333+00:00

@Rina Frusman , Glad we could be of assistance.

Thanks for your continued contribution on Q&A and appreciate much for taking the time to share your feedback

Cheers,

Kapil
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Global Peering between Virtual Network to Virtual Hub

1 additional answer

Your answer