Azure Virtual Desktop and ArcGIS Pro performance

[EmikoCondeso]

Hi all,

We are running our GIS on Azure Virtual desktops, in order to share spatial data among many remote staff.  We are a relatively small org, so Enterprise GIS hasn't been an option for us.  The org otherwise shares data (non GIS) using Sharepoint.

So far, we have had issues with slow processing and big lags. It can take several seconds for a click to register in ArcPro, even when working with high internet speeds and very little going on in the map document in terms of symbology, queries, etc.

Are others experiencing the same? Any tips for optimizing this environment, or should we search for another solution?

With gratitude,

Emiko

[DanPatterson]

How is your setup (hardware, software) in light of the recommended documentation?

ArcGIS Pro on Microsoft Azure Cloud | ArcGIS Pro documentation

[EmikoCondeso]

I'll ask our IT support to review this doc and let me know. Thanks a million!

[Robert_LeClair]

Yes—this is a common symptom when ArcGIS Pro is run via Azure Virtual Desktop and the environment isn’t optimized for latency + GPU acceleration. Even with high bandwidth, ArcGIS Pro interactivity can feel “seconds behind” if round-trip latency (RTT) is high, if the session is CPU-rendering (no effective GPU), or if the VM/GPU is oversubscribed.

Here are some steps you can try (based on Esri guidance):

1. Check network latency first (not just bandwidth)

   • Esri notes remote desktop user experience is very sensitive to latency and typically needs ≤ 200 ms RTT for responsive interaction.
   • If users/hosts/storage are in different Azure regions, move them closer (same region/subnet where possible).
     Source: ArcGIS Pro on Microsoft Azure Cloud (3.7)
     
     

2. Confirm ArcGIS Pro is actually using hardware acceleration (GPU)

   • If hardware acceleration isn’t available, Pro falls back to software rendering (CPU), which often causes stutter/lag in virtual sessions.
     Source: Machine performance optimizations (3.7)
     
     

3. Right-size the AVD session hosts (CPU/RAM/GPU) and reduce contention

   • Esri advises a discrete GPU with at least 4 GB dedicated memory and notes undersized/shared CPU/RAM/GPU can cause lag and delayed response.
     Source: ArcGIS Pro on Microsoft Azure Cloud (3.7)

4. Apply AVD-specific optimizations Esri calls out

   • Use FSLogix for profiles and enable UDP short path; validate performance with the ArcGIS Pro Performance Assessment Tool (PAT).
     Source: ArcGIS Pro on Microsoft Azure Cloud—ArcGIS Pro (3.6)

[EmikoCondeso]

Thanks so much!! I will check with our IT support.  I really appreciate the help.

[DavidSolari]

You should absolutely work with IT to ensure your machines are up to spec like everyone's said. Just keep in mind you'll still run into noticeable latency and random window compositing glitches on AVD, you pay a price for getting Pro running close to your shared files and databases.

[EmikoCondeso]

Thanks for the reply! Can you elaborate on what kind of latency is expected with everything configured properly?  
We notice currently that it can vary a lot from day to day, and not in a predictable way.

[KeithDesertspring]

Not sure if it's 100% relevant, but I am using ArcGIS Pro 3.5 over a Windows remote desktop connection, and everything is sufficiently responsive. The remote machine exceeds the minimum requirements. 

Latency is no higher than it is for other apps running on the computer. About 0.2 second if I had to guess. It's enough to remind you that you're not physically sitting in front of the machine, but not so bad that it's intrusive.