💼 Join our free class to discover our exclusive three-step framework designed to help you achieve certification and secure high-paying jobs in Azure and DevOps: bit.ly/3XchMEA
@kirangem Жыл бұрын
Very clear explanation, though i have no prior networking knowledge I was able to understand the entire explanation. Thanks alot!
@K21Academy Жыл бұрын
Thank you. yours words inspire us to do more and serve you with the best.
@shubhamshukla405228 күн бұрын
Thankyou soo much for the detailed explanation. This session has really cleared my doubts and helped me achieving the deployments. Once again thanks a lot sir.
@K21Academy16 күн бұрын
You are most welcome
@FXK23 Жыл бұрын
Great content, we're about to migrate to this architecture so many thanks for explaining hub-spoke arch. !
@K21Academy Жыл бұрын
Thanks, keep watching!
@theconfusedchannel636515 күн бұрын
Nice explanation. I do agree that it's explained very clearly. Could you please add traffic going from spoke1 to spoke2 via Firewall?
@K21Academy13 күн бұрын
Thank you.. If you want to check the connectivity from spoke 1 to spoke 2 you can ping spoke 1 to spoke 2 or vice versa.
@sambhavpandey2 жыл бұрын
Very nicely explained the concept of Hub and Spoke, thank you!
@K21Academy2 жыл бұрын
Thanks, keep watching!
@niranjanrath7899 ай бұрын
Very nicely explained the concept of Hub and Spoke
@K21Academy8 ай бұрын
Glad you liked it! 😊 Please do let us know what videos you'll like to see next?
@dukeyu87 Жыл бұрын
I remember in my previous organization, not all subnets have route table associated. And the traffic still goes to the firewall. How can that be achieved?
@K21Academy Жыл бұрын
In order for traffic to go through the firewall, even if not all subnets have associated route tables, you can configure the default route on the firewall to forward all traffic to the appropriate destination. By setting up the default route, any traffic that does not have a specific route defined will be sent to the firewall for further processing and inspection. This ensures that all network traffic passes through the firewall, regardless of the subnet's individual route table configuration. Hope this helps. Regards Team K21Academy
@gotamp24 Жыл бұрын
man you're awesome! Thank you for uploading this.
@K21Academy Жыл бұрын
Hey thanks! Do let us know what would you love to watch next?
@FernandoMartinez-fl4cm4 ай бұрын
Amazing material thanks so much for sharing
@K21Academy4 ай бұрын
Thank you for your kind words, we appreciate your support!
@bangtanboys71715 ай бұрын
very beautiful explanation ,seeing the architecture might terrifying for begineers or fresher after your brief anyone can accomplish!
@K21Academy5 ай бұрын
Glad you liked it!
@Shravan_Reddy10 ай бұрын
Good explanation. Could you also show how to use firewall to intercept traffic for malicious content in a scenario where there is a traffic manager and app services as its backend pools?
@K21Academy8 ай бұрын
To give you a short overview In a scenario where there is a Traffic Manager and App Services as its backend pools, Azure Firewall can be used to intercept traffic for malicious content by deploying it in the same virtual network as the App Services. This will allow Azure Firewall to inspect all traffic going to and from the App Services, and block any traffic that is found to be malicious. We cover this practical implementation during our sessions. To know more? Join our FREE Class: bit.ly/4a9v9cq
@Shravan_Reddy8 ай бұрын
Thanks @@K21Academy Does this mean, in this specific scenario a VNET is mandatory for App service setup?
@surbhisharma78532 жыл бұрын
Great Explanation👍🏻
@K21Academy2 жыл бұрын
Thank you, keep watching!
@yaaweehoo Жыл бұрын
Indeed!
@anrainmoore754 Жыл бұрын
This explanation was perfect. Thank you.
@K21Academy Жыл бұрын
Thanks, keep watching!
@user-ur9xl3xs7w5 ай бұрын
thanks for sharing real scenario ,,very much clear explanation
@K21Academy5 ай бұрын
Glad it was helpful!
@muralidharanr33928 ай бұрын
I see, you created two VM's with public IP's for each vnet. I think one VM with public IP is enough.. You can take any one work(spoke) machine using RDP from public IP machine. from that work(spoke) machine the second work machine can be taken for RDP.. just cost saving for public IP.. Another options is to enable bastion- can be in production environment (mid to big size).. Please comment on your views..
@K21Academy6 ай бұрын
We are using the hub as a firewall. This Firewall is common for 2 machines that are acting as 2 work machines in different machines. So if we are connecting one with public IP to other with private, then only one will be working at a time either. then there is no use of creating 2 separate work machines.
@ris9hi Жыл бұрын
Very nice content
@K21Academy Жыл бұрын
Hey! Thanks for the feedback. Do let us know what videos you'd like to see next?
@niranjannt637 Жыл бұрын
Great walkthrough!!
@K21Academy Жыл бұрын
Thanks, keep watching!
@ivangandham9105 Жыл бұрын
Awesome..Explanation.Really liked it.Thank you so much for these kind of stuff.
@K21Academy Жыл бұрын
Thanks, keep watching!
@hammadrana22799 ай бұрын
Great 👍
@K21Academy8 ай бұрын
Thank you! Cheers!
@Snehdeep1000 Жыл бұрын
Thanks for your knowledge
@K21Academy Жыл бұрын
Thanks, keep watching!
@K21Academy Жыл бұрын
Thanks, keep watching!
@aarif6447 Жыл бұрын
Very crisp and informative.
@K21Academy Жыл бұрын
Thanks, keep watching!
@K21Academy Жыл бұрын
Thanks, keep watching!
@rizwanmohammad07 Жыл бұрын
Do we require NSG rule allowed for internet to achieve this
@K21Academy Жыл бұрын
No, you do not need to configure Network Security Group (NSG) rules to allow internet access. When VM-work does not have a public IP and the traffic is passing through Azure Firewall, it means that the access to VM-work is restricted to internal network traffic only. In this setup, VM-work is not directly accessible from the internet, and its inbound traffic is controlled by the Azure Firewall. So if you setup NSG rules then also it will not show any response to it. Hope this helps! Regards Team K21Academy
@satviktripathi93482 жыл бұрын
May i know how internet was working prior to attaching it with firewall vnet ? I think we need nat gateway in vnet for the same
@Cloudgyan872 жыл бұрын
internet is allowed by default on Azure Vms while creating
@dharmendrachauhan5020 Жыл бұрын
Awesome
@K21Academy Жыл бұрын
Thanks, keep watching.
@nabendubhattacharya47382 жыл бұрын
very well explained
@K21Academy2 жыл бұрын
Thanks, keep watching!
@The24hrStruggle2 жыл бұрын
hmm don't understand why you would route traffic from a different geo-region to another geo-region fw? you would said the traffic over the vNET peering to the speak to the other regions surely?
@praveenkumarp13572 жыл бұрын
He was Deployed the HUB ( Firewall ) Subnet on a different region and all other two Spoke subnets was deployed on other two different regions. Inorder to communicate the Spoke Subnets to Firewall subnets we have to enable the Regional VNET Peering , then only Spoke Subnets on Different regions can communicate with Firewall Subnets. In Azure , Azure Firewall Deployment Under each VNETS is not a logical solution as it is bit Costly. That is the reason why he was created a Single firewall under firewall Subnet on Different region and routed all the Spoke Subnet Traffic towards to Firewall Subnet and attached the Spoke subnets on Routing tables. Which means any traffic that is originating from the Spokes subnet to any destinations will be routed to Azure Firewall and based on the Firewall rules ( Network/Application rules) the services will be allow/deny by firewall.
@ismashkhy Жыл бұрын
@@praveenkumarp1357 Azure VPN gateway is the major Trap, when you start creating your network and depending to it you need the VPN gateway as the core, and you realize later on the cost it incur that your whole mesh network is dependent to it you cannot just turn it off. that is why others are switching to SDNetworking, trashing the azure vpn gateway out of the scene. I maybe wrong about this, I would be happy someone could shed some light into this.
@sandeepdhuri8 ай бұрын
dose azure firewall support ikev2 VPN (on premise to Azure ) or need VPN gateway
@K21Academy8 ай бұрын
Yes, Azure Firewall supports IKEv2 VPN for on-premises to Azure VPN connections. However, it is important to note that the Azure Firewall VPN Gateway is still required to create the connection.
@sandeepdhuri8 ай бұрын
@@K21Academy Thank you
@lucifermusic30102 жыл бұрын
Valuable content 👏👏
@K21Academy2 жыл бұрын
Thank you, keep watching!
@romjohnawacay6390 Жыл бұрын
Great thank you ❤
@K21Academy Жыл бұрын
Hey, thanks to you too! Do let us know what videos you'd like to watch next?
@romjohnawacay6390 Жыл бұрын
@@K21Academy im looking for azure application gateway with multiple listners and backend pool