Skip to content

Commit 2515c61

Browse files
authored
Merge pull request #275651 from rcdun/acg_update_vnet_subnet_requirements
Clarify that subnets must be for exclusive use
2 parents 6a12b42 + 489e365 commit 2515c61

File tree

1 file changed

+8
-7
lines changed

1 file changed

+8
-7
lines changed

articles/communications-gateway/prepare-for-vnet-injection.md

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -10,19 +10,20 @@ ms.date: 04/26/2024
1010

1111
# Prepare to connect Azure Communications Gateway to your own virtual network (preview)
1212

13-
This article describes the steps required to connect an Azure Communications Gateway to your own virtual network using VNet injection for Azure Communications Gateway (preview). This procedure is required to deploy Azure Communications Gateway into a subnet that you control and is used when connecting your on premises network with ExpressRoute Private Peering or though an Azure VPN Gateway. Azure Communications Gateway has two service regions with their own connectivity, which means that you need to provide virtual networks and subnets in each of these regions.
13+
This article describes the steps required to connect an Azure Communications Gateway to your own virtual network using VNet injection for Azure Communications Gateway (preview). This procedure is required to deploy Azure Communications Gateway into a subnet that you control and is used when connecting your on premises network with ExpressRoute Private Peering or through an Azure VPN Gateway. Azure Communications Gateway has two service regions with their own connectivity, which means that you need to provide virtual networks and subnets in each of these regions.
1414

1515
The following diagram shows an overview of Azure Communications Gateway deployed with VNet injection. The network interfaces on Azure Communications Gateway facing your network are deployed into your subnet, while the network interfaces facing backend communications services remain managed by Microsoft.
1616

1717
:::image type="content" source="media/azure-communications-gateway-vnet-injection.svg" alt-text="Network diagram showing Azure Communications Gateway deployed into two Azure regions. The Azure Communications Gateway resource in each region connects to an Operator virtual network with Operator controlled IPs." lightbox="media/azure-communications-gateway-vnet-injection.svg":::
1818

1919
## Prerequisites
20-
- Your Azure subscription is [enabled for Azure Communications Gateway](prepare-to-deploy.md#get-access-to-azure-communications-gateway-for-your-azure-subscription).
21-
- Your onboarding team is aware that you intend to use your own virtual networks.
22-
- You have an Azure virtual network in each of the Azure regions to be used as the Azure Communications Gateway [service regions](reliability-communications-gateway.md#service-regions). Learn how to create a [virtual network](/azure/virtual-network/manage-virtual-network).
23-
- You have a subnet to be dedicated to Azure Communications Gateway in each Azure virtual network. These subnets must each have at least 16 IP addresses (a /28 IPv4 range or larger). Learn how to create a [subnet](/azure/virtual-network/virtual-network-manage-subnet).
24-
- Your Azure account has the Network Contributor role, or a parent of this role, on the virtual networks.
25-
- Your chosen connectivity solution (for example ExpressRoute) is deployed into your Azure subscription and ready to use.
20+
21+
- Get your Azure subscription [enabled for Azure Communications Gateway](prepare-to-deploy.md#get-access-to-azure-communications-gateway-for-your-azure-subscription).
22+
- Inform your onboarding team that you intend to use your own virtual networks.
23+
- Create an Azure virtual network in each of the Azure regions to be used as the Azure Communications Gateway [service regions](reliability-communications-gateway.md#service-regions). Learn how to create a [virtual network](/azure/virtual-network/manage-virtual-network).
24+
- Create a subnet in each Azure virtual network for Azure Communications Gateway's exclusive use. These subnets must each have at least 16 IP addresses (a /28 IPv4 range or larger). Nothing else must use this subnet. Learn how to create a [subnet](/azure/virtual-network/virtual-network-manage-subnet).
25+
- Ensure that your Azure account has the Network Contributor role, or a parent of this role, on the virtual networks.
26+
- Deploy your chosen connectivity solution (for example ExpressRoute) into your Azure subscription and ensure it's ready for use.
2627

2728
> [!TIP]
2829
> Lab deployments only have one service region, so you only need to set up a single region during this procedure.

0 commit comments

Comments
 (0)