Skip to content

Update parameters for logical network creation#4276

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

Update parameters for logical network creation#4276
kerimhanif wants to merge 1 commit into
MicrosoftDocs: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.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

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>"

@vary1646 vary1646 Jun 25, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@ronmiab I like the change AI is recommending here; however, the ARM ID shape is not quite right in the example. Can you change it to say this instead for the $fabricResourceID example?

"/subscriptions//resourceGroups/mylocal-rg/providers/Microsoft.ManagedNetworkFabric/l3IsolationDomains/<Layer 3 Isolation Domain> /internalNetworks/"

I am unable to edit this fork. Don't seem to have permissions.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@sipastak FYR as you are reviewer on this.

@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
@github-actions

Copy link
Copy Markdown

This pull request has been inactive for 7 days.
If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions.
If this PR is inactive for 7 more days, it will be closed automatically. Thank you!

@prmerger-automator

Copy link
Copy Markdown
Contributor

@kerimhanif : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@prmerger-automator

Copy link
Copy Markdown
Contributor

@kerimhanif : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@github-actions github-actions Bot removed the inactive label Jun 19, 2026

@vary1646 vary1646 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Added some minor review comments.

```azurecli
az stack-hci-vm network lnet create --subscription $subscription --resource-group $resource_group --custom-location $customLocationID --location $location --name $lnetName --ip-allocation-method "Static" --address-prefixes $addressPrefixes --no-gateway
--ip-pool-start $ipPoolStart --ip-pool-end $ipPoolEnd --ip-pool-type "vm" --dns-servers $dnsServers --fabric-network-configuration-id $fabricResourceID --vlan $vlan
az stack-hci-vm network lnet create --subscription $subscription --resource-group $resource_group --custom-location $customLocationID --location $location --name $lnetName --ip-allocation-method "Static" --address-prefixes $addressPrefixes --no-gateway --ip-pool-start $ipPoolStart --ip-pool-end $ipPoolEnd --ip-pool-type "vm" --dns-servers $dnsServers --fabric-network-configuration-id $fabricResourceID --vlan $vlan

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@kerimhanif thanks for making the tweak to add the space between the parameters. Apart from that, I notice in this PR fork the gateway input is given as --no-gateway whereas in public docs on what is live it is like below in the link here: https://learn.microsoft.com/en-us/azure/azure-local/multi-rack/multi-rack-create-logical-networks?view=azloc-2606

--gateway $gateway

I'd leave it as it the same way as it is on the live doc.

@ronmiab FYI

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@sipastak FYR as you are reviewer on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants