Think of a Service Endpoint as a way to secure your connection to Azure services while still using the public internet. It lets your virtual network “reach out” to services like Azure Storage or SQL Database, but it does so securely over Azure’s network, without needing a public IP. It’s simple and works well if you don’t mind that the traffic is still technically over the internet. Now, a Private Endpoint is a bit different. It’s like giving your Azure service its own private room inside your virtual network. With a Private Endpoint, your traffic never leaves your network-it’s totally isolated. This is perfect if you want to keep everything behind closed doors, like for sensitive data or when you need to meet strict security requirements.
thank you sir, really like the fast pace
Enjoy
Keep up the good work! I like the way you combine demo and explanation.
Thank you!
Great explanation, thank you 😊
Excellent video.
great video mikey
❤🎉 good 👍 explained with diagram 🎉🎉🎉
Think of a Service Endpoint as a way to secure your connection to Azure services while still using the public internet. It lets your virtual network “reach out” to services like Azure Storage or SQL Database, but it does so securely over Azure’s network, without needing a public IP. It’s simple and works well if you don’t mind that the traffic is still technically over the internet.
Now, a Private Endpoint is a bit different. It’s like giving your Azure service its own private room inside your virtual network. With a Private Endpoint, your traffic never leaves your network-it’s totally isolated. This is perfect if you want to keep everything behind closed doors, like for sensitive data or when you need to meet strict security requirements.
@@mwcloud wow 😲 very clear answer, thx 🙏
@@somjadek no problem
Great stuff, thank you
no problem
Great!