VPNs Don’t Actually Protect You

[@AzureAcademy]

🔥Try Twingate Today for FREE 🔥 👉 tinyurl.com/TryTwingate 👈

[@mosksky]

TY Dean as always! Just a thought though, with Microsoft Entra Private Access why do you even need VPN at all? Even bastion is not needed.

[@AzureAcademy]

Thanks for watching! Entra Private Access is on my list to learn about...but Twingate got to me first 😜 I haven't gotten the license to use Global Secure Access yet...but Stay Tuned! Is there anything specific you'd like to see in a video on Entra Private Access?

[@richardsilver3190]

This video is fun to watch and awesome work.

[@AzureAcademy]

Awesome, thanks!

[@pavangrandhi]

Thanks for the Video. This tool is somewhat similar to the open source tool "Coder" which doesn't have much of GUI in the client app, but only available as a CLI tool.

[@AzureAcademy]

Cool, never heard of Coder…there are so many solutions out there ☺️

[@varishwartripathi3885]

Nice information dean

[@AzureAcademy]

Thanks 👍

[@oliversellman1927]

solid!

[@AzureAcademy]

Thanks!

[@rangiz99]

How does this work where the local network ip matches the resource that twingate? Once you connect, is it locked in? Also can you share files over this twingate as well? I didn't see anything on their site for SMB shares

[@AzureAcademy]

In a single Azure virtual network only 1 device can have any single IP...so they can't share. But you could have 2 vnets with the same IPs...I am not sure if Twingate supports that scenario...but if it does...it would ONLY work because of the Twingate agent. yes you can share files over SMB...you would have to enable port 445 in Twingate...but ALSO understand that MOST internet providers BLOCK port 445, so it may not work for you anyway.

[@rangiz99]

@@AzureAcademy I was more worried about being in an Internet cafe hotel wifi and having the same ip address as your vnet subnet. But if twingate is running quic 445 would be encapsulated over 443 for the twingate appliance, no?

[@AzureAcademy]

you are correct...the appliance and the client communicate directly...my point was if you have 2 different vnets in Azure with the same IP Address range and you have 2 Twingate resources on IP 192.168.0.5 on port 445 then I am not sure Twingate could support that...and IF it can...it does so by knowing which endpoint is assigned to which appliance.