Unable to attach Subnet to Function App

Ritesh Ranjan 20 Reputation points
2026-07-07T13:21:10.0133333+00:00

I have subnet created which is getting attached to Storage account under networking, but at function app level its showing not available for integration

User's image

Azure Functions
Azure Functions

An Azure service that provides an event-driven serverless compute platform.

0 comments No comments

Answer accepted by question author
Pravallika KV 18,850 Reputation points Microsoft External Staff Moderator
2026-07-07T13:24:18.8866667+00:00

Hi @Ritesh Ranjan ,

Thanks for reaching out to Microsoft Q&A.

For Azure Functions VNet integration, the key requirement is that the subnet must be delegated to the right service and meet constraints for Functions networking.

For Functions VNet integration (including Flex Consumption), you must:

  1. Register the Microsoft.App resource provider in your subscription.
  2. Delegate the subnet to Microsoft.App/environments.

Also, the documentation calls out that the subnet you choose can’t already be used for other purposes (for example, being used with private endpoints / service endpoints, or being delegated to another hosting plan/service). If the subnet isn’t properly delegated (or is delegated in an incompatible way), the portal won’t list it as available for Function App integration.

Your screenshot specifically mentions delegation size constraint. In Flex Consumption, subnets used for VNet integration are used by a pool of network gateways, and there are sizing guidelines (to ensure the gateway pool has enough IPs). For example:

  • A /27 subnet (27 usable IPs) is typically sufficient for a single app (IP multiplexing)
  • For multiple apps or higher-scale workloads, a /26 is recommended
  • Very small subnets (significantly smaller than /27) can cause gateway creation problems and may not produce an obvious explicit error message.

In the Function App (or Flex Consumption plan) workflow, make sure the subnet meets all of the following:

  • Subnet is delegated to Microsoft.App/environments
    • If you associate the subnet via the portal/CLI during vNet integration setup, the required delegation is typically added automatically.
  • Subnet isn’t already used/delegated for something else
    • If it’s used with other features (like private endpoints/service endpoints) or delegated elsewhere, Functions integration may not be allowed.
  • Subnet is large enough
    • If you’re using Flex Consumption, ensure the subnet is at least /27, and consider /26 if multiple apps share the subnet.

Hope this helps!


If the resolution was helpful, kindly take a moment to click on User's imageand click on Yes for was this answer helpful. And, if you have any further query do let us know.

Was this answer helpful?

1 person found this answer helpful.
0 comments No comments

0 additional answers

Sort by: Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.