Removed stretched cluster requirements

[ManikaDhiman]

No description provided.

[prmerger-automator]

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

[learn-build-service-prod]

Learn Build status updates of commit a473f8d:

✅ Validation status: passed

File	Status	Preview URL	Details
azure-local/concepts/host-network-requirements.md	✅Succeeded
azure-local/concepts/media/host-network-requirements/stretched-cluster.png	✅Succeeded	n/a (file deleted or renamed)
azure-local/concepts/network-atc-overview.md	✅Succeeded

For more details, please refer to the build report.

[prmerger-automator]

PRMerger Results

Issue	Description
File Change Percent	This PR contains file(s) with more than 30% file change.

[Copilot]

Pull request overview

This PR removes all references to stretched cluster functionality from the Azure Local networking documentation and replaces it with rack aware clustering content.

Key Changes

• Removed stretched cluster support feature from Network ATC capabilities
• Removed storage replica references from management traffic definitions
• Replaced the entire stretched clusters section with a new rack aware clustering section that links to detailed documentation

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.

File	Description
azure-local/concepts/network-atc-overview.md	Updated date and removed stretched S2D cluster support feature description
azure-local/concepts/host-network-requirements.md	Updated date, removed storage replica from management traffic definition, removed storage replica note, replaced stretched clusters section with rack aware clustering section
azure-local/concepts/media/host-network-requirements/stretched-cluster.png	Media file (no longer referenced after stretched cluster content removal)

---

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

[v-regandowner]

@alkohli

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