Merge pull request #290925 from dlepow/prefix

[APIM] addressPrefix subnet requirement

Author: denrea

articles/api-management/inject-vnet-v2.md

@@ -68,9 +68,11 @@ The subnet needs to be delegated to the **Microsoft.Web/hostingEnvironments** se
 
 For more information about configuring subnet delegation, see [Add or remove a subnet delegation](../virtual-network/manage-subnet-delegation.md).
 
+[!INCLUDE [api-management-virtual-network-address-prefix](../../includes/api-management-virtual-network-address-prefix.md)]
+
 ### Permissions
 
-You must have at least the following role-based access control permissions on the subnet or at a higher level to configure virtual network integration:
+You must have at least the following role-based access control permissions on the subnet or at a higher level to configure virtual network injection:
 
 | Action | Description |
 |-|-|
@@ -86,13 +88,11 @@ When you [create](get-started-create-service-instance.md) a Premium v2 instance
 
 1. In the **Create API Management service** wizard, select the **Networking** tab.
 1. In **Connectivity type**, select **Virtual network**.
-1. In **Type**, select **Internal**. 
-1. In **Configure virtual networks**, select the virtual network and the delegated subnet that you want to integrate. 
-
-    Optionally, provide a public IP address resource if you want to own and control an IP address that's used only for outbound connection to the internet.
+1. In **Type**, select **Injection**. 
+1. In **Configure virtual networks**, select the virtual network and the delegated subnet that you want to inject. 
 1. Complete the wizard to create the API Management instance.
 
-## DNS settings for integration with private IP address
+## DNS settings for access to private IP address
 
 When a Premium v2 API Management instance is injected in a virtual network, you have to manage your own DNS to enable inbound access to API Management. 
 

includes/api-management-virtual-network-address-prefix.md

@@ -0,0 +1,31 @@
+---
+author: dlepow
+ms.service: azure-api-management
+ms.topic: include
+ms.date: 11/21/2024
+ms.author: danlep
+---
+
+### addressPrefix property
+
+Virtual network injection in the Premium v2 tier requires that the `addressPrefix` subnet property is set to a valid CIDR block. 
+
+If you configure the subnet using the Azure portal, the subnet sets an `addressPrefixes` (plural) property consisting of a list of address prefixes. However, API Management requires a single CIDR block as the value of the `addressPrefix` property. 
+
+To create or update a subnet with `addressPrefix`, use a tool such as Azure PowerShell, an Azure Resource Manager template, or the [REST API](/rest/api/virtualnetwork/subnets/create-or-update). For example, update a subnet using the [Set-AzVirtualNetworkSubnetConfig](/powershell/module/az.network/set-azvirtualnetworksubnetconfig) Azure PowerShell cmdlet:
+
+```powershell
+# Set values for the variables that are appropriate for your environment.
+
+$resourceGroupName = "MyResourceGroup"
+$virtualNetworkName = "MyVirtualNetwork"
+$subnetName = "ApimSubnet"
+$addressPrefix = "10.0.3.0/24"
+
+
+$virtualNetwork = Get-AzVirtualNetwork -Name $virtualNetworkName -ResourceGroupName $resourceGroupName
+
+Set-AzVirtualNetworkSubnetConfig -Name $subnetName -VirtualNetwork $virtualNetwork -AddressPrefix $addressPrefix
+
+$virtualNetwork | Set-AzVirtualNetwork
+```