Azure Container Apps Networking Deep Dive | VNET, Ingress & Private Access Scenarios

 In this video I have addressed - Azure Container Apps “Real World” Networking Scenarios - 

1. Content-web UI Application accessible over internet, content-api accessible only inside container app environment.
2. Content-web UI Application accessible over private network only (from other VNETs), content-api accessible only inside container app environment.
3. Content-web UI Application accessible over private network only (from other VNETs), content-api accessible outside of container app environment, and over private network (from other VNETs).
4. Content-web UI Application accessible over internet, content-api accessible outside of container app environment, and over private network (from other VNETs).
5. Content-web UI and Content-api both accessible over internet.

#AzureBeyondDemos #AzureContainerApps #AzureNetworking #AzureVNET #AzureIngress

#AzurePaaS #AzureCloud #AzureDeepDive

Mandatory NSG Rules URL - https://learn.microsoft.com/en-us/azure/container-apps/firewall-integration?tabs=workload-profiles

If you receive below error - 

Failed to provision IP address: Subscription is not registered for feature Microsoft.Network/AllowBringYourOwnPublicIpAddress required to carry out the requested operation

Solution run below command  in azure cli on portal - 

az feature register --name AllowBringYourOwnPublicIpAddress --namespace Microsoft.Network