Unknown Resource name for Virtual machine scale set in email

Jeffrey Yu (RD-AS) 0 Reputation points

I received an email regarding "Planned maintenance for Azure will impact virtual machines in Australia East". In the Account Information section of the email, the Resource name given is "_aks-reportpool-16178916-vmss_29". However, I can't find this Resource in the instance on the Azure portal but “aks-reportpool-16178916-vmss” is my Virtual machine scale set. What could be the reason for this?

Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
7,404 questions
{count} votes

2 answers

Sort by: Most helpful
  1. SaiSurya Vamsi Sapireddy 0 Reputation points

    There could be naming convention issues like the underscore which was added before the vm name and also there could be some backend services which could be created for the scaleset which can be viewed in portal.

    0 comments No comments

  2. kobulloc-MSFT 25,156 Reputation points Microsoft Employee

    Hello, @Jeffrey Yu (RD-AS) !

    Why am I seeing an underscore in the resource name for a resource in my Virtual Machine Scale Set (VMSS)?

    Virtual Machine Scale Sets will generate a unique name for each VM in the scale set. The naming convention differs by orchestration mode, but matches the format for uniform orchestration instance ID:

    • Flexible orchestration Mode: {scale-set-name}_{8-char-guid}
    • Uniform orchestration mode: {scale-set-name}_{instance-id}

    AKS creates and manages some Azure resources for you so it looks like there is an AKS VMSS instance that will be subject to maintenance.

    Here you can see VMSS_InstanceID when viewing the VMSS instance:

    User's image

    I hope this has been helpful! Your feedback is important so please take a moment to accept answers.

    If you still have questions, please let us know what is needed in the comments so the question can be answered. Thank you for helping to improve Microsoft Q&A!

    User's image

    0 comments No comments