MicrosoftActually my comment was a frustration with MS... I figured what you had said was true, because I often find much-desired azure features come with various caveats once they are actually provided, and this sort of limitation was almost expected. And indeed, other documentation I had read seemed to agree with what you had written. But on re-reading the docs just now, it looks like you can have outbound control in a consumption plan as long as it's a workload profile environment, not a consumption environment. This is a bit confusing, because it's not clear what the "workload profile" environment is actually doing here. Or rather, why would anyone ever create a "consumption environment with a consumption plan" rather than create a "workload profile environment with a consumption plan"? I can't see any disadvantage to the "workload profile environment" choice. Do you have any clarification on that point?
