User Profile
PaulCollinge
MicrosoftJoined Aug 23, 2017
User Widgets
Recent Discussions
Optimizing RDP Connectivity for Windows 365
Updated with RDP & Zscaler connectivity improvements August 2025 The use of VPN or Secure Web Gateway (SWG) client software or agents to provide tunneled access to on-premises resources in addition to providing protected internet access via a cloud based Secure Web Gateway (SWG) or a legacy VPN & on-premises proxy path is very commonly seen in Windows 365 and AVD deployments. This is especially the case when deployed in the recommended Windows 365 with Microsoft Hosted Network (MHN) model where the Cloud PC is located on a network with direct, open high-speed internet available. The more modern, cloud based SWG solutions fit perfectly with this modern Zero-Trust approach and generally perform at a higher level than traditional VPN software, where internet browsing is hairpinned through on-premises proxies and back out to the internet. As we have many Windows 365 customers using such solutions as part of their deployment, there are some specific configuration guidelines which are outlined in this post which Microsoft recommends are applied to optimize key traffic and provide the highest levels of user experience. What is the Problem? Many of these VPN/SWG solutions build a tunnel in the user context, which means that when a user logs in to their device, the service starts and creates the tunnels required to provide both internet and private access as defined for that user. With a physical device the tunnel is normally up and running before or shortly after the user sees their desktop on screen, meaning they can then quickly get on with their work without noticing its presence. However, as with any virtualized device which needs a remote connection to access, the above model poses several challenges: 1. Additional Latency Firstly, the remote desktop traffic is latency sensitive, in that delay to the traffic reaching its destination can easily translate into a poor user experience, with lag on actions and desktop display. Routing this traffic through a tunnel to an intermediary device to reach its destination adds latency and can restrict throughput regardless of how well configured or performing said device is. Modern SWG solutions tend to perform at a much higher levels than a traditional VPN/Proxy approach, but the highest level of experience is always achieved through a direct connection and avoiding any inspection or intermediary devices. Much like Teams media traffic, the RDP traffic in the Windows 365 case should be routed via the most optimal path between the two endpoints so as to deliver the very highest levels of performance, this is almost always the direct path via the nearest network egress. From a Cloud PC side this also means the traffic never leaves Microsoft’s managed network if directly egressed. 2. RDP Connection Drops An additional challenge comes from the use of user-based tunnels. As the user initiates a connection to the Cloud PC, the connection reaches the session host without issue and the user successfully sees the initial logon screen. However, once the user login starts, and the client software then builds the tunnels to the SWG/VPN for the user, the user then experiences a freeze of the login screen. The connection then drops, and we have to go through the reconnection process to re-establish the connection to the Cloud PC. Once this is complete, the user can successfully use the Cloud PC without further issue. Users however may also experience disconnects of the remote session if there is any issue with the tunnel, for example if the tunnel temporarily drops for some reason. Overall, this doesn’t provide a great user experience with the Cloud PC, especially on initial login. Why does this occur? It occurs because the tunnels built to route internet traffic to the SWG generally capture all internet bound traffic unless configured not to do so, a forced tunnel or ‘Inverse split tunnel’. This means the initial login works without issue but as soon as this tunnel is established upon user logon, the RDP traffic gets transferred into it and as it’s a new path, requires reconnecting. Equally, as the traffic is inside this tunnel, if the tunnel drops momentarily and needs to reconnect, this also causes the RDP session to require reconnecting inside the re-established tunnel. In the diagram below, you can see a simplified representation of this indirect connectivity approach with a forced tunnel in place. RDP traffic has to traverse the VPN/SWG resources before hitting the gateway handling the traffic. Whilst this is not a problem for less sensitive traffic and general web browsing, for latency critical traffic such as Teams and the RDP traffic, it is non-optimal. What’s the Solution? Microsoft strongly recommends implementing a forced tunnel exception for the critical RDP traffic which means that it does not enter the tunnel to the SWG or VPN gateway and is instead directly routed to its destination. This solves both of the above problems by providing a direct path for the RDP traffic and also ensuring it isn’t impacted by changes in the tunnel state. This is the same model as used by specific ‘Optimize’ marked Office 365 traffic such as Teams media traffic. On the Cloud PC side this also means this traffic never leaves Microsoft’s managed network. What exactly do I need to bypass from these tunnels? Previously, solving this problem meant significant complexity due to the large number of IP addresses required to configure optimization for this RDP traffic, we provided a script as part of this blog to assist with collecting and formatting these IPs. I'm pleased to share that Microsoft has invested in an extensive and complex piece of work to solve this challenge by building a new, upgraded global gateway infrastructure to allow it to be addressed from a single subnet. In addition to that simplification that we have planned so that this subnet should not see any regular change, abstracting customers from change as we scale the infrastructure and add new regions in future. As of February 2025, this work has now been completed and the old infrastructure decommissioned, this was all completed with zero downtime for our customers. This now allows RDP based traffic to now be covered by two single subnets rather than many hundred as previously was the case. There are further improvement works due to be delivered in the coming months for UDP based RDP to provide new dedicated and globally scaled TURN infrastructure. This post will be updated when this is complete and RDP connectivity is therefore in its final and complete, simplified and secured state. These temporary elements are: The WindowsVirtualDesktop service tag Is now up to date as of 19th March 2025 with all decommissioned IPs removed. 2. UDP based RDP via TURN now exclusively uses 51.5.0.0/16 as of August 2025. The new, dedicated subnet is in the WindowsVirtualDesktop service tag. More on this can be found in this post. This work will also vastly expand our global TURN relay availability. RDP based Connectivity bypass: As of August 2025, the critical traffic which carries RDP is contained within the following simplified endpoints: RDP Endpoints for Optimization Row Endpoint Protocol Port Purpose 1 *.wvd.microsoft.com TCP 443 Core TCP based RDP and other critical service traffic 2 40.64.144.0/20 TCP 443 Core TCP based RDP 3 51.5.0.0/16 UDP 3478 Core UDP based RDP via TURN Please see this article for more information on row 3 In some network equipment/software we can configure bypass using FQDNs and wildcard FQDNs alone, and we’d recommend that this method (row 1) is used in addition to the IP based rules if possible. However, some solutions do not allow the use of wildcard FQDNs so it’s common to see only IP addresses used for this bypass configuration. In this case you can use the newly simplified rows 2 & 3 in the table above, making sure row 1 is still accessible via the SWG/Proxy. There are also a small number of other endpoints which should be bypassed on the Cloud PC side: Other required VPN/SWG bypass requirements: Other endpoints for Optimization Row Endpoint Protocol Port Purpose 4 azkms.core.windows.net TCP 1688 Azure KMS - Traffic Needs to arrive from Azure public IPs 5 169.254.169.254 TCP 80 Azure Fabric communication 6 168.63.129.16 TCP 80 Azure Fabric communication These additional bypass requirements (4-6) are not RDP related but are required for the following reasons: Row 4 – This is Azure KMS activation which is a required endpoint for a Cloud PC and AVD Session Hosts. The traffic for this needs to arrive from an Azure public IP, if not then the connection will not be successful. Therefore it should not be sent via a 3 rd party internet egress such as via an SWG or proxy. IP addresses corresponding to the FQDN can be found via the link above if required. Rows 5 & 6 – These are critical IP addresses used to communicate to the Azure Fabric to operate the VM. We need to ensure these are not inadvertently sent in any VPN/SWG tunnel where they will not be then able to reach their destination in Azure. How do I implement the RDP bypass in common VPN/SWG solutions? Microsoft is working with several partners in this space to provide bespoke guidance and we’ll add detailed guidance for other solutions here as we get them confirmed. Already available however is Zscaler ZIA. Zscaler Client Connector The changes outlined above should make configuration in all scenarios vastly simpler moving forward. Due to some fantastic work to assist our mutual customers by our friends at Zscaler, as of February 2025 and version 4.3.2 of the Zscaler Client Connector, the majority of the mentioned Windows 365 and AVD traffic which requires optimization, including RDP can be bypassed with a single click configuration within a predefined IP based bypass! Zscaler ZIA Configuration Version 4.3.2 (Released Feb 2025) of the Zscaler Connector Client portal enables this feature. Ensure a recent version of the Client Connector is installed on both the Cloud PC (And Physical device if Zscaler is used there) to take advantage. In the Zscaler Client Connector Portal, select the new IP-Based, Predefined Application Bypass for Windows 365 & Azure Virtual Desktop. This contains preconfigured bypass for RDP and KMS traffic. 3. Add the following endpoints to the bypass configuration manually as they are not included in the automatic bypass. Endpoint Protocol Port Purpose 169.254.169.254 TCP 80 Azure Fabric communication 168.63.129.16 TCP 80 Azure Fabric communication Other VPN/SWG solutions Microsoft is currently working with other partners in this space to provide detailed guidance for other VPN/SWG solutions and will list them here as they are complete. Please let us know in the comments if you’d like us to list a particular solution and we’ll aim to prioritize based on feedback. In the interim, use rows 1-6 in the tables above to create manual bypasses from VPN/SWG/Proxy tunnels. This should be significantly simpler and have much lower change rates than previously due to the IP consolidation. FAQs: Q: In a Microsoft Hosted Network deployment, is there anything else I need to do? A: Unless the local Windows firewall is configured to block access to the endpoints noted, there should be nothing else required, the network the virtual NIC sits in has direct, high speed connectivity Microsoft’s backbone and the internet. Q: In an Azure Network Connection scenario, is there anything further I need to do? A: In this scenario, the recommended path for the traffic is directly out of the VNet into Microsoft’s backbone. Depending on the configuration it may require allowing the endpoints noted in this article through a firewall or NSG. The WindowsVirtualDesktop service tag or FQDN tag may help with automating rules in firewalls or configuring User Defined Routing. RDP traffic specifically should be sent direct into Microsoft’s backbone via a NAT Gateway or similar with no TLS inspection, avoiding putting load on NVAs such as Firewalls. Q: Do I need to configure the bypass on just the Cloud PC? A: RDP connectivity (Rows 1-3) is used identically on both the physical and cloud sides. It is strongly advised that the bypass is applied to both the Cloud PC and the connecting client if that also uses the SWG/VPN to connect. If both are using the same configuration profile then this should happen automatically. Rows 4-6 are only required on the cloud side. Q: How often do the IP addresses Change? A: Now the improvement work is complete we don’t anticipate regular change. You can monitor the WindowsVirtualDesktop service tag for changes if desired and we’re working on getting these requirements into the M365 Web Service longer term for monitoring and automation. Q: Can I add more than the RDP traffic to the bypass. A: Microsoft only provides IP addresses for the RDP connectivity at present. However if your solution is capable of configuration by FQDN alone, then you can add other service endpoints to your optimized path, these can be found on this Microsoft docs page. Q: Im using a true split tunnel, does this impact me? A: The above advice is for a forced tunnel scenario (inverse split tunnel) where the default path is via the tunnel and only defined exceptions are sent direct, which is often referred to as a split tunnel in common parlance and is the most commonly seen deployment model of such solutions. However a split tunnel in the technically accurate sense of the words, where the default path is the internet and only defined endpoints (such as corp server ranges/names) are sent down the tunnel, shouldn’t need such configuration as the RDP traffic should follow the default path to the internet. Q: Does this also optimize RDP shortpath? A: RDP Shortpath for Public Networks works to provide a UDP based RDP connection between the client and Cloud PC if enabled and achievable. This connection is in addition to the TCP based connection described above and the dynamic virtual channels such as graphics, input etc are switched into the UDP connection if deemed optimal. Row 3 above covers this traffic for connectivity via TURN relays. Please see this article for more information on this connectivity model. Q: Is this advice also shared in Microsoft’s official documentation? A: We’re currently working on uplifting the entire connectivity documentation for Windows 365 and the above will form part of this work in the coming months. We’ll share the official link in this blog when available. Q: Does this advice apply equally to AVD? A: Yes, both Windows 365 and AVD have exactly the same requirements in terms of the connectivity discussed in this blog.Re: Optimizing RDP Connectivity for Windows 365
Correct, using tunnel1 you can use a PAC file to make the adjustment. Given Zscaler's recommendation is for tunnel2 then this is what we focus on above. The IP subnets should come down to just two within the coming months making this easier to configure.Re: Optimizing RDP Connectivity for Windows 365
SanjayP2280 The FQDN to offload should be *.wvd.microsoft.com. Alternatively use the IPs outlined in the article, this should work seamlessly. We're working on reducing the subnet count down to two subnets and this work should complete in the coming months. PaulUpcoming Endpoint Requirements Improvement for Windows 365
Windows 365 has a range of connectivity requirements in terms of FQDNs which need to be accessible directly from the VNet for the service to be able to operate and users connect to their Cloud PC. As the service has grown and expanded, over time this list has grown at in parallel. Significant effort has been going on in the background by our fantastic engineering team to simplify and reduce these requirements and also abstract customers from future change where possible as the service expands and improves over time. I’m pleased to announce Windows 365 customers will start to see the first of the improvements cumulating from this work start rolling out over the coming months. This has been relayed to customers via message center post ID MC675811 already but you’ll find more detail on this change below. What is changing? The first of these improvements revolves around the reduction of the required FQDNs for the service. Over the coming months we’ll be removing the use of a considerable number of the required FQDNs from the requirements, once this is fully complete, we’ll remove them from our docs page and at that point they can then be safely removed from any firewall rules etc. We will send out official communications to customers when this removal can be done. Following this initial phase, even more removals are planned in future as engineering work to facilitate this completes. In addition there are also other significant improvements being worked on which we’ll announce nearer the time they are ready to be released. What are the endpoints being replaced with? We’re moving a large number of the FQDNs to resolve under an existing wildcard FQDN *.infra.windows365.microsoft.com (*.infra.windows365.microsoft.us if within Windows 365 US Government environments) which has been part of the published endpoint requirements for a considerable amount of time. For example, an existing endpoint such as cpcsaamssa1prodprap01.blob.core.windows.net will now become accessible via something.infra.windows365.microsoft.com instead. As the wildcard means ‘anything’, this means we can create future endpoints inside this wildcard domain without the need for changes to your rulesets and configuration. Where in my Windows 365 deployment does this impact? These changes are only for the Cloud PC side only. No access is required for these endpoints on the side of the physical device connecting to Windows 365. For customers using recommended Microsoft Hosted Network (MHN) model, the underlying network for the VNet automatically has access to the required endpoints so for example for traffic initiated during the provision phase has access with no configuration required. However, please ensure any proxy or Secure Web Gateway (SWG) path allows access to this endpoint should connectivity be required from the Cloud PC itself post provisioning. For customers using Azure Network Connection (ANC) please ensure that the underlying network path the VNet has, allows for direct access to this domain, for example through a virtual firewall in Azure providing the required connectivity for the service. Please also ensure any proxy/ SWG path the Cloud PC uses once provisioned, also allows access. Customers using Azure Firewall and FQDN tags should have to make no change as the endpoint is already included in the tag. For more information on these two network deployment models, see here. What are the benefits of this change? There are numerous benefits accrued through this first phase of improvements: Reduced endpoint requirements for initial configuration – Configuring firewalls and rulesets will become significantly simpler. Vastly reduced change rate – As with any growing and expanding cloud service, new endpoint requirements happen regularly. With this approach the goal is to ensure wherever possible, any new service endpoint will come from the existing wildcard FQDN meaning customers are abstracted from this change and do not have to make regular rule updates. Reduced risk of misconfiguration – The simpler requirements and reduced change rate, reduces the risk of missing endpoints in any configuration. Enables future improvements in required endpoint provisioning/management to be announced at a future date. What do I need to do to prepare? As the endpoint we’re migrating to (*.infra.windows365.microsoft.com) has been in the published requirements for a considerable amount of time, it’s very likely that no change to configuration is necessary in most customer environments. However, you may want to ratify that this endpoint is accessible from your environments by doing the following. For Customers using Azure Network Connection, please ensure *.infra.windows365.microsoft.com is accessible directly from the VNet, for example in an Azure Firewall or other NVA. Customers using FQDN tags in Azure firewall need to make no change as the endpoint is already in the tag. For any customers using a proxy or Secure Web Gateway (SWG) for traffic initiated from the Cloud PC once provisioned & configured, please ensure the rulesets for these services allow *.infra.windows365.microsoft.com How do I check access is possible? Although this endpoint isn’t designed to be human accessible, If you wish to ratify that access is possible to *.infra.windows365.microsoft.com you can use the following methods: The recommended way to check is by using an ANC Healthcheck. The check for this wildcard FQDN will be live in the ANC checks late October 23 and will flag a warning if not accessible. I’ll update this blog when this method is live and ready for use. If you wish to manually check access, from a browser running within the VNet you want to test, go to saprod.infra.windows365.microsoft.com – If accessible you’ll get an XML error returned as per the example below. Ensure the traffic is sent direct from the VNet however and not via a proxy or similar as the key connectivity is required during provisioning when proxies will not be in use. From a windows device within the VNet you can use PSPING to make a test TCP connection to the endpoint using the following command Psping -n 5 saprod.infra.windows365.microsoft.com:443 You will again need to ensure this connection is routed directly out of the VNet and not via any SWG/Proxy infrastructure so as to ensure the direct path required for provisioning/operation is available. If successful you should see a response similar to that below:Re: Optimizing RDP Connectivity for Windows 365
Zscaler cannot use wildcard FQDNs in the config above, hence why IPs are used in the example. You should also include the two IPs mentioned in addition as they are both not included in the RDP IP information. I don't expect them to change as they are used pervasively within Azure.Re: Optimizing RDP Connectivity for Windows 365
Hi, The answer depends on the solution you're using, some VPN/SWG software allows configuration using wildcard FQDNs, where that's possible you can use *.wvd.microsoft.com. Others don't support wildcard FQDNs so you'll have to use the IP list. We're working on consolidating the IP space into a small number of subnets which won't change regularly which will resolve this particular challenge, however that will take some considerable time to complete.
Recent Blog Articles
How to quickly optimize Office 365 traffic for remote staff & reduce the load on your infrastructure
Over the past few weeks, Microsoft, and more specifically the Office 365 Network team have seen a large influx of questions from customers around how best to optimize their Office 365 connectivity as...
