Do not arc enable the nodes for cloud deployed clusters even if they are disconnected from ARC#29074
Merged
vidai-msft merged 3 commits intoAzure:mainfrom Jan 20, 2026
Conversation
…are in disconnected state
| Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR modifies the Azure Stack HCI registration flow to prevent automatic Arc enablement of cluster nodes during repair registration when the cluster was deployed through cloud deployment. The change ensures that for cloud-deployed clusters, Arc enablement is handled by the cloud deployment process rather than being triggered manually during repair operations.
Changes:
- Updated MSI flow logic to detect cloud deployments and skip manual Arc enablement in such cases
- Added appropriate logging for the new cloud deployment skip path
- Updated ChangeLog to document the behavior change
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| src/StackHCI/StackHCI/ChangeLog.md | Documents the new behavior where Arc enablement is skipped for cloud-deployed clusters during repair registration |
| src/StackHCI/StackHCI.Autorest/custom/stackhci.ps1 | Adds cloud deployment detection in Invoke-MSIFlow to conditionally skip Arc enablement, wrapping the existing enablement logic in an else block for non-cloud deployments |
Member
|
/azp run |
Contributor
|
Azure Pipelines successfully started running 3 pipeline(s). |
vidai-msft
requested changes
Jan 19, 2026
bniranjanbhat
approved these changes
Jan 20, 2026
Member
|
/azp run |
Contributor
|
Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command. |
Contributor
|
@Samhitha-Microsoft Please resolve the conflict. |
Contributor
Author
Done. |
Member
|
/azp run |
Contributor
|
Azure Pipelines successfully started running 3 pipeline(s). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
In the current registration flow, if the nodes are disconnected from Arc, during repair registration, the nodes will be arc enabled again. But, in case of cloud deployment Arc enablement should not be done even if the machine is disconnected form Arc.
Mandatory Checklist
Please choose the target release of Azure PowerShell. (⚠️ Target release is a different concept from API readiness. Please click below links for details.)
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.mdand reviewed the following information:ChangeLog.mdfile(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.## Upcoming Releaseheader in the past tense.ChangeLog.mdif no new release is required, such as fixing test case only.