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
4 ай бұрын
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.
@mrwaeta1
Жыл бұрын
Thank you for the clear explanation , you got yourself a new subscriber from Botswana
@PetterTech
Жыл бұрын
Awesome, thank you!
@jano.5485
4 ай бұрын
Big shocker - a website that should only be accessed internally can be hosted internally 😂
@PetterTech
4 ай бұрын
ikr!? 😅
@cloudwork-y4c
4 ай бұрын
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
4 ай бұрын
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
@cloudwork-y4c
4 ай бұрын
@@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
@SenthilkumarSV
11 ай бұрын
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
11 ай бұрын
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
11 ай бұрын
@@PetterTech Indeed, your response helps. I was on the same page too. Thanks for your quick response.
@virabadrasana
22 күн бұрын
@@PetterTech Services in the spokes would need to employ conditional forwarding? I understand that only a DNS server can do conditional forwarding, not a service. Please could you explain what you mean, as I do not have a DNS service available in the spoke. Many Thanks!
@PetterTech
20 күн бұрын
Re-reading my comment I see that it could have been clearer. For the spokes you would change the DNS server property of the vNet to point to whatever type of DNS resolver you have in the hub.
@sherwinaka007
Ай бұрын
great explaining on your end brother
@PetterTech
Ай бұрын
Much appreciated 👍
@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.
@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 👍
@MusicGameFinatic999
2 жыл бұрын
Thanks for the video! Clear and helpful.
@PetterTech
2 жыл бұрын
Thanks for the feedback, appreciate it! 👍
@masoudkooranloo908
4 ай бұрын
Thanks very useful and gripping!
@chavvagayathri3219
6 ай бұрын
Great explanation
@PetterTech
6 ай бұрын
Thank you! Glad you liked it:)
@doroteyaagayna5714
Жыл бұрын
Very understandable explanation. Keep up the good work!
@PetterTech
Жыл бұрын
Thank you! Very much appreciated ❤️
@zxcv4695152526
Жыл бұрын
awesome👍
@danforo94
Жыл бұрын
So clear and precise. Thanks a lot for your work
@PetterTech
Жыл бұрын
Thank you ;)
@noname-xt4vt
5 ай бұрын
Thanks for the explanation.
@PetterTech
5 ай бұрын
You're welcome! Thanks for watching 👍
@pauldoherty6069
Жыл бұрын
Nice one, thanks for the explainer.
@PetterTech
Жыл бұрын
My pleasure!
@mortencarlsson2719
8 ай бұрын
Great work! Just what I needed!
@PetterTech
8 ай бұрын
Thank you, glad you liked it 👍
@IncorrectTarget.
11 ай бұрын
Thank you Sir!
@PetterTech
11 ай бұрын
Thank you for watching!
@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.
Пікірлер: 41