What is Private Endpoint in Azure? | Intro to Private Endpoints

In this video I cover just what Private Endpoint is in Azure. And how they differ (or not) from Service Endpoint, Private Link and the Private Link Service
Docs page for Private Link: docs.microsoft.com/en-us/azur...
Docs page for Private Endpoint: docs.microsoft.com/en-us/azur...
Docs page for Private Link service: docs.microsoft.com/en-us/azur...
Docs page for Service Endpoints: docs.microsoft.com/en-us/azur...
Docs page for Private Resolver: docs.microsoft.com/en-us/azur...
Limitations of Private Endpoint: docs.microsoft.com/en-us/azur...
Socials:
Ask me stuff on Twitter: / pettertech
Catch me live on Twitch: / pettertech
Check out my awful code at Github: github.com/PetterTech
Follow me on LinkedIn: / pettertech
I also have merch: merch.streamelements.com/nere...
#Azure #AzurePrivateEndpoint
azure functions vnet integration private endpoints azure private endpoints private endpoints in azure private endpoints for azure functions

[@MusicGameFinatic999]

Thanks for the video! Clear and helpful.

[@PetterTech]

Thanks for the feedback, appreciate it! 👍

[@doroteyaagayna5714]

Very understandable explanation. Keep up the good work!

[@PetterTech]

Thank you! Very much appreciated ❤️

[@darkpiv]

So clear and precise. Thanks a lot for your work

[@PetterTech]

Thank you ;)

[@mortencarlsson2719]

Great work! Just what I needed!

[@PetterTech]

Thank you, glad you liked it 👍

[@masoudkooranloo908]

Thanks very useful and gripping!

[@pauldoherty6069]

Nice one, thanks for the explainer.

[@PetterTech]

My pleasure!

[@ericgray8526]

Thank you for this! The graphics and your straight forward explanation helped me to finally wrap my head around this for the 104. Subbed, keep up the good work!

[@PetterTech]

Thanks! And good luck to you on the 104 👍

[@oliversmith6348]

@@PetterTech So true, you defined it so clearly that it's hard to forget the concept now.

[@noname-xt4vt]

Thanks for the explanation.

[@PetterTech]

You're welcome! Thanks for watching 👍

[@DonReality]

Thank you for explaining this, so it's not quite like a VPN.
Also, I'm curious what mapping tool do you use to create those diagrams? I'm using packet tracer but it lacks the Cloud icons. Help appreciated.

[@PetterTech]

Not quite no :)
I use Lucidchart for my diagrams. Awesome tool and free too if you can live with the limitations of the free tier 👍

[@chavvagayathri3219]

Great explanation

[@PetterTech]

Thank you! Glad you liked it:)

[@wrongworld]

Would you use this service if you wanted to access a local drive on the virtual machine? I'm trying to make a local scanned folder accessible to users after logging in to the VM.

[@PetterTech]

If you're talking about a single vm where multiple users will log on and you want them all to have access to a local drive, then no.
A scenario where it might be useful is if you utilize Azure Files to store the scanned folder instead. In that case you would use Private Endpoint in conjunction with Azure Files.

[@IncorrectTarget.]

Thank you Sir!

[@PetterTech]

Thank you for watching!

[@SenthilkumarSV]

Great video with awesome explainations. So how this is going to be workout in the Hub & Spoke Architecture with Site-to-site connectviity please? What is the best practices for Site-to-site, Hub & Spoke Vnets, Private endpoint and private DNS scenario as a whole? I mean the placements of Private endpoints, Private DNS, Vnet-links in the whole situation.

[@PetterTech]

So in a hub & spoke architecture you would setup the site-to-site in the hub vNet and all the spoke vNets would need to traverse the hub in order to reach whatever your site-to-site connection connects to.
You can have your private endpoints in each of the spokes, but they should integrate with private DNS zones linked to the hub vNet. Then you would also need a DNS resolver in the hub, either VM based or use the private resolver service. Services in the spokes or on the other side of your site-to-site would then need to use conditional forwarding of DNS to the DNS resolver placed in your hub in order to resolve the names of your private endpoints.
Hope that answers your question :)

[@SenthilkumarSV]

​@@PetterTech Indeed, your response helps. I was on the same page too. Thanks for your quick response.

[@mrwaeta1]

Thank you for the clear explanation , you got yourself a new subscriber from Botswana

[@PetterTech]

Awesome, thank you!

[@SarmadJari]

very nice video, but when PaaS services communicate or having a service/app deployed in Azure communicate with an Azure PaaS service, the traffic does not flow through the internet, it flowes within Azure Network (Azure designed to keep the traffic as much as possible within it`s backbone for security and performance), the example of the Visrtual Disktop and the storage accounts is a bit misleading :)

[@PetterTech]

Well, yes. I do simplify it a bit and you are correct that the traffic will not leave Microsoft's backbone if not necessary. But how do we define when "the internet" starts? Is it when the traffic leaves your edge or when it leaves your providers edge? If you browse a website hosted in someone else's Azure environment from your AVD for example, or you not on the internet? Because the same would apply to the traffic there.

[@user-vj2tp3qv6e]

azure private endpoint is not working with azure cosmos mongo correctly. it is not working as with drivate DNS as with custom because of rs names, tls verification... omg just wasting time

[@PetterTech]

Have you tried using the "normal" url for your cosmos instance instead of the one for privatelink? It should do the redirect and not fail on ssl

[@user-vj2tp3qv6e]

@@PetterTech I even made local record in /etc/hosts how host mentioned in connection string and point it to Private Endpoint IPs. Only one conclusion - Cosmos Mongo can not work via Private Endpoint

[@jano.5485]

Big shocker - a website that should only be accessed internally can be hosted internally 😂

[@PetterTech]

ikr!? 😅

[@zxcv4695152526]

awesome👍