Question 710
An engineer enabled the Microsoft.Storage service endpoint on subnet app-subnet and added that subnet to a storage firewall allowlist. The storage endpoint still resolves to an Azure public service IP. Security now requires clients to connect through a private IP address allocated inside the VNet. Which design change meets that stricter network requirement?
Explanation
Correct Answer
Azure service endpoints extend VNet identity to supported Azure PaaS services while the service endpoint retains public service IP addressing. A private endpoint is the mechanism that presents an approved service subresource at a private IP on a NIC in the selected VNet. The administrator should create that connection, configure relevant private DNS resolution, and validate the allowed route before closing unwanted public access paths. Service endpoint firewall rules alone do not satisfy the new private-address requirement.
Incorrect Answers
NSGs and service tags can influence allowed traffic, but they cannot transform a storage service public endpoint into a VNet private IP. The service endpoint remains a supported network identity/routing approach using service public addresses. Private Link and private DNS are required for a private endpoint design.
Allocating a public IP address to another resource does not cause an Azure Storage service FQDN to resolve to a private IP. Storage is a platform service with its own endpoint. A private endpoint must be created and approved for the relevant Storage service subresource.
Storage redundancy protects data across infrastructure locations; it does not determine whether clients address a private endpoint or a public Storage service IP. GZRS can be appropriate for availability, but it cannot reconfigure a VNet DNS response into a private network interface.