Access to the delegated container subnet from the rest of the network

%3CLINGO-SUB%20id%3D%22lingo-sub-2221609%22%20slang%3D%22en-US%22%3EAccess%20to%20the%20delegated%20container%20subnet%20from%20the%20rest%20of%20the%20network%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2221609%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20an%20on-premise%20network%3A%20ONPREM-VLAN%26nbsp%3B%20which%20is%20connected%20to%20an%20Azure%20VLAN%3A%20AZUREVLAN1%20using%20Site%20to%20Site%20VPN%20connection.%20This%20AZUREVLAN1%20is%20in%20subscription-1.%20We%20have%20another%20subscription%3A%20subscription-2%20which%20has%20two%20more%20VLANs%3A%20AZUREVLAN2%20and%20AZUREVLAN3.%20AZUREVLAN2%20is%20one%20Azure%20region%20(same%20as%20AZUREVLAN1%20i.e.%20Australia%20Southeast)%20and%20AZUREVLAN3%20is%20in%20another%20Azure%20region%20(i.e.%20In%20Australia%20East).%20We%20have%20enabled%20Vnet%20peering%20between%20all%20the%20three%20VLANs.%20We%20have%20also%20established%20routing%20from%20our%20on-premise%20network%3A%20ONPREM-VLAN%20to%20all%20the%20three%20Azure%20VLANs.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%2C%20when%20we%20created%20a%20delegated%20container%20subnet%20in%20AZUREVLAN3%20it%20is%20only%20accessible%20from%20other%20subnets%20within%20AZUREVLAN3.%20it%20is%20not%20accessible%20from%20any%20other%20VLANs%20(AZUREVLAN2%2C%20AZUREVLAN1%20and%20ONPREM-VLAN)%20in%20the%20network.%20Here%20is%20the%20screenshot%20of%20that%20delegated%20container%20subnet%3A%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Screenshot%202021-03-19%20133835.png%22%20style%3D%22width%3A%20527px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F265416i9FF9BDB3F4C73BB2%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22Screenshot%202021-03-19%20133835.png%22%20alt%3D%22Screenshot%202021-03-19%20133835.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EIs%20there%20a%20way%20i%20can%20enable%20routing%20from%20the%20rest%20of%20the%20network%20to%20this%20delegated%20subnet%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2221609%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EVirtual%20Network%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Contributor

Hi All,

 

We have an on-premise network: ONPREM-VLAN  which is connected to an Azure VLAN: AZUREVLAN1 using Site to Site VPN connection. This AZUREVLAN1 is in subscription-1. We have another subscription: subscription-2 which has two more VLANs: AZUREVLAN2 and AZUREVLAN3. AZUREVLAN2 is one Azure region (same as AZUREVLAN1 i.e. Australia Southeast) and AZUREVLAN3 is in another Azure region (i.e. In Australia East). We have enabled Vnet peering between all the three VLANs. We have also established routing from our on-premise network: ONPREM-VLAN to all the three Azure VLANs.

 

However, when we created a delegated container subnet in AZUREVLAN3 it is only accessible from other subnets within AZUREVLAN3. it is not accessible from any other VLANs (AZUREVLAN2, AZUREVLAN1 and ONPREM-VLAN) in the network. Here is the screenshot of that delegated container subnet:

Screenshot 2021-03-19 133835.png

Is there a way i can enable routing from the rest of the network to this delegated subnet?

 

0 Replies