Hi @BalajiNext,
In order to securely have access to SFTP enabled Blob Storage for third parties from the specific IPs.By configuring NAT on your on-premises firewall with the private IP of the private endpoint can work. Here, assign a public IP on your on-prem firewall and configure NAT rules to map the public to private IP of the private endpoint.Once the public IP configured. Allow the inbound traffic from specific third-party IPs to the public IPs on port 22 (SFTP) and please make sure that the NAT rule translates this traffic to the private endpoint's private IP.
Then provide the third-party IPs with the below SFTP connection string:
<storage-account-name>.<local-user>@<public-IP>
Replace <storage-account-name>
with your storage account name, <local-user>
with the SFTP user, and <public-IP>
with the public IP of your on-prem firewall.
Also, please make sure that the DNS resolution for the private endpoint is exactly configured on your on-prem networks.
However, please try an alternative option as is to set up a secure application or service on your on-premises network to act as a proxy for SFTP access. This service would manage the SFTP connections from third parties and then securely transfer the files to Azure Blob Storage using the private endpoint.I hope by following the above will help in resolving the issue.
Please let us know in the comments below, if the issue is resolved or still persists. We will be glad to assist you closely.
Please do consider to “up-vote”
wherever the information provided helps you, this can be beneficial to other community members. Accepted answers show up at the top, resulting in improved discoverability for others.