Resolving Connections Between MS Power Automate and SaaS REST API

Products

• Automic SaaS

Issue/Introduction

When attempting to connect to the Automic SaaS REST API using Microsoft Power Automate, the connection fails with the following error message:

HTTP request failed as there is an error: 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.'

This error typically occurs when the request originates from outside the customer's internal network

Cause

The issue is caused by the Automic SaaS infrastructure blocking incoming traffic from Microsoft Power Automate IP ranges that have not been whitelisted. Because Power Automate uses a wide range of dynamic IP addresses, the requests fail to establish a connection with the [HOSTNAME] endpoint

Resolution

To resolve this issue, the relevant Microsoft Power Automate IP ranges must be whitelisted within the Automic SaaS environment.

Step 1: Identify Required IP Ranges

Identify the specific outbound IP addresses or ranges used by Power Automate for your region. Microsoft provides documentation for these ranges, but they can be extensive.

Step 2: Request Whitelisting

Open a support case with Broadcom to request the whitelisting of the identified IP ranges for your specific SaaS instance.

Step 3: Verification

Once the IP addresses have been whitelisted by the SaaS Operations team, verify the connection by running the Power Automate flow again. If the connection still fails, you can use the following endpoint to identify the specific IP address making the request: https://ip.saas.automic.com/

By calling this URL from within your Power Automate tool, the response will return the public IP address being used, which can then be verified against the whitelisted list