HI Himanshu,
I've attached the image here of the error.
As for the azure subscription how do I know which resource to choose?
patch 11.2509.1001.21 is currently failing
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(131.20000000000002, 16%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJC%3C/text%3E%3C/svg%3E)
Joe Comeau
40
Reputation points
Errors:
Test Active Directory Domain Name Resolution
Test RP registrations are present in the subscription
the remediation is a bit convoluted and need some assistance to apply the patch
Azure Local
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(300.8, 8%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHS%3C/text%3E%3C/svg%3E)
Himanshu Shekhar 5,740 Reputation points Microsoft External Staff Moderator2026-04-16T21:59:57.96+00:00 Joe Comeau
The validation checks are reporting errors for Active Directory domain name resolution and resource provider (RP) registration. These checks confirm that the environment prerequisites are in place for the patch to be applied.
Active Directory Domain Name Resolution must be fully functional to ensure the service can successfully communicate with the domain controllers.
Resource Providers must be registered at the subscription level before dependent services or patches can be applied.
If any required RP is missing or in a partial state, remediation will fail.
Foe registering resource providers is available here: https://learn.microsoft.com/azure/azure-resource-manager/troubleshooting/error-register-resource-provider & https://learn.microsoft.com/azure/azure-resource-manager/management/resource-providers-and-types
We have validated from the backend that the solution update has now completed successfully.
The earlier health check failures were due to:
- Stale/incorrect resource provider (RP) registrations in the subscription
- A conflicting DNS configuration
Both of these issues have been mitigated:
- RP registration issue was resolved
- DNS-related issue was addressed by correcting the invalid DNS entry
At this point, the cluster is in a healthy and updated state, and no further action is required from your side. If you have any further queries, let me know. If the information is helpful, please click on Upvote and Accept Answer on it.
Sign in to comment
1 answer
Sort by: Most helpful
-
Joe Comeau 40 Reputation points
2026-04-17T16:39:40.77+00:00 -
Himanshu Shekhar 5,740 Reputation points Microsoft External Staff Moderator
2026-04-20T18:48:19.6+00:00 Please verify the following:
- The nodes can resolve the domain using DNS (correct DNS server configured)
- The nodes can discover a domain controller (domain connectivity test)
- Required AD ports (especially DNS and authentication ports) are not blocked by firewall or NSG
(AD communication heavily depends on DNS and network reachability)
If DNS or connectivity is not working correctly, the validation step will fail even if domain join previously succeeded.
For the subscription selection: You should select the same Azure subscription where your Azure Local / HCI resources are registered
Navigate to:
- Azure Portal > Subscription > Resource Providers
- Ensure required providers show Registered (not “NotRegistered” or “Registering”)
- If not registered, manually register them before retrying. Resource providers must be registered at the subscription level before deployments or updates can proceed
-
Joe Comeau 40 Reputation points
2026-04-20T19:35:42.48+00:00 Hi Himanshu,
We've verified the DNS.
2.Ensure required providers show Registered (not “NotRegistered” or “Registering”)
How do we know which providers should be registered? what are the required ones?
-
Himanshu Shekhar 5,740 Reputation points Microsoft External Staff Moderator
2026-04-21T01:05:31.8066667+00:00 Joe Comeau Could you please confirm if the upgrade needs to be performed at this time ?
-
Joe Comeau 40 Reputation points
2026-04-21T15:59:20.7133333+00:00 Hi Himanshu,
We are discussing since we are at 23H2, would it be possible to guide us to upgrade to the latest OS instead?
Best,
Andy
-
Himanshu Shekhar 5,740 Reputation points Microsoft External Staff Moderator
2026-04-21T23:21:48.5733333+00:00 Joe Comeau - Could you please share the details asked via private messages
-
Himanshu Shekhar 5,740 Reputation points Microsoft External Staff Moderator
2026-04-27T22:57:11.96+00:00 Joe Comeau
Recommended action:
Could you please verify the following on DNS server 10.0.**:
It is an AD-integrated DNS server, or correctly forwarding requests to one.
It can resolve the domain hci.hli.ubc.ca successfully.
The required A record exists for the domain and points to a valid domain controller.
Once this DNS inconsistency is corrected and both DNS servers are resolving the domain properly, please proceed with resuming the solution update.
Note - please check private messages as well for details
Sign in to comment -