'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Find the Source IP for Power Automate SFTP Connections
Question details
The user needs to identify the correct source IP addresses for a Power Automate cloud flow to successfully upload attachments to an on-premises SFTP server.
- Product
- Power Automate
- Device & OS
- not provided
- Scenario
- A cloud flow is configured to retrieve Outlook attachments and upload them to an on-premises SFTP server, but the connection is failing despite whitelisting published Power Platform IP addresses.
- Observed behavior
- The SFTP connection is blocked or times out because the actual outbound IP address used by the Power Automate flow is not recognized or whitelisted by the on-premises firewall.
Ensure your on-premises SFTP server's firewall logs are configured to actively record rejected inbound connection attempts, as this is the fastest way to identify the exact IP being blocked.
Consult the Microsoft Power Automate Community
Because Power Automate networking and on-premises SFTP configurations involve highly specific architectural details, reaching out to the official community is the best way to get targeted guidance.
Power Automate infrastructure relies heavily on Azure, meaning the outbound IPs can sometimes differ from standard documentation. The community experts and Microsoft engineers actively monitor these forums to provide updated routing information.
Open your web browser and navigate to the official Microsoft Power Automate Community page.
Sign in using your Microsoft 365 or Power Platform account credentials.
Create a new topic in the relevant sub-forum. Be sure to mention your region, the specific SFTP connector you are using, and the fact that published IP whitelisting has already failed.
Verify Azure Logic Apps IP Address Ranges
Since Power Automate flows are built on top of Azure Logic Apps infrastructure, you may need to whitelist specific Azure datacenter IPs rather than just standard Power Platform IPs.
Looking for a Lightweight Alternative for Office Productivity?
While complex cloud automation and SFTP integration might require specialized Microsoft tools, your daily document, spreadsheet, and presentation tasks don't need heavy, expensive software. WPS Office provides a free, highly compatible alternative to Microsoft Office, ensuring seamless file management and excellent performance.
- 1. Download the Installer: Visit the official WPS Office website and click the 'Free Download' button.
- 2. Install WPS Office: Run the downloaded lightweight setup file and follow the quick on-screen instructions.
- 3. Open Your Documents: Launch WPS Office and open your existing Microsoft Office files seamlessly with zero formatting loss.
Frequently Asked Questions
Why are my published Power Platform IP addresses failing to connect?
Power Automate routes its traffic through the underlying Azure Logic Apps infrastructure. If you only whitelist standard Power Platform outbound IPs, the specific regional Azure data center IPs that process your flow's requests may still be blocked by your firewall.
Can I set a static IP for my Power Automate cloud flow?
Power Automate cloud flows do not natively support assigning a single static IP address out of the box. To use a consistent static IP, you generally need to route your flow's outbound traffic through an Azure API Management or a custom Azure NAT Gateway setup.
Where can I find the exact IP that attempted the SFTP connection?
The most reliable method is to trigger the Power Automate flow and immediately inspect the firewall logs or security event logs of your on-premises SFTP server for dropped inbound connections on port 22 (or your custom SFTP port).
