Power Automate private network configuration guide
On this page
In this guide, you will learn how configure access for power automate within a private instance of CluedIn.
This guide is applicable to only private CluedIn instances.
Advanced Configuration: Power Automate / Power Apps in a Private Network
To enable Power Automate or Power Apps to communicate with CluedIn from within a private network, external access must be configured through a publicly accessible endpoint.
Connectivity Requirements
Power Automate must access CluedIn through a public URL. The data flow diagram (see below) illustrates how Power Automate routes requests to CluedIn. To support this setup, the following components are required:
-
Public DNS
-
Public IP Address
CluedIn Server Configuration
The public DNS must be defined on the CluedIn server using an environment variable:
CLUEDIN_APPSETTINGS__PROXY_PUBLICURL = "workflow-{env}.{your-domain}"
-
Replace
{env}with your deployment environment (e.g.,dev,prod) -
Replace
{your-domain}with your organization’s domain name
Firewall Configuration
Power Automate operates from Microsoft-managed IP ranges, which must be allowed through your network perimeter.
If you’re using Azure Firewall, Microsoft provides a service tag to simplify rule configuration:
-
Use the service tag:
AzureConnectorsLogicApps -
This automatically includes all required outbound IP ranges for Power Automate and related services
