Skip to content

Update parameters for logical network creation#4276

Open
kerimhanif wants to merge 1 commit intoMicrosoftDocs:mainfrom
kerimhanif:patch-10
Open

Update parameters for logical network creation#4276
kerimhanif wants to merge 1 commit intoMicrosoftDocs:mainfrom
kerimhanif:patch-10

Conversation

@kerimhanif
Copy link
Copy Markdown
Contributor

Fixed CLI syntax in static logical network example. Added missing space between --no-gateway and --ip-pool-start. Corrected undefined PowerShell variable $fabricResourceID in the example.
Changed the order in the variable list, moved $ipPoolStart to the top

Fixed CLI syntax in static logical network example.
Added missing space between --no-gateway and --ip-pool-start.
Corrected undefined PowerShell variable $fabricResourceID in the example.
@learn-build-service-prod
Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 52567d2:

✅ Validation status: passed

File Status Preview URL Details
azure-local/multi-rack/multi-rack-create-logical-networks.md ✅Succeeded

For more details, please refer to the build report.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the multi-rack “static logical network” documentation example to ensure the provided CLI snippet is syntactically correct and the referenced variables are defined.

Changes:

  • Replaced an unused/incorrect internal network variable with $fabricResourceID in the parameter setup.
  • Fixed the az stack-hci-vm network lnet create example so flags are correctly spaced/continuous (no broken line).
  • Reordered IP pool variables and normalized the “Next steps” list formatting.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

```azurecli
$lnetName = "mylocal-lnet-static"
$internalNetworkName = "<Layer 3InternalNetwork>"
$fabricResourceID = "<Layer 3InternalNetworkID>"
@v-regandowner
Copy link
Copy Markdown
Contributor

@sipastak

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator Bot added the aq-pr-triaged Tracking label for the PR review team label May 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

aq-pr-triaged Tracking label for the PR review team do-not-merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants