Taking the "Public" out of Public Clouds: Getting Started with Private Endpoints
summary
Defines a checklist of seven steps required to make Azure private endpoints actually work: create a private endpoint resource, couple it to the Azure resource and correct target subresource, assign a VNet subnet IP, deploy or reference the exact-named private DNS zone, add the A record and add the VNet link. Demonstrates in the Azure Portal with a VM and Storage Account (blob and table) where public access is disabled and the service is reachable only from inside the VNet, and warns to centralize DNS to avoid VNet-link conflicts.
AI-written summary · about
chapters (6)
- 0:00Introduction to private endpoints
- 7:50Seven steps to success
- 21:31Demo of private endpoint deployment
- 32:09Centralized DNS in hub and spoke
- 38:52Common mistakes with private endpoints
- 44:50Q&A and wrap-up
related talks
38mSecure Azure Resources using Azure Private Link
53mProtect Your Data: Azure Networking Essentials for Developers
21mSecure apps on Azure Spring Cloud with Managed Virtual Network
50mSecuring Native Cloud Application Perimeter
01h 00mEverything You Always Wanted to Know About Azure Security But Were Afraid to Ask
43mDefending the Cloud: Securing Your Microsoft Data Workloads
22mAzure Infrastructure - What Not to Do- 22mAzure Infrastructure - What Not to Do