Update V-net connectivity explanation for AD FS

[tom-maher]

Clarified the V-net to V-net connectivity requirements for AD FS deployment, specifying the communication method between federation servers and WAP servers - https://learn.microsoft.com/en-us/windows-server/identity/ad-fs/deployment/best-practices-securing-ad-fs#communication-between-federation-servers

[prmerger-automator]

@tom-maher : 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 ddbc11e:

✅ Validation status: passed

File	Status	Preview URL	Details
WindowsServerDocs/identity/ad-fs/deployment/active-directory-adfs-in-azure-with-azure-traffic-manager.md	✅Succeeded

For more details, please refer to the build report.

[Copilot]

Pull Request Overview

This PR updates the documentation for AD FS deployment in Azure to clarify V-net to V-net connectivity requirements. The change replaces the previous statement that no connectivity between virtual networks is needed with specific communication requirements for federation servers and WAP servers.

• Clarified communication requirements between federation servers and WAP servers
• Specified HTTP port 80 usage for configuration synchronization
• Updated guidance on V-net connectivity for AD FS deployments

---

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

[Copilot]

The updated explanation is incomplete and potentially misleading. It only mentions HTTP port 80 but doesn't address whether V-net to V-net connectivity is actually required or not, which was the key point of the original text. Consider clarifying whether connectivity between virtual networks is needed and under what circumstances.

Suggested change

* **V-net to V-net connectivity between two regions:** Federation servers on an AD FS farm communicate with other servers in the farm and the Web Application Proxy (WAP) servers via HTTP port 80 for configuration synchronization.

* **V-net to V-net connectivity between two regions:** V-net to V-net connectivity may be required if your AD FS farm spans multiple regions and federation servers or Web Application Proxy (WAP) servers in different regions need to communicate for configuration synchronization (typically via HTTP port 80). If each region is deployed as a fully self-contained environment with its own domain controllers and AD FS farm, V-net to V-net connectivity may not be necessary. Carefully assess your deployment topology to determine whether cross-region connectivity is needed for your scenario.

[v-dirichards]

@robinharwood, @Xelu86
Can you review the proposed changes?

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team
#assign: @robinharwood, @Xelu86