Hi @ Abhishiktha Somisetty (TCS),
Welcome to Microsoft Q&A Platform.
This issue was caused by creating multiple Private Endpoints for the same Azure Storage sub-resource (for example, multiple Private Endpoints targeting Blob). When multiple endpoints exist for the same sub-resource and share the same Private DNS zone, Azure resolves the storage account name based on DNS, not by user selection. As a result, the VM may resolve the name to the most recently created or an unintended Private Endpoint, leading to connectivity issues.
As discussed, offline, Microsoft recommends creating separate Private Endpoints for each storage service, such as Blob, File, Queue, and Table, and ensuring the correct sub-resource is selected during Private Endpoint creation. For example, Blob access should use the blob sub-resource, while Azure Files access should use the file sub-resource.
This approach ensures that Azure creates the correct DNS records (for example, privatelink.blob.core.windows.net or privatelink.file.core.windows.net) and allows the VM to resolve to the intended Private Endpoint IP.
Once the Private Endpoints were aligned with the correct storage sub-resources, connectivity from the VM worked as expected without interruption.
References:
https://learn.microsoft.com/en-us/azure/storage/common/storage-private-endpoints https://learn.microsoft.com/en-us/azure/private-link/private-endpoint-dns
I hope this information helps resolve your issue. Please feel free to ask if the provided solution does not help or if you have any additional questions
Please
and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.