Updating Azure Local failed on "Test host intent configuration readiness"

Question

Updating Azure Local failed on "Test host intent configuration readiness"

MB 30

updating our Azure local cluster to to the latest cumulative update 2025.05 v11.2505.1001.22

All validation passes except getting a critical error on "Test host intent configuration readiness"" with no other information. See screenshot. I've run the Azure Environment Checker as well and it passed 100%. We just updated to feature update 11.2504.1001.19 earlier in the day and this update showed up after, had no issues updating that.

User's image

Mounika Reddy Anumandla 6,570 Reputation points Microsoft External Staff Moderator

2025-06-19T10:17:43.1933333+00:00
MB

The error you're seeing — “Test host intent configuration readiness” → Critical error — during the Azure Stack HCI cumulative update (2025.05 v11.2505.1001.22) usually relates to mismatches or inconsistencies between:

The intent metadata stored in Azure

The actual host or cluster configuration (e.g., networking, hardware layout, identity bindings, etc.)

Since your screenshot shows no further information in the right pane and you've confirmed the Azure Environment Checker passes.
Review Event Logs on cluster nodes

Check logs on each node:

Event Viewer → Applications and Services Logs → Microsoft-AzureStack-HCI-Operational

Look for event IDs around the time the error occurred

Verify Network ATC intent health state:

Check current network intents

Get-NetIntent

Ensure all intents match your current configuration (no references to deleted intents).

If the ConfigurationStatus isn't healthy, verify that the VM network adapter name is the same as the network adapter name.https://learn.microsoft.com/en-us/azure/azure-local/upgrade/troubleshoot-upgrade-to-23h2?view=azloc-2504

Run PowerShell Commands: Open PowerShell on your Azure Local machine and execute the following commands to get more details on the readiness check failure:

Get-SolutionUpdate | FT Version,State,HealthCheckResult

This will show you the overall state of the updates. Look for HealthCheckFailed values.

Check Detailed Health Results: You can further investigate by running this command to filter out any specific tests that failed:

$result = Get-SolutionUpdate $result.HealthCheckResult | Where-Object {$_.Status -ne "SUCCESS"} | FL Title,Status,Severity,Description,Remediation

This should give you detailed information on what might be causing the failure.

Remediate Failed Tests: Based on the output from the previous commands, take the necessary actions as per the Remediation field for each failing test. Address any critical issues identified there.

Re-check Readiness: After addressing any issues, you should run the readiness checks again:

Get-SolutionUpdate -Id <some ID> | Start-SolutionUpdate -PrepareOnly

Additional Suggestions:

Ensure that all your nodes are properly configured and integrated, particularly after any recent updates.

Make sure that your Active Directory configuration is correct as per any additional requirements specified in the release notes. Also please refer: https://jtpedersen.com/2025/01/azure-local-azure-update-management-issue-validation-failing/
https://learn.microsoft.com/en-us/azure/azure-local/upgrade/install-solution-upgrade?view=azloc-2504

Please tag me for further queries!

MB 30

Hi Mounika,

The output for
$result = Get-SolutionUpdate

$result.HealthCheckResult | Where-Object {$_.Status -ne "SUCCESS"} | FL Title,Status,Severity,Description,Remediation

Title : Test host intent configuration readiness

Status : FAILURE

Severity : CRITICAL

Description : Test network intent configuration could be possible applied on host 10.181.0.13

Remediation : Please doulbe check your adapters advanced property.

              **Get adapter name: Get-NetAdapter | ft Name**

              **Get-NetAdapterAdvancedProperty -Name <ADAPTERNAME> -RegistryKeyword <Property To Check>**

                         **<Adapter Name>: Name of the adapter, got from the above Get-NetAdapter call**

                         **<Property To Check>: what property to check. We are validating below properties:**

                                         ***NetworkDirectTechnology: check "ValidDisplayValues" in it to see if a specific NetworkDirect technology is supported by the adapter**

                                                                   **Valid value should be the combination of the** following: iWARP, RoCE, RoCEv2

              Sample: Check what NetworkDirect technology is supported by adapter "Ethernet"

                     (Get-NetAdapterAdvancedProperty -Name "Ethernet" -RegistryKeyword "*NetworkDirectTechnology").ValidDisplayValues

Not sure if that means I should be looking at the adapter called "Ethernet". That's the BMC NIC on the nodes. All 4 nodes are showing this error. The thing is we just did a feature update earlier in the day and it went through all the checks fine.

Thanks

Mounika Reddy Anumandla 6,570 Reputation points Microsoft External Staff Moderator

2025-06-19T15:47:08.6633333+00:00
Hi MB,

Thank you for replying back!
The failure is coming from the Host Intent Configuration Readiness Check, specifically:

"Test network intent configuration could be possible applied on host 10.181.0.13" "Please double check your adapter's advanced property."

The remediation suggests:

Get-NetAdapter Get-NetAdapterAdvancedProperty -Name <AdapterName> -RegistryKeyword "*NetworkDirectTechnology"

This indicates that one or more of your physical NICs are missing expected RDMA (Remote Direct Memory Access) configuration values.

Azure Stack HCI relies on intent-based configuration for host networking, especially for Storage Spaces Direct (S2D) and RDMA over SMB Direct. The update readiness engine validates that all participating adapters support compatible NetworkDirect technologies like:

iWARP

RoCE

RoCEv2

If a NIC does not report any of these capabilities, the intent validation fails.

AFAIK, you should not be including the “Ethernet” (BMC NIC) in the host intent.

You mentioned:

"We just did a feature update earlier in the day and it went through all the checks fine."

That makes sense because feature updates don’t always re-validate network intent in the same depth as a solution update (like 2025.05), which includes new intent validation logic or stricter enforcement.

So now, the solution update is picking up that the BMC NIC is included in your network intent, but it doesn’t support RDMA or NetworkDirectTechnology, which causes the check to fail on all nodes.

Please see: https://learn.microsoft.com/en-us/azure/azure-local/upgrade/troubleshoot-upgrade-to-23h2?view=azloc-2504#network-atc-intent-health-state

Hope it helps!

Let me know if you have any further queries!

If the comment is helpful, please click "upvote" to let us know!
MB 30 Reputation points

2025-06-19T16:29:28.5066667+00:00

OK thanks, I will check, but the BMC NIC is not part of any intents (management, compute or storage)
MB 30 Reputation points

2025-06-19T17:35:14.2566667+00:00

Attaching a screenshot of the adapters and ports assigned to the intents. Both don't have the BMC adapter as part of the intent.
Mounika Reddy Anumandla 6,570 Reputation points Microsoft External Staff Moderator

2025-06-20T16:39:36.1433333+00:00

Hi MB,

Looks like an adapter property being misconfigured. Can you provide me the details asked through private message!
Mounika Reddy Anumandla 6,570 Reputation points Microsoft External Staff Moderator

2025-06-27T05:29:09.13+00:00

Hi MB,

Sorry for delayed response! Please run the below command to verify the adapter properties!

Get-NetAdapter Get-NetAdapterAdvancedProperty -Name <AdapterName> -RegistryKeyword "NetworkDirectTechnology" Valid value should be the combination of the folowing: iWARP, RoCE, RoCEv*

Additional ref: https://learn.microsoft.com/en-us/azure/azure-local/concepts/host-network-requirements?view=azloc-2505&source=recommendations#rdma

https://techcommunity.microsoft.com/discussions/azurestack/guidance-on-network-configurations-for-azure-stack-hci-cluster/3879556

1 answer

Your answer

MB 30 Reputation points

2025-06-19T14:13:48.5333333+00:00

Hi Mounika,

The output for
$result = Get-SolutionUpdate

$result.HealthCheckResult | Where-Object {$_.Status -ne "SUCCESS"} | FL Title,Status,Severity,Description,Remediation

Title : Test host intent configuration readiness

Status : FAILURE

Severity : CRITICAL

Description : Test network intent configuration could be possible applied on host 10.181.0.13

Remediation : Please doulbe check your adapters advanced property.

**Get adapter name: Get-NetAdapter | ft Name** **Get-NetAdapterAdvancedProperty -Name <ADAPTERNAME> -RegistryKeyword <Property To Check>** **<Adapter Name>: Name of the adapter, got from the above Get-NetAdapter call** **<Property To Check>: what property to check. We are validating below properties:** ***NetworkDirectTechnology: check "ValidDisplayValues" in it to see if a specific NetworkDirect technology is supported by the adapter** **Valid value should be the combination of the** following: iWARP, RoCE, RoCEv2 Sample: Check what NetworkDirect technology is supported by adapter "Ethernet" (Get-NetAdapterAdvancedProperty -Name "Ethernet" -RegistryKeyword "*NetworkDirectTechnology").ValidDisplayValues

Not sure if that means I should be looking at the adapter called "Ethernet". That's the BMC NIC on the nodes. All 4 nodes are showing this error. The thing is we just did a feature update earlier in the day and it went through all the checks fine.

Thanks
Mounika Reddy Anumandla 6,570 Reputation points Microsoft External Staff Moderator

2025-06-19T15:47:08.6633333+00:00

Hi MB,

Thank you for replying back!
The failure is coming from the Host Intent Configuration Readiness Check, specifically:

"Test network intent configuration could be possible applied on host 10.181.0.13" "Please double check your adapter's advanced property."

The remediation suggests:

Get-NetAdapter Get-NetAdapterAdvancedProperty -Name <AdapterName> -RegistryKeyword "*NetworkDirectTechnology"

This indicates that one or more of your physical NICs are missing expected RDMA (Remote Direct Memory Access) configuration values.

Azure Stack HCI relies on intent-based configuration for host networking, especially for Storage Spaces Direct (S2D) and RDMA over SMB Direct. The update readiness engine validates that all participating adapters support compatible NetworkDirect technologies like:

iWARP

RoCE

RoCEv2

If a NIC does not report any of these capabilities, the intent validation fails.

AFAIK, you should not be including the “Ethernet” (BMC NIC) in the host intent.

You mentioned:

"We just did a feature update earlier in the day and it went through all the checks fine."

That makes sense because feature updates don’t always re-validate network intent in the same depth as a solution update (like 2025.05), which includes new intent validation logic or stricter enforcement.

So now, the solution update is picking up that the BMC NIC is included in your network intent, but it doesn’t support RDMA or NetworkDirectTechnology, which causes the check to fail on all nodes.

Please see: https://learn.microsoft.com/en-us/azure/azure-local/upgrade/troubleshoot-upgrade-to-23h2?view=azloc-2504#network-atc-intent-health-state

Hope it helps!

Let me know if you have any further queries!

If the comment is helpful, please click "upvote" to let us know!
MB 30 Reputation points

2025-06-19T16:29:28.5066667+00:00

OK thanks, I will check, but the BMC NIC is not part of any intents (management, compute or storage)
MB 30 Reputation points

2025-06-19T17:35:14.2566667+00:00

Attaching a screenshot of the adapters and ports assigned to the intents. Both don't have the BMC adapter as part of the intent.
Mounika Reddy Anumandla 6,570 Reputation points Microsoft External Staff Moderator

2025-06-20T16:39:36.1433333+00:00

Hi MB,

Looks like an adapter property being misconfigured. Can you provide me the details asked through private message!
Mounika Reddy Anumandla 6,570 Reputation points Microsoft External Staff Moderator

2025-06-27T05:29:09.13+00:00

Hi MB,

Sorry for delayed response! Please run the below command to verify the adapter properties!

Get-NetAdapter Get-NetAdapterAdvancedProperty -Name <AdapterName> -RegistryKeyword "NetworkDirectTechnology" Valid value should be the combination of the folowing: iWARP, RoCE, RoCEv*

Additional ref: https://learn.microsoft.com/en-us/azure/azure-local/concepts/host-network-requirements?view=azloc-2505&source=recommendations#rdma

https://techcommunity.microsoft.com/discussions/azurestack/guidance-on-network-configurations-for-azure-stack-hci-cluster/3879556

Answer 1

Michael Gauthier 0

Running into the same issue. Only have 4 NICs in the server.

Get-NetAdapter | select Name,Status

Name Status

storage1-s1p2 Up

storage2-s3p2 Up

vManagement(compute_management) Up

compute1-s1p1 Up

compute2-s3p1 Up

All of the adapters are showing RoCE and RoCEv2 support:

(Get-NetAdapterAdvancedProperty -Name "compute1-s1p1" -RegistryKeyword "*NetworkDirectTechnology").ValidDisplayValues

RoCE

RoCEv2

(Get-NetAdapterAdvancedProperty -Name "compute2-s3p1" -RegistryKeyword "*NetworkDirectTechnology").ValidDisplayValues

RoCE

RoCEv2

Did you get this resolved? Not sure what to look at or remediate?

Mounika Reddy Anumandla 6,570 Reputation points Microsoft External Staff Moderator

2025-06-27T05:30:32.4366667+00:00

Michael Gauthier

If you are facing similar issue, can you send the log using https://learn.microsoft.com/en-us/azure/azure-local/manage/collect-logs?view=azloc-2505&tabs=powershell and share with us the output to investigate further!

Share via

Updating Azure Local failed on "Test host intent configuration readiness"

Check current network intents

1 answer

Your answer