Power Apps
Built for Microsoft Power Apps's outbound API calls and IP allowlisting. Power Apps reaches external APIs through custom connectors and Power Automate flows, neither of which exposes an HTTP proxy field or lets you run a sidecar, and Microsoft's cloud egress IPs are shared and shifting across tenants, so any API that requires a fixed allowlisted IP rejects the call. QuotaGuard gives your Power Apps integration two static IP addresses through a small relay you host, so allowlisted APIs accept every request from your canvas apps, model-driven apps, custom connectors, and Power Automate flows.
QuotaGuard puts two fixed IP addresses onto the target API's allowlist for your Microsoft Power Apps integration. Because a custom connector is an OpenAPI wrapper with only a Host and Base URL and no proxy setting, a small relay you host forwards each outbound call through QuotaGuard at the connectivity layer, so the target sees one of your two static IPs instead of Microsoft's shifting egress 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 as environment variables, and point your custom connector Host at the relay URL with the target API in an X-Target-URL header. Register your two static IPs with the target API once.
- The Target Sees Static IPs, Not Microsoft Power Apps's: The relay forwards every request through QuotaGuard, so the target API sees your two static IPs. Power Apps'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 your Microsoft Power Apps integration calls enforces IP allowlisting. If the target rejects requests from unregistered IPs, Power Apps's dynamic egress fails and you need the two static IPs. Calls to APIs with no IP allowlist do not need it.