From daf8419346c4b52e13813bc1dc2ced552fd284c1 Mon Sep 17 00:00:00 2001
From: Larissa Fortuna <56982181+lkfortuna@users.noreply.github.com>
Date: Wed, 5 Jun 2024 09:32:07 -0700
Subject: [PATCH] Update azure-vnet-supported-regions.md (#50993)

Co-authored-by: Joe Clark <31087804+jc-clark@users.noreply.github.com>
---
 .../reusables/actions/azure-vnet-supported-regions.md | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/data/reusables/actions/azure-vnet-supported-regions.md b/data/reusables/actions/azure-vnet-supported-regions.md
index cf13ff07ff..a4b1b52849 100644
--- a/data/reusables/actions/azure-vnet-supported-regions.md
+++ b/data/reusables/actions/azure-vnet-supported-regions.md
@@ -27,4 +27,15 @@ Azure private networking supports GPU runners in the following regions.
 - `NorthCentralUs`
 - `SouthCentralUs`
 
+Azure private networking supports arm64 runners in the following regions.
+
+- `EastUs`
+- `EastUs2`
+- `WestUs2`
+- `NorthCentralUs`
+- `SouthCentralUs`
+
+> [!NOTE]
+> GPU and arm64 runners are currently in beta and subject to change.
+
 If your desired region is not supported, please submit a request for new region availability in [this GitHub form](https://resources.github.com/private-networking-for-github-hosted-runners-with-azure-virtual-networks/). You may also use global virtual network peering to connect virtual networks across Azure regions. For more information, see [Virtual network peering](https://learn.microsoft.com/en-us/azure/virtual-network/virtual-network-peering-overview) in the Azure documentation.