Transcrito
Azure Private Link - Simply Explained
18 de jul. de 2026 ·
16m 8s
Descarga y escucha en cualquier lugar
Descarga tus episodios favoritos y disfrútalos, ¡dondequiera que estés! Regístrate o inicia sesión ahora para acceder a la escucha sin conexión.
Azure Private Link - Simply Explained
Descripción
Many Azure admins assume their storage accounts and databases are private just because they run in Azure, but they are reachable from the internet by default. This episode explains Azure...
mostra más
Many Azure admins assume their storage accounts and databases are private just because they run in Azure, but they are reachable from the internet by default. This episode explains Azure Private Link in plain English for cloud beginners and IT pros, covering private endpoints, DNS, alternatives like VPN and ExpressRoute, costs and the gotchas to avoid.
In this episode
Key takeaways
Worth quoting
“Your subscription is a billing and management boundary, not a network boundary. By default, your Azure services are reachable from the internet.” – Mirko Peters (02:08)
“Enabling a private endpoint does not turn off the public endpoint automatically. They can both exist at the same time. If you create a private endpoint, but never touch the public endpoint settings, your storage account is still reachable from the internet.” – Mirko Peters (03:25)
Explore more on M365.FM
Follow and rate M365.FM in your podcast app, and join the free M365 community at m365con.net.
Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-microsoft-365-azure-cloud-power-platform-ai--6704921/support.
mostra menos
In this episode
- 00:00 – Why Azure services are not private by default
- 00:50 – The old way: public endpoints everywhere
- 02:29 – The private endpoint as a network interface card
- 04:17 – DNS and private DNS zones
- 08:08 – Private Link vs. VPN, ExpressRoute and service endpoints
- 10:11 – Private Link service for your own applications
- 11:47 – Security, compliance and cost
- 13:36 – Implementation gotchas and takeaway
Key takeaways
- Azure PaaS services such as Storage, SQL and Key Vault ship with public endpoints, and a subscription is a billing boundary, not a network boundary.
- Azure Private Link places a private endpoint with a private IP inside your virtual network, and private DNS zones make the existing service URL resolve to it so applications need no changes.
- Creating a private endpoint does not disable public access, on-premises clients need DNS forwarding, and the extra per-endpoint cost is best justified for sensitive, regulated production workloads.
Worth quoting
“Your subscription is a billing and management boundary, not a network boundary. By default, your Azure services are reachable from the internet.” – Mirko Peters (02:08)
“Enabling a private endpoint does not turn off the public endpoint automatically. They can both exist at the same time. If you create a private endpoint, but never touch the public endpoint settings, your storage account is still reachable from the internet.” – Mirko Peters (03:25)
Explore more on M365.FM
- Episode page: the full episode with chapters, quotes and FAQ on Azure Private Link
- Azure Private Link – the service that places a private endpoint with a private IP inside your virtual network
- Azure ExpressRoute – the private circuit to Azure that still needs Private Link for private PaaS access
- Compliance – how Private Link helps prove sensitive data stays off public networks for HIPAA, GDPR, PCI
- Related episode: The Death of the Chatbot: Why Your Dataverse Strategy Is Broken
Follow and rate M365.FM in your podcast app, and join the free M365 community at m365con.net.
Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-microsoft-365-azure-cloud-power-platform-ai--6704921/support.
Información
| Autor | Mirko Peters M365, Azure & AI |
| Organización | m365 FM |
| Página web | www.m365.fm |
| Etiquetas |
Copyright 2026 - Spreaker Inc. an iHeartMedia Company
Comentarios