Bug: Azure Local / Azure Arc Onboarding Stuck – Private Link Scope Network Error

Open

#184 opened on Oct 3, 2025 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language: PowerShell
Stars: 78
Forks: 60
Avg merge: 1d 6h
Merged PRs (30d): 5

Description

> **IMPORTANT**: Do not share any personal data in the bug report. This repository is a public forum and this report will also be public.

**Bug description**
I am trying to onboard Azure Local on Azure Arc. The onboarding process gets stuck with the following error message:
```
No indication of Private Link Scope but found private endpoint agentserviceapi.guestconfiguration.azure.com: *.*.*.*
It appears that the process is expecting a Private Link Scope, but the existing scope is deployed in another subscription. This prevents the onboarding from completing.

INFO AZCM0026: Network Error
```
**Repro steps**
Steps to reproduce the behavior:
Start onboarding Azure Local / Azure Stack HCI to Azure Arc.

Follow the onboarding steps until the process checks for Private Link Scope.

Observe that it fails with the above network error.

**Expected behavior**
The onboarding should not ask for a Private Link Scope if the scope is in a different subscription. The process should either:

Allow cross-subscription scopes, or

Skip the Private Link requirement when no scope exists in the current subscription.

**Environment (please complete the following information):**

Agent Version : 1.55.03132.2414
Agent Logfile : C:\ProgramData\AzureConnectedMachineAgent\Log\himds.log
Agent Status : Disconnected
Agent Last Heartbeat :
Agent Error Code :
Agent Error Details :
Agent Error Timestamp :
Using HTTPS Proxy :
Proxy Bypass List :
Upstream Proxy :
Gateway URL :
Cloud Provider : AzSHCI
Cloud Metadata
Manufacturer : HPE
Model : ProLiant DL380 Gen10 Plus

**Screenshots**

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Research direction

Reproduce Azure Local / Azure Arc onboarding through the Private Link Scope check and inspect C:\ProgramData\AzureConnectedMachineAgent\Log\himds.log for the AZCM0026 failure. Determine whether a scope in another subscription is supported or should be skipped; done means onboarding completes without this network error.

Written by the indexing model from the issue text.

Assessment

Tech stack: azure
Domain: cloud, infrastructure
Issue type: Bug
Difficulty: 4/5
Estimated time: 3-5 days
Activity status: Stale
Clarity: Mostly clear
Newbie friendliness: 35/100