diff --git a/data/reusables/actions/azure-vnet-supported-regions.md b/data/reusables/actions/azure-vnet-supported-regions.md index 460e529680..cf13ff07ff 100644 --- a/data/reusables/actions/azure-vnet-supported-regions.md +++ b/data/reusables/actions/azure-vnet-supported-regions.md @@ -1,16 +1,24 @@ The {% data variables.product.prodname_actions %} service supports a subset of all the regions that Azure provides. To facilitate communication between the {% data variables.product.prodname_actions %} service and your subnet, your subnet must be in one of the following supported regions. -- `EastUs` -- `EastUs2` -- `WestUs2` -- `AustraliaEast` -- `CentralUs` -- `FranceCentral` -- `NorthEurope` -- `NorwayEast` -- `SoutheastAsia` -- `SwitzerlandNorth` -- `UkSouth` + Azure private networking supports GPU runners in the following regions. @@ -19,4 +27,4 @@ Azure private networking supports GPU runners in the following regions. - `NorthCentralUs` - `SouthCentralUs` -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. +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.