As far as will it directly emulate the Mac's perms no.
Assuming your IP for your Windows VM is in your AD networks subnet whether DHCP or static all you should have to do is renter your AD credentials and you should be all set. As far as joining the Windows VM to the AD you may or may not have issues there, this will depend on your VM software.
This can be a little odd, technically your virtualization software is pretending to be a router in that it takes your internet connection and and creates a separate subnet for it. From which (like a router) instead of using your host machines IP scheme it uses a separate one. It also sets up a DHCP and DNS NOT connected to AD in anyway for the VMs.
Depending upon your VM software you might not be able to establish a connection.
The mainstream options (Hyper-V*, VMWare, and Virtualbox) all support bridged networking and do not hinder the connection in anyway I am aware. This DOES NOT mean that another software wont.
However with NAT it's possible that the software might block ports needed for AD to communicate correctly this could include AD Auth (LDAP), DHCP (IPs), and DNS (Host Resolution), etc.
Note for Hyper-V - It is only supported on Windows 8.0 and above as well as Windows Server 2008 and above.
I would recommend that you use Virtualbox instead of VMWare or Parallels. It can be found here. https://www.virtualbox.org/wiki/Downloads
- It's free
- It works on almost every modern OS there is
- It supports most of the virtual disk formats for every other solution. Examples include (VHD - Hyper-V/VPC, VMDK - VMWare, HDD - Parallels, etc)