Skip to content

Update functions-networking-options.md #125901

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
wants to merge 1 commit into
base: main
Choose a base branch
from
+2 −2
Open

Update functions-networking-options.md #125901

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
4 changes: 2 additions & 2 deletions articles/azure-functions/functions-networking-options.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -125,8 +125,8 @@ Considerations for the [Elastic Premium](./functions-premium-plan.md), [Dedicate
* The feature is available for Elastic Premium and App Service Premium V2 and Premium V3. It's also available in Standard but only from newer App Service deployments. If you are on an older deployment, you can only use the feature from a Premium V2 App Service plan. If you want to make sure you can use the feature in a Standard App Service plan, create your app in a Premium V3 App Service plan. Those plans are only supported on our newest deployments. You can scale down if you desire after that.
* The feature can't be used by Isolated plan apps that are in an App Service Environment.
* The app and the virtual network must be in the same region.
* The feature requires an unused subnet that's a /28 or larger in an Azure Resource Manager virtual network.
* The integration subnet can be used by only one App Service plan.
* The feature requires a subnet that's a /28 or larger in an Azure Resource Manager virtual network.
Copy link
Contributor

Choose a reason for hiding this comment

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

@rapopescu16 @im-samz - if the subnet is being used by other services (like a private endpoint into, say, service bus or storage) then the virtual network integration would fail. While I understand that the subnet can be shared between multiple app service plans now, it can't also be delegated to other services right? I think this distinction would still be worth calling out. For Flex Consumption in the docs we made this distinction by using two different bullet points:
image

Copy link
Contributor

@im-samz im-samz May 12, 2025 •
edited
Loading

Choose a reason for hiding this comment

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

I addressed this in a separate PR wtih Glenn: https://github.com/MicrosoftDocs/azure-docs-pr/pull/299657/files

Copy link
Contributor

Choose a reason for hiding this comment

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

@im-samz Should we close this PR if it was addressed in the private repo?

Copy link
Contributor

Choose a reason for hiding this comment

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

Hey @v-dirichards, this comment was specifically for Thiago's suggestion. The changes raised in Raluca's PR were not part of that other PR.

* The integration subnet can be used by multiple App Service plans.
* You can have up to two regional virtual network integrations per App Service plan. Multiple apps in the same App Service plan can use the same integration subnet.
* You can't delete a virtual network with an integrated app. Remove the integration before you delete the virtual network.
* You can't change the subscription of an app or a plan while there's an app that's using regional virtual network integration.
Expand Down