Regional availability

Put the desktop
near the work.

Session placement follows tenant residency policy first. Capacity review then considers the people who will use the desktop.

Northern Europe / residency zone

Northern Europe

Regional workspace placement for engineering teams and residency-bound business applications.

Metro RTT planning target <15 msOPERATIONAL
Western Europe / residency zone

Western Europe

Browser desktop delivery for distributed staff and partner access inside the agreed region.

Regional RTT planning target <25 msOPERATIONAL
RegionAvailability zoneSession admissionPlacement control
Northern EuropeRegional workspace zoneAccepting tenant capacity reviewsTenant-pinned
Western EuropeRegional workspace zoneAccepting tenant capacity reviewsTenant-pinned

Planning targets describe access to the regional service, not a guaranteed desktop response time. User location, image workload, and local connectivity affect measured results.

Redundancy without moving your data

Regional interconnect paths can change while the broker preserves the tenant’s residency boundary. An unavailable region does not authorize automatic placement elsewhere.

Capacity is agreed before access

We review concurrent desktops, image memory, display requirements, and recovery expectations before reserving a pool. Facility details and tenant recovery procedures are shared during security onboarding.

Choosing an endpoint

Use the regional identifier assigned during onboarding. Endpoint roles and current admission policy are published in the regional coordinator’s discovery index. The integration guide explains how to resolve them.

Dedicated Access