Power Automate

QuotaGuard puts your two static IPs onto the target API's allowlist for Microsoft Power Automate through a small relay you host at the connectivity layer. Because Power Automate cannot set an HTTP proxy, the relay forwards each outbound call through QuotaGuard, so the target sees one of your two static IPs instead of Microsoft's shared, rotating connector ranges. Trusted for static IP connectivity since 2013.

• Relay-Based Setup: Host a small relay function on AWS Lambda or a Google Cloud Function, set your QuotaGuard connection URL and a secret key, and point Power Automate's HTTP action at the relay with the target API carried in an X-Target-URL header and the secret in an X-Relay-Key header. Register your two static IPs with the target API once.
• The Target Sees Static IPs, Not Microsoft Power Automate's: The relay forwards every request through QuotaGuard, so the target API sees your two static IPs. Power Automate's rotating egress and the relay host's own IP never reach the allowlist check.
• Multi-Platform Support: The relay deploys on AWS Lambda or Google Cloud Functions, and the same relay serves Bubble, Zapier, and any other platform that can call a URL but cannot set a proxy. One piece of infrastructure covers them all.
• Production-Grade Reliability: A load-balanced pair of static IPs with health checks and automatic failover. Both IPs go on the target's allowlist, and traffic routes through whichever responds.
• Shield for Regulated Data: For HIPAA, PCI-DSS, or SOC 2 workflows, QuotaGuard Shield uses SSL passthrough so QuotaGuard never decrypts the data flowing between the relay and the target API.

Gate note: You only need this when the API Microsoft Power Automate calls enforces IP allowlisting. If the target rejects requests from unregistered IPs, Power Automate's shared egress fails and you need the two static IPs. Calls to APIs with no IP allowlist do not need it.