| title | description | services | documentationcenter | author | manager | ms.assetid | ms.service | ms.workload | ms.tgt_pltfrm | ms.devlang | ms.topic | ms.date | ms.author |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Azure RemoteApp network bandwidth - general guidelines | Microsoft Docs |
Understand some basic network bandwidth guidelines for your Azure RemoteApp collections and apps. |
remoteapp |
msmbaldwin |
mbaldwin |
529bf318-ae37-4c14-a11c-43fa703d68a3 |
remoteapp |
compute |
na |
na |
article |
11/23/2016 |
mbaldwin |
Important
Azure RemoteApp is being discontinued. Read the announcement for details.
If you do not have the time or capability to run the network bandwidth tests for Azure RemoteApp, here are some fairly generic guidelines that can help you estimate network bandwidth per user.
If you have a mix of these scenarios, we don't recommend anything less than (or equal to) 10 MB/s as the MINIMUM network bandwidth for modern Internet-connected apps in a remote environment. (Although, as discussed, this will not guarantee a better than average user experience.)
Azure RemoteApp does best on 100 MB LAN. At the 10 MB/s network profile, when jitter above 120 ms is more than 5%, the user will see an average experience. At 1 MB/s the different is glaring - for example, in a slide show, the user might not see animated transitions at all because frames are skipped.
10 MB/s network profile is close to LAN in most aspects. 1 MB/s will provide an OK experience, although there may be some jitter when a user scrolls while there are images on the screen.
100 MB/s LAN provides the best experience, while 10 MB/s is acceptable (meaning we keep up with the frame rate but jitter increases). At 1 MB/s, jitter is very high and noticeable.
This is a low-bandwidth usage scenario. At 256 KB/s we provide as good of an experience as LAN.