'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Handle Shared IP Addresses in Azure Virtual Desktop Pooled Session Hosts
Question details
An administrator wants to assign separate IP addresses to individual users who are sharing a single Azure Virtual Desktop pooled session host.
- Product
- Azure Virtual Desktop
- Device & OS
- not provided
- Scenario
- Configuring network identity and IP assignments for a pooled session host environment to avoid shared IP addresses among multiple users.
- Observed behavior
- Currently, five users sharing one pooled session host all appear to have the exact same IP address because they share the host's network identity.
Verify your current Azure Virtual Desktop host pool configuration in the Azure portal and ensure you have sufficient administrative permissions to review networking topologies.
Understand Azure Virtual Desktop IP Assignment Limitations and Seek Architectural Guidance
Because pooled session hosts inherently share a single network identity, consult Microsoft Learn for advanced architectural workarounds.
In an Azure Virtual Desktop (AVD) pooled environment, multiple users log into the same virtual machine (session host). Because they share the underlying operating system, they inherently share the VM's network interface (NIC) and its assigned IP address.
Assigning individual IP addresses per user on a shared host is not a native feature of standard Windows 10/11 multi-session networking. To achieve traffic separation without moving users to personal desktops, specialized third-party routing or Network Virtual Appliance (NVA) solutions may be required.
Log in to the Azure portal, navigate to Azure Virtual Desktop, and select 'Host pools'. Confirm that your setup is designated as 'Pooled' rather than 'Personal'.
Navigate to the official Microsoft Learn Azure Q&A forum. Post a detailed query about your specific networking requirements so Azure specialists can recommend appropriate architecture or third-party solutions.
If dedicated IP addresses are a strict compliance requirement, evaluate whether moving specific users to Personal (dedicated) session hosts is a viable and cost-effective workaround for your organization.
Enhance Your Virtual Desktop Experience with WPS Office
While configuring your Azure Virtual Desktop infrastructure, ensure your users have access to a lightweight, highly compatible office suite. WPS Office is a powerful, free alternative to Microsoft Office that runs smoothly in virtualized and pooled environments.
- 1. Download the Enterprise Installer: Obtain the lightweight WPS Office installer suitable for multi-user deployment from the official website.
- 2. Deploy to Session Hosts: Install the application across your Azure Virtual Desktop pooled session hosts using your preferred endpoint management tool.
- 3. Configure Default Apps: Use Group Policy or profile management to set WPS Office as the default application for user documents.
Frequently Asked Questions
Why do multiple users in a pooled host share the same IP address?
Users in a pooled host share the same underlying virtual machine and its operating system. Consequently, all outbound network traffic from that VM is routed through the VM's single primary network interface card (NIC) and its assigned IP address.
Can I use Remote Desktop IP Virtualization with AVD Windows 10 multi-session?
Remote Desktop IP Virtualization is traditionally a feature of Windows Server Remote Desktop Services (RDS). It is not natively supported or documented for Windows 10 or Windows 11 Enterprise multi-session deployments.
What is the easiest way to give an AVD user a dedicated IP address?
The most straightforward and fully supported method is to assign the user a 'Personal' (dedicated) desktop within Azure Virtual Desktop, which provisions a dedicated VM and IP address exclusively for that user.
