WAC not detect subnet inside vNet when configuring Azure Extended Network. Hi

Taryel Kazimov 5 Reputation points
2024-07-18T07:50:13.12+00:00

Hi

I am trying to setup Azure Extended Network from OnPremise to Azure using this documentation.

Extend your on-premises subnets into Azure using extended network for Azure | Microsoft Learn

I already setup VPN between OnPrem and Azure with VPN Gateway and checked connection.

I created vNet with 3 subnets in Azure 1 for VPN 1 for External Network and 1 for Extended network which overlap with my on Prem subnet 192.168.20.0/24

Windows Server 2022 Azure Edition created on Azure with Hyper-V role VMSwitches and with 2 vNIC connected to External (Main with gateway and 2nd to extended subnet without gateway)

Windows Server 2022 Datacentre deployed to On-premise with 2NIC 1 in routable subnet from which i can ping Azure Appliance and 2nd in my on Prem extended network.

I creaded 3rd server in OnPremise with W2022 and installed latest version of WAC. Logged to azure install Azure Extended Network extension and added my Network Extender onpremise server to WAC.

After setup starts it ask me to select which network to extended and this network is 192.168.20.0/24 in 2nd window i need to choose Subscription in Azure, RG, and vNet. After WAC need to automatically detect my extended subnet inside VNet but it can't detectd it and say that " Warning No subnet(192.168.20.0/24) found in current selected virtual network**"**

So what can be

WAC

vNet

Windows for business | Windows Client for IT Pros | Networking | Network connectivity and file sharing
Windows for business | Windows Server | Devices and deployment | Set up, install, or upgrade
Windows for business | Windows Server | User experience | Other
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Taryel Kazimov 5 Reputation points
    2024-07-20T05:57:15.1166667+00:00
    
    

    st update. WAC can't parse Azure API request. I used fiddler to view http request and can see that subnet is returning inside JSON but WAC can't parse it. MS need to update WAC extension to catch these changes inside Azure. Lost 2 week of my life.Untitled

    1 person found this answer helpful.
    0 comments No comments

Your answer

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