Share via

Azure Local Cluster Validation failing at Evaluate interface ValidateArcIntegration step

Lavanya Roy 66 Reputation points
2025-06-03T21:12:06.4533333+00:00

Hi,

I have a two-node azure local cluster but I am running into validation issues with it - This is the exact error message -

Type 'ValidateArcIntegration' of Role 'EnvironmentValidator' raised an exception: { "ExceptionType": "text", "ErrorMessage": "The provided account MSI@50342 does not have access to subscription ID "xxx-xxx-xxx-xxx". Please try logging in with different credentials or a different subscription ID. If a subscription is not specified, please check the configs by Get-AzConfig.", "ExceptionStackTrace": "at Invoke-AzStackHciArcIntegrationValidation, C:\Program Files\WindowsPowerShell\Modules\AzStackHci.EnvironmentChecker\AzStackHciArcIntegration\AzStackHci.ArcIntegration.psm1: line 166\r\nat Test-AzStackHciArcIntegration, C:\Program Files\WindowsPowerShell\Modules\AzStackHci.EnvironmentChecker\AzStackHciArcIntegration\AzStackHciArcIntegration.psm1: line 136\r\nat \u003cScriptBlock\u003e, \u003cNo file\u003e: line 1\r\nat RunSingleValidator, C:\NugetStore\AzStackHci.EnvironmentChecker.Deploy.10.2505.0.2008\content\Classes\EnvironmentValidator\EnvironmentValidator.psm1: line 878\r\nat ValidateArcIntegration, C:\NugetStore\AzStackHci.EnvironmentChecker.Deploy.10.2505.0.2008\content\Classes\EnvironmentValidator\EnvironmentValidator.psm1: line 572\r\nat \u003cScriptBlock\u003e, C:\CloudDeployment\ECEngine\InvokeInterfaceInternal.psm1: line 157\r\nat Invoke-EceInterfaceInternal, C:\CloudDeployment\ECEngine\InvokeInterfaceInternal.psm1: line 152\r\nat \u003cScriptBlock\u003e, \u003cNo file\u003e: line 50" } at RunSingleValidator, C:\NugetStore\AzStackHci.EnvironmentChecker.Deploy.10.2505.0.2008\content\Classes\EnvironmentValidator\EnvironmentValidator.psm1: line 898 at ValidateArcIntegration, C:\NugetStore\AzStackHci.EnvironmentChecker.Deploy.10.2505.0.2008\content\Classes\EnvironmentValidator\EnvironmentValidator.psm1: line 572 at <ScriptBlock>, C:\CloudDeployment\ECEngine\InvokeInterfaceInternal.psm1: line 157 at Invoke-EceInterfaceInternal, C:\CloudDeployment\ECEngine\InvokeInterfaceInternal.psm1: line 152 at <ScriptBlock>, <No file>: line 50

It fails on The evaluate interface Validate Arc integration step.

Any idea what that MSI@50342 is? cannot find it under managed identities. For now I have given the Cluster MI and the Node MIs access to the subscription but still failing.

Any help would be appreciated!

Azure Local

2 answers

Sort by: Most helpful
  1. Pieter Teeling 30 Reputation points
    2025-06-13T18:48:37.5466667+00:00

    The issue is the version of the az.accounts powershell module. If you're running anything but 4.0.2, you'll run into this scenario.
    Start by checking the version of the module (Get-InstalledModule -Name Az.Accounts) and see if you're running 4.0.2 or anything else.

    If you have 4.0.2 and other versions, delete the rest (without notification)
    Get-InstalledModule -Name Az.Accounts -AllVersions -ErrorAction SilentlyContinue | Where-Object { $.Version -ne '4.0.2' } | ForEach-Object { Uninstall-Module -Name $.Name -RequiredVersion $_.Version -Force -ErrorAction SilentlyContinue }.

    If 4.0.2 is missing:
    Install-Module -Name Az.Accounts -RequiredVersion "4.0.2" -Force -AllowClobber -SkipPublisherCheck

    Do this on all your nodes/machines.

    Doing this will make the Azure Stack HCI Arc Integration step during the cluster validation of Azure Local continue without the errors you've seen before.

    Was this answer helpful?

    3 people found this answer helpful.

  2. Mark Beaupre 0 Reputation points
    2026-06-13T02:46:51.6433333+00:00

    We just hit this same issue this evening.

    However, just removing the version 5.5.0 of the Az.Accounts module and installing version 4.0.2 on the seed node will not work. If you leave the version of 10.0.0 Az.Resources module, you will get an error from the Azure Portal during verification steps that you need to run version 5.5.0 of the Az.Accounts module.

    What we did under the guidance of Azure Support was to remove all versions of the Az.Accounts and Az.Resources modules from all nodes in the cluster. Then we installed version 4.0.2 of the Az.Accounts module and version 7.8.0 of the Az.Resources module on all nodes in the cluster. Verification was successful after performing these actions.

    Was this answer helpful?

    0 comments No comments

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.