Share via

Unable to integrate required subnet

Juhi Saxena 41 Reputation points
2023-11-02T07:13:05.32+00:00

I need to associate the VNET and Function App with a subnet id as it has all the firewall accesses which we require. But I am not able to associate as it is being disabled in the dropdown while choosing to integrate the VNET as shown in the attachment (VNET-Association-Issue-1.png).

We also tried to raise a Support Request for the same but we couldn't raise and got the attached (Support-Request-Error.png) error while raising it.

The plan which it is giving in the error with which the subnet is associated does not exist anymore but still it is showing associated. Can someone please help us with this.

Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
4,678 questions
Azure Virtual Network
Azure Virtual Network
An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
2,311 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. MuthuKumaranMurugaachari-MSFT 22,276 Reputation points
    2023-11-02T13:54:33.13+00:00

    Juhi Saxena Thanks for posting your question in Microsoft Q&A. I assume both Function app and VNET are in the same region (regional VNET integration), otherwise you cannot associate with the subnet.

    Have you already reviewed doc: Subnets and Regional Virtual network integration and validated the conditions? To summarize, you need to use unused/dedicated subnet with a minimum size of /24 and /26 for Windows and Linux plans respectively (/28 or larger in ARM VNET). If the subnet is already associated with any other apps in the same or different plan, then it cannot be used.

    Update:

    We found the subnet was associated with another app service plan that was deleted which caused the issue. Our product team has applied the mitigation in the backend to resolve the issue.

    0 comments