For me this problem is related with Global VNET Peering limitation. If I would like to connect to a kubernetes exposed service from a VM running in different VNET connected by Global VNET peering, it fails. I must use VNET2VNET only for this limitation.
Thank you for the suggestion. It would help if you can share your use case.
Please consider using automation approach based on resource manager templates – see https://aka.ms/apimdevops.