How to Send POS Sales Data from Power Apps to Corporate API via Power Automate Using Static IP

hi Sho​  You’re not missing anything here, this is a very common limitation with Power Automate Cloud.

Short answer: Power Automate Cloud can’t give you a static outbound IP, and there’s no supported way to make it do so. Because it runs in a shared, multi-tenant environment, the outbound IPs are dynamic by design.

What you’re describing routing the call through an Azure-hosted intermediary with a static IP is exactly how most teams solve this. The typical pattern looks like this:

Power Apps → Power Automate (Cloud) → Azure service (static IP) → Corporate API

In practice, people usually pick one of these:

• Logic Apps (single-tenant) in a VNET with a NAT Gateway
• Azure Functions (App Service plan, not Consumption) with VNET + NAT Gateway

Both options stay 100% cloud, give you a fixed public IP to whitelist, and are fully supported. Power Automate just calls the Azure endpoint over HTTPS, and that service forwards the request to the corporate API.

Why this works well:

• Meets strict IP allow-listing requirements
• No on-prem gateway or Power Automate Desktop
• Easy to add logging, retries, validation, and auth in one place
• Scales cleanly as volume grows

So yes, your assumption is correct, and you’re already aligned with the recommended architecture. Power Automate handles the workflow, and Azure handles the networking constraints.