You are configuring a V4 Azure Function App that needs to connect to an external service. The external service requires all incoming requests to originate from a single, static public IP address. The Function App is currently running on an Elastic Premium plan.
Which two actions should you perform to configure the Function App for static outbound IP addresses? (Select two.)
- Configure regional virtual network (VNet) integration for the Function App to a delegated subnet.Answer
- Associate an Azure NAT Gateway with a public IP address to the integrated subnet.Answer
- CScale the Function App hosting plan down to a Consumption plan to allocate static outbound IPs.
- DConfigure a user-assigned managed identity for the Function App to grant outbound firewall access.
Answer
Configure regional virtual network (VNet) integration for the Function App to a delegated subnet, and associate an Azure NAT Gateway with a public IP address to the integrated subnet.
To route outbound traffic from a V4 Azure Function App through a static public IP address, you must first configure regional virtual network (VNet) integration. This places the outbound traffic of the Function App within a delegated subnet. Next, you associate an Azure NAT Gateway (which has an assigned static public IP address) with that delegated subnet. Any outbound internet-bound traffic from the subnet will use the NAT Gateway's static public IP.
Step-by-Step Solution
Key Concept
Configuring static outbound IP addresses for Azure Functions using virtual network integration and NAT Gateway.
Estimated Time:2m 0s