Skip to content

Clarify that publicNetworkAccess is not applicable for APIM Premium V2 VNet-injected instances #128611

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
Shikha Sinha (shksin) wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Clarify that publicNetworkAccess is not applicable for APIM Premium V2 VNet-injected instances #128611

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
3 changes: 3 additions & 0 deletions articles/api-management/virtual-network-concepts.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,6 +71,9 @@ This configuration is recommended for scenarios where you want to isolate both t

:::image type="content" source="./media/inject-vnet-v2/vnet-injection.png" alt-text="Diagram of injecting an API Management instance in a virtual network to isolate inbound and outbound traffic." :::

> [!NOTE]
> When using VNet injection (Internal mode), the `publicNetworkAccess` property is not applicable. The network perimeter is controlled by the customer through NSG rules and VNet routing. Setting `publicNetworkAccess` to either `Enabled` or `Disabled` on a VNet-injected instance has no effect on traffic behaviour.

@PatAltimore Pat Altimore (PatAltimore) Jul 22, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
> When using VNet injection (Internal mode), the `publicNetworkAccess` property is not applicable. The network perimeter is controlled by the customer through NSG rules and VNet routing. Setting `publicNetworkAccess` to either `Enabled` or `Disabled` on a VNet-injected instance has no effect on traffic behaviour.
> When using VNet injection (Internal mode), the `publicNetworkAccess` property is not applicable. The network perimeter is controlled using NSG rules and VNet routing. Setting `publicNetworkAccess` to either `Enabled` or `Disabled` on a VNet-injected instance has no effect on traffic behavior.


For more information, see [Inject a Premium v2 instance into a virtual network](inject-vnet-v2.md).

## Virtual network integration (v2 tiers)
Expand Down