Skip to main content
Question

Implications of moving the Azure region our Cloud and MWM instances are in

  • March 25, 2026
  • 1 reply
  • 30 views

dcw601
Do Gooder (Customer)
Forum|alt.badge.img+1

We are in the early stages of a multi-year and multi-phase project to roll out IFS Cloud, MWM, MWO, and PSO, along with other systems.  One of those is a new ESRI (GIS) instance.  For reasons of capacity management, Microsoft has asked us to build the ESRI instance in the US Central region of Azure.  Our IFS deployments are in US Eastern.  For planning purposes, we would like to understand the implications of having our applications in multiple regions, and, conversely, the implications of moving our IFS deployments to a new region to keep them close together.

IFS experts: what insights can you share?

IFS customers: has anyone faced a similar situation, and how have you handled it?

1 reply

Udara Hasantha
Do Gooder (Customer)
Forum|alt.badge.img+4
  • Do Gooder (Customer)
  • March 25, 2026

Hi ​@dcw601 

My idea is to keep things as they are for now and build the ESRI instance in US Central as Microsoft wants. Set up secure connections between the two regions, test the performance for a couple of weeks, and monitor it closely. If there are no real issues after 1–2 months, just leave it. Only move IFS to Central later if your GIS usage becomes very heavy (over 30% of daily work) or if you have other strong reasons. Since you're still early in the project, this is low risk and easy to change later.

You may contact IFS Operational Success for further details. 

Reasoning for this idea

Microsoft's latest backbone stats (30-day P50 median, June 2025 data):

  • East US → Central US: 28 ms RTT
  • East US 2 → Central US: 36 ms RTT

Which is excellent for enterprise workloads.

  • Intra-region is <2 ms, but 28–36 ms is completely fine for:
    • IFS GIS Map service calls
    • ArcGIS REST/Feature Service queries
    • MWM/MWO map rendering
    • PSO optimization jobs that pull spatial data