You have an Azure subscription that contains the virtual networks shown in the following table.

Statement

Answer

From VM1, you can access File1 by using a private IP address.

Yes

From VM2, you can access File1 by using a private IP address.

Yes

From VM2, you can access File2 by using a private IP address.

No

The private endpoint is configured for the blob sub-resource of contoso2024. Azure Storage private endpoints are created for individual storage services. Microsoft documents separate private endpoint targets for blob , file , queue , table , and other supported storage services. Therefore, PE1 provides private connectivity to Blob Storage, which contains File1, but it does not provide a private endpoint for the Azure Files service that contains File2. Microsoft Learn

VM1 → File1 = Yes. VM1 is in VNet1, and VNet1 is peered with VNet2. A private endpoint has an IP address in Subnet21, and private endpoint connectivity can be consumed from connected virtual networks, including peered VNets, provided DNS resolves the storage Blob endpoint to that private IP. Microsoft Learn

VM2 → File1 = Yes. VM2 resides directly in VNet2, where the blob private endpoint exists, so it can reach File1 through the endpoint ' s private IP.

VM2 → File2 = No. File2 resides in an Azure file share , which requires a separate private endpoint targeting the file sub-resource and normally uses the privatelink.file.core.windows.net private DNS zone. The existing blob private endpoint cannot provide private-IP connectivity to Azure Files.