ASE creation validation UI assumptions to be reviewed
In current implementation ASE basic tab validation assumes that VNET and ASE should be deployed in different RG's. When RBAC in organisation is arranged on RG level and DevOps team is expected to deploy everything in one RG, ASE UI gives false-positive privilege validation errors (as it assumes privileges on subscription level), while you are actually able deploy using download/deploy the template. Quite confusing to see Create button disabled in this case. Hopefully this scenario could be taken into account in the future implementations. (support case 119031524002148 suggested to post it here).