Fixing "No subnet found in current selected virtual network" when deploying VXLAN in Azure TLDR – Virtual Networks deployed via the Azure Portal now include the “addressPrefixes” property rather than “addressPrefix”. The VXLAN extension in Windows Admin Center does not use this value and therefore fails to identify the subnet you wish to VXLAN with.

Fixing "No subnet found in current selected virtual network" when deploying VXLAN in Azure.

A simple workaround to set the "addressPrefix" attribute on a subnet and resolve Windows Admin Center VXLAN extension error.

zurl.co/Cy8BO

We’re heading to the Farnborough Business Expo next week, and we can’t wait to meet local businesses ready to upgrade their IT operations. 📈


Pop by our stand for a chat about how we can protect what you've worked so hard to build.🔨

@B2BExpos

@iasme1.bsky.social have announced, on social media, that last year, the 200,000th Cyber Essentials certification had been issued. This marks a significant milestone within the scheme and shows the positive uptake from UK based businesses.

#bzbIT #CyberEssentials #CyberSecurity

🚀 14 Days to Go! Farnborough Business Expo 🚀

It’s always great to connect with others, and we can’t wait to share what bzb IT is up to. Join our team at The Village Hotel on Stand 38.

#bzbIT #Cybersecurity #ITSupport #Exhibiting #B2BExpo