content_sources: - type: mslearn-adapted url: https://learn.microsoft.com/azure/azure-functions/functions-networking-options - type: mslearn-adapted url: https://learn.microsoft.com/azure/app-service/overview-nat-gateway-integration - type: mslearn-adapted url: https://learn.microsoft.com/azure/nat-gateway/nat-overview diagrams: - id: nat-gateway-architecture type: flowchart source: self-generated justification: "NAT Gateway integration pattern from MSLearn documentation" based_on: - https://learn.microsoft.com/azure/app-service/overview-nat-gateway-integration content_validation: status: verified last_reviewed: 2026-04-12 reviewer: agent core_claims: - claim: "Azure Functions plans without VNet integration cannot use NAT Gateway for outbound egress control" source: https://learn.microsoft.com/azure/azure-functions/functions-networking-options verified: true - claim: "App Service VNet integration can route outbound traffic through a NAT Gateway attached to the integration subnet" source: https://learn.microsoft.com/azure/app-service/overview-nat-gateway-integration verified: true - claim: "NAT Gateway provides stable outbound public IP addresses for internet egress" source: https://learn.microsoft.com/azure/nat-gateway/nat-overview verified: true

Scenario 4: Fixed Outbound IP (NAT Gateway)¶

Stable outbound IP addresses for function app egress through NAT Gateway, enabling IP-based allowlisting on downstream services.

When to Use¶

• Downstream services require IP allowlisting (legacy firewalls, third-party APIs)
• Regulatory requirements for predictable egress identity
• Multi-region deployments needing consistent outbound IPs per region
• SaaS integrations that authenticate by source IP

Architecture¶

flowchart TD
    INET[Internet] -->|HTTPS| FA[Function App]

    subgraph VNET["VNet"]
        subgraph INT_SUB["Integration Subnet + NAT Gateway"]
            FA --> NAT[NAT Gateway]
        end
        subgraph PE_SUB["Private Endpoint Subnet"]
            PE_BLOB[PE: blob]
        end
    end

    NAT --> PIP[Public IP<br/>203.0.113.10]
    PIP --> EXTERNAL[External Service<br/>IP Allowlist: 203.0.113.10]

    PE_BLOB --> ST[Storage Account]
    FA --> PE_BLOB

    style FA fill:#0078d4,color:#fff
    style VNET fill:#E8F5E9,stroke:#4CAF50
    style NAT fill:#FCE4EC,stroke:#E91E63
    style PIP fill:#FCE4EC,stroke:#E91E63

Supported Plans¶

[^1]: Basic (B1) supports VNet integration per Azure documentation, but is not tested or recommended for NAT Gateway scenarios in this guide. Use Standard (S1+) for production.

Prerequisites¶

Complete Scenario 2: Private Egress first. This scenario adds NAT Gateway to the integration subnet.

Required from Scenario 2: - [ ] Function App with VNet integration enabled - [ ] Integration subnet configured

Additional requirements: - [ ] Public IP address or prefix for NAT Gateway - [ ] NAT Gateway resource

Step-by-Step Configuration¶

Step 1: Create Public IP for NAT Gateway¶

az network public-ip create \
  --name "pip-nat-func" \
  --resource-group "$RG" \
  --location "$LOCATION" \
  --sku Standard \
  --allocation-method Static \
  --zone 1 2 3

Step 2: Create NAT Gateway¶

az network nat gateway create \
  --name "nat-func" \
  --resource-group "$RG" \
  --location "$LOCATION" \
  --public-ip-addresses "pip-nat-func" \
  --idle-timeout 10

Step 3: Associate NAT Gateway with Integration Subnet¶

az network vnet subnet update \
  --name "snet-integration" \
  --resource-group "$RG" \
  --vnet-name "$VNET_NAME" \
  --nat-gateway "nat-func"

Step 4: Get NAT Gateway Public IP¶

az network public-ip show \
  --name "pip-nat-func" \
  --resource-group "$RG" \
  --query "ipAddress" \
  --output tsv

Save this IP address for downstream allowlisting.

Step 5: Enable Route All (Premium/Dedicated Only)¶

For Premium and Dedicated plans, ensure all egress routes through VNet:

az functionapp config appsettings set \
  --name "$APP_NAME" \
  --resource-group "$RG" \
  --settings "WEBSITE_VNET_ROUTE_ALL=1"

Using Public IP Prefix (Multiple IPs)¶

For high-throughput workloads, use a public IP prefix instead of a single IP:

# Create IP prefix (e.g., /30 = 4 IPs)
az network public-ip prefix create \
  --name "pip-prefix-nat-func" \
  --resource-group "$RG" \
  --location "$LOCATION" \
  --length 30

# Create NAT Gateway with prefix
az network nat gateway create \
  --name "nat-func" \
  --resource-group "$RG" \
  --location "$LOCATION" \
  --public-ip-prefixes "pip-prefix-nat-func" \
  --idle-timeout 10

Verification¶

Check NAT Gateway Association¶

az network vnet subnet show \
  --name "snet-integration" \
  --resource-group "$RG" \
  --vnet-name "$VNET_NAME" \
  --query "natGateway.id" \
  --output tsv

Verify Outbound IP¶

Create a function that calls an external service showing the source IP:

curl --request GET "https://$APP_NAME.azurewebsites.net/api/check-ip"

Or call httpbin.org to see your egress IP:

# Example function code
import azure.functions as func
import requests

def main(req: func.HttpRequest) -> func.HttpResponse:
    response = requests.get("https://httpbin.org/ip")
    return func.HttpResponse(response.text)

Expected: The origin field should match your NAT Gateway public IP.

Test from Function App¶

az functionapp show \
  --name "$APP_NAME" \
  --resource-group "$RG" \
  --query "outboundIpAddresses" \
  --output tsv

Capacity Planning¶

NAT Gateway has specific capacity limits:

For high-scale workloads: - Add more public IPs or use IP prefix - Distribute across multiple NAT Gateways with different subnets

Cost Considerations¶

NAT Gateway pricing:

Troubleshooting¶

Combining with Private Ingress¶

NAT Gateway can be combined with site private endpoint for full isolation:

flowchart TD
    CORP[Corporate Client] -->|Private IP| PE_APP[Site Private Endpoint]
    PE_APP --> FA[Function App]

    subgraph VNET["VNet"]
        PE_APP
        FA --> NAT[NAT Gateway]
    end

    NAT --> PIP[Public IP: 203.0.113.10]
    PIP --> EXTERNAL[External API]

    style FA fill:#0078d4,color:#fff
    style NAT fill:#FCE4EC,stroke:#E91E63

See Also¶

• Networking Scenarios Overview
• Scenario 2: Private Egress
• Scenario 3: Private Ingress
• Platform: Networking

Sources¶

• Azure Functions networking options (Microsoft Learn)
• NAT Gateway integration with App Service (Microsoft Learn)
• What is Azure NAT Gateway? (Microsoft Learn)