Lab 6 Ex 5 Task 2: Public IP creation fails; Create public IP resource before editing VM IP

[SkillableMG]

• Lab answer key: Deploying and configuring Windows Server on Azure VMs
• Exercise 5: Configuring Windows Server security in Azure VMs
• Task 2: Configure Inbound HTTP access to an Azure VM

When editing the az800l06-vm0 IP configuration in the above task, the public IP resource currently cannot be deployed from the Edit IP Configuration blade as specified in the instructions. The resource fails to deploy due to the Azure portal default domainNameLabel configuration now specified for that resource. The DNS record is already reserved. Please see the template and deployment excerpts below for reference.

Creation of the public IP resource via the Create a public IP address page does not enforce this default currently. To resolve the issue identified above, create the public IP resource in this way prior to the existing Task 2 steps.

Template excerpt:

{
    "type": "Microsoft.Network/publicIpAddresses",
    "apiVersion": "2022-05-01",
    "name": "az800l06-vm0-pip1",
    "location": "eastus",
    "sku": {
        "name": "Standard",
        "tier": "Regional"
    },
    "properties": {
        "publicIPAllocationMethod": "Static",
        "idleTimeoutInMinutes": 4,
        "publicIpAddressVersion": "IPv4",
        "dnsSettings": {
            "domainNameLabel": "az800l06-vm0-pip1"
        }
    },
    "id": "/subscriptions/<uuid>/resourceGroups/AZ800-L0601-RG/providers/Microsoft.Network/publicIpAddresses/az800l06-vm0-pip1"
}

Deployment exerpt:

    "error": {
      "code": "DeploymentFailed",
      "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.",
      "details": [
        {
          "code": "DnsRecordIsReserved",
          "message": "DNS record az800l06-vm0-pip1.eastus.cloudapp.azure.com is already reserved by another resource."
        }
      ]
    }

Changes proposed in this pull request:

• Create the public IP resource before continuing with the existing Task 2
• Select the already-created public IP at Task 2 step 7 (existing numbering)

[TJGitHubUser]

Verified by test team at Skillable.