An Azure service that stores unstructured data in the cloud as blobs.
For a Logic App Standard, the IP to allow depends on which SFTP connector is being used:
- If using the built-in/In-app SFTP connector in Logic App Standard, the connection runs in the single-tenant environment. With Virtual network integration configured, the outbound connection can use the public IP of the NAT gateway.
- If using the shared/managed SFTP-SSH connector, it runs in the multi-tenant environment, so adding the Logic App Standard app outbound IP list is not the correct approach for VNet-routed access.
For the scenario described, the supported configuration from the available guidance is:
- In the Logic App Standard resource, go to Settings > Network > Virtual network integration.
- Under Application routing, make sure Outbound internet traffic is selected.
- Under Virtual network routing, make sure the NAT gateway is selected.
- On the storage account networking side, allow the public IP of the NAT gateway rather than the Logic App outbound IP list.
If the workflow is using the built-in SFTP connector, this aligns with Logic App Standard behavior because the built-in connector runs in the single-tenant environment and can directly connect by using the app environment networking.
Also verify these Azure Blob Storage SFTP requirements:
- SFTP access uses the Blob Storage endpoint (
blob.core.windows.net), not the Data Lake endpoint. - If access is restricted to selected networks, the firewall/network configuration affects connectivity to Azure Storage endpoints.
- If connecting from outside Azure or from restricted networks, port 22 must be allowed.
If the trigger currently uses SFTP-SSH rather than the built-in SFTP connector, switching to the built-in SFTP connector in Logic App Standard is the relevant configuration path when the requirement is to route through the VNet/NAT gateway.