Action required: Your help is needed to unlock resources to allow OS Upgrade to Server 2022

Vanessa Hew 0 Reputation points
2025-11-27T03:33:28.53+00:00

Required action

To enable us to proceed with the necessary upgrades, we request that you temporarily unlock your Azure resources and Network Security Groups (NSGs) to allow changes.

Could I get the steps on Azure portal to 'unlocking Azure resources and NSGs' mentioned above?

Azure Resource Mover
Azure Resource Mover
An Azure service used for moving multiple resources between Azure regions.
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Suchitra Suregaunkar 4,210 Reputation points Microsoft External Staff Moderator
    2025-11-27T04:40:32.67+00:00

    Hello Vanessa Hew

    Thank you for posting your query on Microsoft Q&A platform.

    Check for Resource Locks:

    Locks prevent changes to resources. You need to remove them temporarily.

    Steps in Azure Portal:

    1. Sign in to Azure Portal.
    2. Navigate to the resource (VM, resource group, etc.).
    3. In the left menu, select Locks.
    4. If you see any locks (e.g., Read-only or CanNotDelete), click the lock name.
    5. Select Delete to remove the lock.

    Review NSG Rules:

    NSGs control traffic. If upgrade traffic is blocked, you need to adjust rules.

    Steps in Azure Portal:

    1. In the portal, search for Network security groups → open the NSG attached to your VM NIC and/or subnet.
    2. Review Inbound security rules and Outbound security rules.
    3. Temporarily allow the ports/protocols you need for the upgrade (examples below).
      • RDP: TCP 3389 inbound to your admin IP(s) (least‑privilege).
      • WinRM (HTTP/HTTPS): TCP 5985/5986 inbound from your management network if used. (Ensure matching Windows firewall rules inside the VM.)
      • Windows Update/Content delivery (outbound): allow HTTP/HTTPS (80/443); for Azure Firewall/advanced scenarios prefer FQDN/App rules per current guidance instead of deprecated service tags for update scanning.
    4. Save changes and run the upgrade.
    5. After the upgrade, revert NSG changes to your baseline.

    Validate Connectivity:

    • Ensure the VM can reach Windows Update or upgrade media sources.
    • If using private networks, confirm outbound connectivity via firewall or NSG adjustments.

    After Upgrade:

    1. Reapply resource locks (Read‑only/CanNotDelete) at the original scopes.
    2. Reinstate NSG baselines (remove temporary “Allow” rules, re‑enable any “Deny” rules)

    Reference: https://dori-uw-1.kuma-moon.com/en-us/azure/azure-resource-manager/management/lock-resources?tabs=json and https://dori-uw-1.kuma-moon.com/en-us/azure/governance/policy/samples/nist-sp-800-53-r5

    Thanks,

    Suchitra.


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.