Forum Discussion

SomeRandomNPC's avatar
SomeRandomNPC
Copper Contributor
Jun 19, 2024

LAB VM Hardening loosing connectivity

Hi, I need some help here,

 

I am working on a project on an AzureLab to automate the installation of a Privileged Access Management solution (CyberArk). The problem I am encountering is that the Vault VM (containing passwords) needs a drastic hardening.

 

Everything works until I restart the VM after the hardening process from AzureLAB (I am able to restart it from windows without a problem). The starting button never ends and after 10 minutes the VM is disconected. However, until those 10 minutes I am still able to use it as if it worked completly fine.

 

My only clue here is I suppose that AzureLAB uses behind the scenes a specific utility to check if the VM is actually started, wich is blocked by my hardening ?

 

Does anyone already encountered a similar problem ?

Any help would be appreciated, thanks.

Azure Lab Services
  • Rahul_Srivastava's avatar
    Rahul_Srivastava
    Icon for Microsoft rankMicrosoft
    Jun 26, 2024
    It looks like the outbound access for the lab agent is being blocked. Please add the following endpoints for outbound traffic:
     
    -The IP for an Azure endpoint required for Azure vm communication
        168.63.129.16
     
    -The host name used for storage account.
        'labservicesprod.blob.core.windows.net'
     
    -The host name used for heartbeats.
     
        'labs-westus.prod.labservices.azure.com',
        'labs-westeurope.prod.labservices.azure.com',
        'labs-westcentralus.prod.labservices.azure.com',
        'labs-ukwest.prod.labservices.azure.com',
        'labs-uksouth.prod.labservices.azure.com',
        'labs-uaenorth.prod.labservices.azure.com',
        'labs-switzerlandnorth.prod.labservices.azure.com',
        'labs-southeastasia.prod.labservices.azure.com',
        'labs-southcentralus.prod.labservices.azure.com',
        'labs-southafricanorth.prod.labservices.azure.com',
        'labs-norwayeast.prod.labservices.azure.com',
        'labs-northeurope.prod.labservices.azure.com',
        'labs-northcentralus.prod.labservices.azure.com',
        'labs-koreacentral.prod.labservices.azure.com',
        'labs-japaneast.prod.labservices.azure.com',
        'labs-germanywestcentral.prod.labservices.azure.com',
        'labs-francecentral.prod.labservices.azure.com',
        'labs-eastus2euap.prod.labservices.azure.com',
        'labs-eastus2.prod.labservices.azure.com',
        'labs-eastus.prod.labservices.azure.com',
        'labs-eastasia.prod.labservices.azure.com',
        'labs-centralus.prod.labservices.azure.com',
        'labs-centralindia.prod.labservices.azure.com',
        'labs-canadaeast.prod.labservices.azure.com',
        'labs-canadacentral.prod.labservices.azure.com',
        'labs-brazilsouth.prod.labservices.azure.com',
        'labs-australiasoutheast.prod.labservices.azure.com',
        'labs-australiaeast.prod.labservices.azure.com',

    Please let us know if this fixes the issue. Thank you.

Share