Hi Allmhuran,
I submitted an edit for review to remove the erroneous statement that the Dedicated workload profile must be used. Many thanks again for pointing out my mistake. Hopefully, at least in this instance, you will forge a more positive impression of Microsoft and Azure Container Apps.
Workload Profiles is a newer architecture than the Consumption Only architecture that Azure Container Apps used initially. It is this newer architecture with the two plans, Dedicated and Consumption, that makes the egress control possibility. I can see the confusion with the term consumption and often find myself being very careful how I word what environment and plan I mean. In my opinion, our naming here has been a bit ambiguous, unfortunately. You are witnessing an evolution of architecture as Azure Container Apps continues to grow.
This article should lay it out a bit more clearly, I hope. While we will continue to support Consumption Only, my recommendation for anyone using Azure Container Apps going forward is to use Workload Profiles with either consumption or dedicated as this is built on newer architecture.
I hope this helps!
Simon