Merge pull request #20 from riperez123/riperez123-patch-27

Update article date and support ticket scenarios

Author: riperez123

articles/azure-vmware/architecture-stretched-clusters.md

@@ -3,7 +3,7 @@ title: Architecture - Design considerations for vSAN stretched clusters
 description: Learn about how to use stretched clusters for Azure VMware Solution.
 ms.topic: concept-article
 ms.service: azure-vmware
-ms.date: 12/24/2024
+ms.date: 1/8/2026
 ms.custom: references_regions, engagement-fy24
 # Customer intent: "As a cloud architect, I want to design a vSAN stretched cluster for Azure VMware Solution, so that I can enhance application availability and ensure resilience against Availability Zone failures while managing my infrastructure efficiently."
 ---
@@ -116,7 +116,10 @@ No. A stretched cluster is created between two availability zones, while the thi
     - NSX Edge Scale-OUT to add additional NSX Edges is not supported at this time.
 - Open a [support ticket](https://rc.portal.azure.com/#create/Microsoft.Support) from the Azure portal for the following scenarios (be sure to select **Stretched Clusters** as a **Problem Type**):
     - Connect a private cloud to a stretched cluster private cloud.
-    - Connect two stretched cluster private clouds in a single region.
+    - Connect two stretched cluster private clouds.
+ 
+>[!NOTE]
+>Azure VMware Solution interconnect between stretched cluster private clouds is supported only when both stretched clusters are either hosted within the same pod set or have no common pod between them. It is not supported if the private cloud share only one common pod.
 
 ### What kind of latencies should I expect between the availability zones (AZs)?