Thank you so much Adam! this is yet another best content from you. I wanted to understand that the first case where we are proposing using the High Resiliency ER (basically 2 circuits in different location) is that same as the Metro SKU (or the Metro SKU is more on the Primary and Seconday connections distributed across 2 cities and for now since its in preview its only in West Europe, South Asia and Switzerland North)? The reason I ask because with 2 different circuit i.e. high resiliency customer will have to pay for 2 circuits and if they use Metro SKU then its just distributing primary and secondary to 2 cities? If my understanding on Metro SKU is correct?
Another great video Adam. Think I've watched them all - keep them coming. I had forgotten about the ERGW AZ SKU! So that'll need to be looked at ASAP and that migration tool looks the ticket. Many thanks. In the industry, I struggled to find network engineers/architects whose skills go in depth into the CSP's space. So this library youve built up of videos, is a massive help.
Hey Adam. Love and follow your content religiously. Question, we are running in to a limitation in Azure. We would like to be able to geo-block/restrict TCP (non-http) traffic by country. We have deployed Azure Application Gateway with WAF v2 in front of the Azure firewall which takes care of the http geo-blocking scenario. But, unfortunately even with using the new preview feature of App Gateway by having the TCP load balancing capability, it still does not cater for inbound TCP traffic restriction. Would love to get your opinion on this. I just wish MS would enable Geo-Blocking capability at the FW level but would be keen to hear other possible solutions.
Hi Adam, thanks for the informative video as always. Quick question on the scenario with MSEE inter-region hairpin. From my understanding, in usual Vnet peering you cannot do a peering if the other vnet already has a gateway, right? Does it only apply for VPN gateway? or also for ExpressRoute Gateway (meaning each gateway has ER gateway), does Global peering affects this? (in a way that maybe it's possible in Global peering but not normal vnet peering) Thanks again!
@@AdamStuart1 thanks! that makes sense. So you can peer them for connectivity between 2 vnets traffics but not when it's hub-and-spoke where you want the spokes from each hubs to talk with each other.
Sorry to go off topic, but I remember that you did a video on routing backup traffic from on prem to Azure but bypassing the azure firewall, to avoid azure firewall costs for processing backup traffic. I can’t seem to find that video, has it been deleted or am I not searching properly? (found it!: ua-cam.com/video/QIT9E4D5lh8/v-deo.htmlsi=jv_bFBOafECzj6C9)
Thank you so much Adam! this is yet another best content from you.
I wanted to understand that the first case where we are proposing using the High Resiliency ER (basically 2 circuits in different location) is that same as the Metro SKU (or the Metro SKU is more on the Primary and Seconday connections distributed across 2 cities and for now since its in preview its only in West Europe, South Asia and Switzerland North)? The reason I ask because with 2 different circuit i.e. high resiliency customer will have to pay for 2 circuits and if they use Metro SKU then its just distributing primary and secondary to 2 cities? If my understanding on Metro SKU is correct?
Another great video Adam. Think I've watched them all - keep them coming.
I had forgotten about the ERGW AZ SKU! So that'll need to be looked at ASAP and that migration tool looks the ticket. Many thanks.
In the industry, I struggled to find network engineers/architects whose skills go in depth into the CSP's space. So this library youve built up of videos, is a massive help.
Nice one Adam.
Hey Adam. Love and follow your content religiously.
Question, we are running in to a limitation in Azure. We would like to be able to geo-block/restrict TCP (non-http) traffic by country.
We have deployed Azure Application Gateway with WAF v2 in front of the Azure firewall which takes care of the http geo-blocking scenario. But, unfortunately even with using the new preview feature of App Gateway by having the TCP load balancing capability, it still does not cater for inbound TCP traffic restriction.
Would love to get your opinion on this. I just wish MS would enable Geo-Blocking capability at the FW level but would be keen to hear other possible solutions.
Thanks Adam,
How are designers making these errors? Just having hard time imaging it. We are talking networking fundamentals.
because they don’t bother to read how a product works, limitations and features.
Hi Adam, thanks for the informative video as always.
Quick question on the scenario with MSEE inter-region hairpin. From my understanding, in usual Vnet peering you cannot do a peering if the other vnet already has a gateway, right? Does it only apply for VPN gateway? or also for ExpressRoute Gateway (meaning each gateway has ER gateway), does Global peering affects this? (in a way that maybe it's possible in Global peering but not normal vnet peering)
Thanks again!
You can peer VNets that have VNG/GW, but you cannot tick the boxes for using remote gateway, if you have a local GW.
@@AdamStuart1 thanks! that makes sense. So you can peer them for connectivity between 2 vnets traffics but not when it's hub-and-spoke where you want the spokes from each hubs to talk with each other.
Sorry to go off topic, but I remember that you did a video on routing backup traffic from on prem to Azure but bypassing the azure firewall, to avoid azure firewall costs for processing backup traffic. I can’t seem to find that video, has it been deleted or am I not searching properly? (found it!: ua-cam.com/video/QIT9E4D5lh8/v-deo.htmlsi=jv_bFBOafECzj6C9)
Yes, just be aware these designs (any design that uses custom routing) is currently not compatible with Routing Intent
@@AdamStuart1 ok, thanks for the heads up.