Update Edge Scale-OUT recommendation details

[kgbhat]

Clarified Edge Scale-OUT limitations for Azure VMware Solution Stretched Cluster. https://portal.microsofticm.com/imp/v5/incidents/details/682699004/summary

[prmerger-automator]

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

[learn-build-service-prod]

Learn Build status updates of commit afa63ca:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/azure-vmware/azure-vmware-solution-nsx-scale-and-performance-recommendations-for-vmware-hcx.md	✅Succeeded

For more details, please refer to the build report.

[Copilot]

Pull Request Overview

This PR clarifies documentation limitations for Edge Scale-OUT functionality in Azure VMware Solution by adding an important restriction notice. The update addresses a specific customer inquiry about Edge Scale-OUT support in stretched cluster configurations.

• Added clarification that Edge Scale-OUT is not supported on Azure VMware Solution Stretched Cluster private cloud

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

The limitation notice should be separated from the main description with proper spacing or formatting for better readability. Consider adding a line break or using a separate sentence.

Suggested change

	3. Edge Scale-OUT: If customer has large number of Hosts in the SDDC and workloads, NSX Edge Scale-OUT (from two Edges to four Edges) could be an option to add additional NSX Edge data path resources.Edge Scale-out is currently not supported on Azure VMware Solution Stretched Cluster private cloud.
	3. Edge Scale-OUT: If customer has large number of Hosts in the SDDC and workloads, NSX Edge Scale-OUT (from two Edges to four Edges) could be an option to add additional NSX Edge data path resources.
	**Limitation:** Edge Scale-out is currently not supported on Azure VMware Solution Stretched Cluster private cloud.

[ttorble]

@kgbhat - did you intend to open this PR in the private repo? It looks like you have access to the private repo, and if so, you should use that for content updates. I'll leave this PR open in case @jjaygbay1 wants to review it here. If you decide to open a new PR in the private repo, please close this PR. Thanks.

@jjaygbay1

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