I am currently deploying an ASP.NET Core Web API on Azure App Service and I need this service to utilize a static public IP address. The reason behind this requirement is that there is a 3rd party integration which necessitates IP whitelisting.
https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/linux_web_app
Moreover, I also plan to deploy the same ASP.NET Core Web API in Azure Container Registry (ACR) and leverage Azure Kubernetes Service (AKS) for orchestration. I mention this in case it impacts the process of assigning the static public IP to the Azure App Service.
Edit
I created a simple App Service using Terraform code:
resource "azurerm_service_plan" "asp" {
name = "${local.basename}-asp"
resource_group_name = module.resource_group.name
location = var.location
os_type = "Linux"
sku_name = "P1v2"
}
resource "azurerm_linux_web_app" "app" {
name = "${local.basename}-app"
resource_group_name = module.resource_group.name
location = var.location
service_plan_id = azurerm_service_plan.asp.id
site_config {}
}
Does that mean that if I whitelist all of these IP addresses in Binance's API key, it's going to be okay? Just to clarify, if I wanted to have a single outbound IP address, then I would have needed NAT Gateway, right?

azurerm_virtual_network, followed byazurerm_public_ip, subnet, etc. But it looks like creating a virtual network and subnet is meant to be used in cases where you have two applications and you want both of them to use the same IP address?