First minute is actually wrong. Azure subnet route tables are automatically populated with systems routes, one of which is "Internet" "If you don't override Azure's default routes, Azure routes traffic for any address not specified by an address range within a virtual network to the Internet. There's one exception to this routing. If the destination address is for one of Azure's services, Azure routes the traffic directly to the service over Azure's backbone network" So traffic to internet destine for azure owned prefixes never leaves the az backbone. The service endpoints introduced an "optimized" route to reach azure services without having it traverse the traditional egress route to the internet. Ultimately this was introduced because people couldn't get their head around the fact that the traffic just didn't leave azure.
I've had this doubt for so long with me hahaah. Amazing explanation man, thank you very much. Just to summarize the difference between the private endpoint and private link, we should use private link when private endpoints aren't available, right?
Hi Shai! Thanks for this Vid. Btw i have my questions regarding the usage of service EP and Private. you've mentioned that if Paas are used in public we should use Service endpoint solely? and if Paas service is used within Azure we should use private link? these two points should be followed at all times?
Hi, I believe you are mixing up private links and private endpoints. As per Microsoft documentation, the private link used for connecting with azure provided PaaS and the private endpoints is used for connecting two network privately or azure provided PaaS powered by azure private link. But you are saying the opposite
Even with no demo, this was a very concise and clear explanation of these topics. Thanks!
First minute is actually wrong. Azure subnet route tables are automatically populated with systems routes, one of which is "Internet"
"If you don't override Azure's default routes, Azure routes traffic for any address not specified by an address range within a virtual network to the Internet. There's one exception to this routing. If the destination address is for one of Azure's services, Azure routes the traffic directly to the service over Azure's backbone network"
So traffic to internet destine for azure owned prefixes never leaves the az backbone. The service endpoints introduced an "optimized" route to reach azure services without having it traverse the traditional egress route to the internet. Ultimately this was introduced because people couldn't get their head around the fact that the traffic just didn't leave azure.
Thanks, man, I was highly confused between these. Thanks for the explanation.
Best on point explanation so far.
I've had this doubt for so long with me hahaah. Amazing explanation man, thank you very much.
Just to summarize the difference between the private endpoint and private link, we should use private link when private endpoints aren't available, right?
straight to the point... U deserve my like..👍
Hi Shai! Thanks for this Vid. Btw i have my questions regarding the usage of service EP and Private. you've mentioned that if Paas are used in public we should use Service endpoint solely? and if Paas service is used within Azure we should use private link? these two points should be followed at all times?
Hi, I believe you are mixing up private links and private endpoints. As per Microsoft documentation, the private link used for connecting with azure provided PaaS and the private endpoints is used for connecting two network privately or azure provided PaaS powered by azure private link. But you are saying the opposite
Good info- thanks!
Thanks mate
Thank you 👍
thx good video
Thank you 😊