Using private endpoints to lock down cloud access
Start at the client
Imagine an internal API reading a blob through its usual storage hostname. A private endpoint gives the target service a private address on your virtual network. The API still needs the correct name resolution, network reachability and data permissions.
Walk the route
Resolve the storage hostname inside the API runtime. Check that it resolves to the intended private address and that the endpoint targets the required storage subresource. Test an authorised read using the workload identity.
Verify both access paths
Review public network access separately. Test the same operation from an external network using an appropriately controlled test identity. Keep the two results together so reviewers can see which path is allowed and why.