Azure Subscriptions and vNETs

%3CLINGO-SUB%20id%3D%22lingo-sub-160508%22%20slang%3D%22en-US%22%3EAzure%20Subscriptions%20and%20vNETs%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-160508%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Want%20to%20clarify%20the%20following%20statement%20from%20the%20article%20EXpressRoute%20FAQs%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAre%20virtual%20networks%20connected%20to%20the%20same%20circuit%20isolated%20from%20each%20other%3F%20No.%20From%20a%20routing%20perspective%2C%20all%20virtual%20networks%20linked%20to%20the%20same%20ExpressRoute%20circuit%20are%20part%20of%20the%20same%20routing%20domain%20and%20are%20not%20isolated%20from%20each%20other.%20If%20you%20need%20route%20isolation%2C%20you%20need%20to%20create%20a%20separate%20ExpressRoute%20circuit.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAnd%20from%26nbsp%3B%3CSPAN%3EAzure%20Onboarding%20Guide%20for%20IT%20Organizations%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20multiple%20virtual%20networks%20are%20to%20share%20a%20single%20enterprise%20ExpressRoute%20connection%2C%20essentially%20there%20is%20no%20network%20isolation%20between%20those%20networks.%20In%20this%20case%2C%20any%20separation%20the%20subscription%20design%20may%20try%20to%20define%20is%20eliminated%20and%20must%20be%20achieved%20through%20subnet%20layer%20Network%20Security%20Groups%20(NSGs).%20When%20the%20virtual%20networks%20are%20attached%20to%20the%20same%20ExpressRoute%20circuit%2C%20they%20are%20essentially%20a%20single%20routing%20domain.%20A%20subscription%20hosting%20only%20PaaS%20services%20could%20have%20no%20virtual%20network%20at%20all%2C%20and%20the%20design%20limitations%20discussed%20above%20would%20not%20apply.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EDoes%20that%20mean%2C%20if%20we%20connect%20multiple%20vNETs%20(even%20from%20different%20subscriptions)%20using%20single%20ExpressRoute%20connection%2C%20there's%20no%20network%20level%20isolation%20as%20we%20think%20of%20by%20having%20setup%20multiple%20subscriptions.%20If%20we%20want%20to%20enforce%20this%20isolation%2C%20we%20need%20to%20implement%20Network%20Security%20Groups%20Thanks%20Taranjeet%20Singh%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-160508%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ENetworking%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
New Contributor

Hi Want to clarify the following statement from the article EXpressRoute FAQs

 

Are virtual networks connected to the same circuit isolated from each other? No. From a routing perspective, all virtual networks linked to the same ExpressRoute circuit are part of the same routing domain and are not isolated from each other. If you need route isolation, you need to create a separate ExpressRoute circuit.

 

And from Azure Onboarding Guide for IT Organizations

 

If multiple virtual networks are to share a single enterprise ExpressRoute connection, essentially there is no network isolation between those networks. In this case, any separation the subscription design may try to define is eliminated and must be achieved through subnet layer Network Security Groups (NSGs). When the virtual networks are attached to the same ExpressRoute circuit, they are essentially a single routing domain. A subscription hosting only PaaS services could have no virtual network at all, and the design limitations discussed above would not apply.

 

Does that mean, if we connect multiple vNETs (even from different subscriptions) using single ExpressRoute connection, there's no network level isolation as we think of by having setup multiple subscriptions. If we want to enforce this isolation, we need to implement Network Security Groups Thanks Taranjeet Singh

0 Replies