Network requirements

A stable, low-latency network connection to an Azure data center is critical for a good user experience in Azure Remote Rendering. Poor network conditions can result in dropped connections, unstable, jittery, or 'jumping' holograms, and noticeable lag when updating the server-side scene graph.

Guidelines for network connectivity

The exact network requirements depend on your specific use case, such as the number and frequency of modifications to the remote scene graph as well as the complexity of the rendered view, but there are a number of guidelines to ensure that your experience is as good as possible:

  • Your internet connectivity needs to support at least 40 Mbps downstream and 5 Mbps upstream consistently for a single user session of Azure Remote Rendering, assuming there is no competing traffic on the network. We recommend higher rates for better experiences.
  • Wi-Fi is the recommended network type since it supports a low latency, high-bandwidth, and stable connection. Some mobile networks introduce jitter that can lead to a poor experience.
  • Using the 5-GHz Wi-Fi band will usually produce better results than the 2.4-GHz Wi-Fi band, though both should work.
  • If there are other Wi-Fi networks nearby, avoid using Wi-Fi channels in use by these other networks. You can use network scanning tools like WifiInfoView to verify whether the channels your Wi-Fi network uses, are free of competing traffic.
  • Strictly avoid using Wi-Fi repeaters or LAN-over-powerline forwarding.
  • Avoid competing bandwidth-intense traffic – such as video or game streaming – on the same Wi-Fi network.
  • If you have multiple devices on the same access point, the requirements scale up correspondingly. If you have multiple access points across an environment, load balance devices across the access points, so they are evenly distributed.
  • Having good Wi-Fi signal strength is essential. If possible, stay close to your Wi-Fi access point and avoid obstacles between your client device and the access points.
  • Make sure that you always connect to the nearest Azure data center for your region. The closer the data center, the lower the network latency, which has a huge effect on hologram stability.


The downstream bandwidth is mostly consumed by the video stream, which in turn is split between color- and depth information (both 60 Hz, stereo).

Network performance tests

If you want to get an initial understanding of whether the quality of your network connectivity is sufficient to run Azure Remote Rendering, there are existing online tools that you can use. We strongly recommend running these online tools from a reasonably powerful laptop connected to the same Wi-Fi as the device that you are planning to run your Azure Remote Rendering client application on. Results obtained from running the tests on a mobile phone or HoloLens2 are usually less useful, as they have proven to show significant variation on low-powered endpoint devices. The location at which you place the laptop should be roughly at the same place at which you expect to use the device that runs your Azure Remote Rendering client application.

Here are a few simple steps for a quick test of your network connectivity:

  1. Run a network testing tool like to get data on the overall latency and upstream/downstream bandwidth of your network connection. Pick a server closest to you and run the test. While the server will not be the Azure data center that Azure Remote Rendering will connect to, the resulting data is still useful to understand the performance of your internet connection and Wi-Fi.
    • Minimum requirement for Azure Remote Rendering: Approx. 40 Mbps downstream and 5 Mbps upstream.
    • Recommended for Azure Remote Rendering: Approx. 100 Mbps downstream and 10 Mbps upstream. We recommend running the test multiple times and taking the worst results.
  2. Use a tool like that measures latency to Azure data centers. Select the Azure data center supported by Azure Remote Rendering that is closest to you (see supported regions) and run a latency test. If there is variation in the numbers you see, give the results some time to stabilize.
    • Minimum requirement for Azure Remote Rendering: Latency should consistently be less than 80 ms.
    • Recommended for Azure Remote Rendering: Latency should consistently be less than 40 ms.

While low latency is not a guarantee that Azure Remote Rendering will work well on your network, we have usually seen it perform fine in situations where these tests passed successfully. If you are encountering artifacts such as unstable, jittery, or jumping holograms when running Azure Remote Rendering, refer to the troubleshooting guide.

How to 'ping' a rendering session

It might be useful to measure latencies against a specific session VM, as this value may differ from values reported by The hostname of a session is logged by the powershell script to create a new session. Similarly, there is a hostname property in the REST call response and also in the C++/C# runtime API (RenderingSessionProperties.Hostname). Furthermore, the handshake port is needed, which can be retrieved similarly.

Here is some sample output from running the RenderingSession.ps1 script:

Retrieve hostname from powershell output

ARR session VMs do not work with the built-in command line 'ping' tool. Instead, a ping tool that works with TCP/UDP must be used. A simple tool called PsPing (download link) can be used for this purpose. The calling syntax is:

psping.exe <hostname>:<handshakeport>

Example output from running PsPing:

PsPing an ARR session

Next steps