Abhishiktha Somisetty (Tata Consultancy Services Limi) Kumar can you confirm if this can be transferred internally to respective team who can help us in establishing the connection to required private end point rather than connecting to the latest Private

Abhishiktha Somisetty (TCS) 20 Reputation points Microsoft External Staff
2025-12-18T12:26:51.33+00:00

Unable to connect to storage account from the VM, It is taking the latest private end point rather than the required end point. How to configure the required private end point to connect to storage account from VM.

Azure Storage
Azure Storage
Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
0 comments No comments
{count} votes

Answer accepted by question author
  1. Vallepu Venkateswarlu 3,140 Reputation points Microsoft External Staff Moderator
    2025-12-18T12:40:34.4466667+00:00

    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 210246-screenshot-2021-12-10-121802.pngand “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.