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:
- Sign in to Azure Portal.
- Navigate to the resource (VM, resource group, etc.).
- In the left menu, select Locks.
- If you see any locks (e.g., Read-only or CanNotDelete), click the lock name.
- 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:
- In the portal, search for Network security groups → open the NSG attached to your VM NIC and/or subnet.
- Review Inbound security rules and Outbound security rules.
- 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.
- Save changes and run the upgrade.
- 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:
- Reapply resource locks (Read‑only/CanNotDelete) at the original scopes.
- 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.