We have a complex set of group policies to map printers to users when they log in from different locations, and we have been using group policy preference item-level targeting features (terminal session with Client TCP/IP address range), but this is not working in the Azure Virtual Desktop "Remote Desktop" client. This was working great when we used Remote Desktop services and the regular Remote Desktop Connection client (msrtc.exe). The AVD client needs to recognize the client IP address of an Azure Virtual Desktop user so we can assign item-level targeting to those clients. For example, when a user logs into AVD from a client in the office, they will get the printers for that office, and when they travel to a branch office, they will get the printers from that branch office, and if they log in from home, they get a completely different set of printers.