Skip to content

Commit bcaaea7

Browse files
authored
Update - Update deployment (external VNET) (#15391)
Update deployment (external VNET) -- Location parameter is creating an error The location parameter was creating an issue when I tried to integrate my APIM with Internal Vnet> I had the following error: New-AzApiManagementVirtualNetwork: A parameter cannot be foundthat matches parameter name 'Location'. However, removing the -Location parameter worked for me.
1 parent 3f3ef0a commit bcaaea7

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/ApiManagement/ApiManagement/help/Set-AzApiManagement.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ This example gets an Api Management instance, scales it to five premium units an
3636

3737
### Example 2: Update deployment (external VNET)
3838
```powershell
39-
PS C:\> $virtualNetwork = New-AzApiManagementVirtualNetwork -Location "East US" -SubnetResourceId "/subscriptions/a8ff56dc-3bc7-4174-a1e8-3726ab15d0e2/resourceGroups/Api-Default-WestUS/providers/Microsoft.Network/virtualNetworks/dfVirtualNetwork/subnets/backendSubnet"
39+
PS C:\> $virtualNetwork = New-AzApiManagementVirtualNetwork -SubnetResourceId "/subscriptions/a8ff56dc-3bc7-4174-a1e8-3726ab15d0e2/resourceGroups/Api-Default-WestUS/providers/Microsoft.Network/virtualNetworks/dfVirtualNetwork/subnets/backendSubnet"
4040
PS C:\> $apim = Get-AzApiManagement -ResourceGroupName "ContosoGroup" -Name "ContosoApi"
4141
PS C:\> $apim.VpnType = "External"
4242
PS C:\> $apim.VirtualNetwork = $virtualNetwork

0 commit comments

Comments
 (0)