Skip to content

Clarify publicNetworkAccess property effects on APIM Premium V2 VNet-injected instance #128610

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
shksin wants to merge 1 commit into
base: main
Choose a base branch
from
+1 −0
Open

Clarify publicNetworkAccess property effects on APIM Premium V2 VNet-injected instance #128610

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions articles/api-management/inject-vnet-v2.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,7 @@ If you want to enable *public* inbound access to an API Management instance in t
> * Virtual network injection described in this article is available only for API Management instances in the Premium v2 tier. For networking options in the different tiers, see [Use a virtual network with Azure API Management](virtual-network-concepts.md).
> * Currently, you can inject a Premium v2 instance into a virtual network only when the instance is **created**. You can't inject an existing Premium v2 instance into a virtual network. However, you can update the subnet settings for injection after the instance is created.
> * Currently, you can't switch between virtual network injection and virtual network integration for a Premium v2 instance.
> * The *publicNetworkAccess* property has no effect on API Management instances deployed with virtual network injection. With Internal VNet injection, the gateway endpoint is assigned a private IP address only and has no public IP. Network access is governed entirely by your NSG rules and VNet routing — not by the *publicNetworkAccess* property. The *publicNetworkAccess* property is only relevant for instances that use inbound private endpoints without VNet injection, where a public IP exists and needs to be explicitly disabled. See [Connect privately to API Management using an inbound private endpoint](https://learn.microsoft.com/en-us/azure/api-management/private-endpoint).
Comment thread
shksin marked this conversation as resolved.

## Prerequisites

Expand Down