This is interesting to know about. Are you using 7.3? If this is a confirmed issue, the only workaround may be to use a different naming scheme for Azure. Please update the thread with whatever you hear from support.
We are using 7.3. A different naming scheme may circumvent the issue, but bypasses our enterprise standards for naming. Also, it still would be unable to increment the naming prefix in vRA, which means it would only increment based on what Azure VMs currently exist. This process is very quick in a small environment, but if we reach hundreds of VMs, the process will likely become much slower.
We have a ticket opened and as soon as we receive resolution, I will update this thread. Thanks.