I see that Ben Armstrong has posted instructions on how to use Windows Internet Connection Sharing (ICS) to give your Hyper-V virtual machines access to networks via a wireless adapter.

However ICS does not appear to work if the network that your wireless adapter is connected to uses the 192.168.0/24 subnet (as this is used on the internal side of ICS).

If you are in this situation, then instead of using ICS, the inbuilt Routing and Remote Access (RRAS) service can be used instead. The benefit of RRAS is that any arbitrary subnet(s) can be used on the internal interface (and you can have as many as you want).

To install RRAS use the Server Manager to install the Network Policy And Access Role. RRAS now exists as a sub-feature of this role. You can add this role using Server Manager.

Then open the RRAS MMC Administrative console, and use the wizard that runs at first use to choose NAT routing, and then configure your external (WLAN) interface and internal interface (an internal network created by Hyper-V Management MMC).

Edit: You should give the internal adapter an IP address before running the wizard - so that the NAT routing wizard knows what IP addresses your internal LAN is going to be using, and can configure routing appropriately.

It is possible to have the RRAS service provide DHCP addresses to your Hyper-V machines. However since most of these are probably servers (and thus have static addresses), you can configure a static address pool in RRAS.

If you wish to have your Hyper-V machines able to contact your host PC on the internal interface, configure exceptions (or disable) in th Windows Firewall on the individual adapter configured by Hyper-V (this can be done on the Advanced tab in the Windows Firewall control panel on the host).

Edit: If you haven't using RRAS before, then John Paul Cook has an excellent step-by-step guide on configuring this entire configuration (with screenshots) on his blog.