The change we would like to see is greater control of the template initiated by LCS to created cloud-hosted F&O dev environments.

Once the environment and all infrastructure is created in Azure, the use of NLBs/Public IPs is violating our security principles and then our team need to go and fix them to implement JIT access.

The ability to control this when generating the environment would be more secure and a great benefit to avoid additional work.