Hosting Geo SCADA Expert on Microsoft Azure: Architecture, Sizing, and Licensing
Key Takeaway
Geo SCADA Expert runs on Microsoft Azure virtual machines using the same software and sizing approach as on-premise servers, scaled to your database object count. Key Azure-specific considerations are instance-based licensing with fixed MAC address and disk ID pinning, secure connectivity from field devices via VPN or ExpressRoute, high-performance disk for the historian, and placing primary and standby servers in separate fault domains for redundancy.
Quick Answer
Geo SCADA Expert runs on Microsoft Azure virtual machines using the same software and sizing approach as an on-premise server, scaled to your database object count. The Azure-specific items to get right are instance-based licensing (with fixed MAC address and disk ID pinning for soft-key licenses), secure connectivity from field devices via VPN or ExpressRoute, high-performance managed disk for the historian, and separating primary and standby servers into different fault domains for redundancy. Always confirm current licensing and sizing rules with Schneider Electric before you build.
Why Azure for Geo SCADA
Azure is a common landing spot for Geo SCADA because many SCADA shops already run Windows Server and SQL Server, both of which are first-class on Azure. Teams that have standardized on Microsoft identity, networking, and management tooling can extend those practices to their SCADA estate rather than maintaining a separate on-premise stack. For the broader trade-offs, see our cloud vs on-premise comparison.
Reference Architecture
A typical Azure-hosted Geo SCADA deployment includes:
- Geo SCADA Expert server VM running Windows Server, sized to your database and historian load.
- Standby server VM in a separate availability zone or fault domain for redundancy, mirroring the on-premise primary/standby pattern.
- Virtual ViewX / web server VM on IIS, kept separate from the Geo SCADA server for security and scalability, as in our ViewX client setup guide.
- Secure connectivity from remote sites — a site-to-site VPN or an Azure ExpressRoute private circuit — so field RTUs reach the server without exposing it to the public internet.
- High-performance managed disks separating the operating system, the configuration database, the historian, and the event journal where performance demands it.
Sizing the VM
Azure VM sizing follows the same logic as physical Geo SCADA servers: it is driven primarily by the number of database objects, point count, historian throughput, and client load. A small system with on the order of ten thousand objects needs far less compute and disk than a large estate with tens of thousands of objects and heavy historian recording. Rather than copying a fixed spec, calculate resources from Schneider's recommended server configurations for your object count, then map that to an equivalent Azure VM SKU and managed-disk tier. If you consolidate multiple Geo SCADA servers onto shared infrastructure, aggregate their requirements. Historian performance especially benefits from premium SSD; see historian optimization for the tuning that complements good disk choices.
Licensing in Azure
Geo SCADA Expert licensing is instance-based: you need a license for each running copy of the software, including each Virtual ViewX server. For soft-key (license file) deployments in a cloud environment, the VM is generally pinned to a fixed MAC address on its virtual NIC and a fixed system disk ID so the license remains valid. Redundant architectures require a license per running instance. These mechanics change over time and are enforced by Schneider, so confirm the exact current requirements — and have your license files updated for the new machine identifiers — with Schneider Electric before migrating.
Connectivity and Latency
The biggest architectural change versus on-premise is that field devices now communicate to a server in Azure. Plan for resilient connectivity: redundant VPN tunnels or ExpressRoute with failover, careful tuning of DNP3 and Modbus timeouts to tolerate added latency, and edge buffering at the RTU so events are not lost during a connectivity blip. Security for this connectivity is covered in securing hosted Geo SCADA.
Backups, Patching, and HA
Cloud hosting does not remove the maintenance burden — it relocates it. You still need disciplined patching, verified backups, and tested failover. Azure makes some of this easier (snapshots, zone redundancy), but the discipline of our backup and failover testing guide still applies.
Getting Help
NFM Consulting designs and operates Azure-hosted Geo SCADA environments — sizing, networking, licensing coordination, and ongoing managed support. Contact NFM Consulting to plan an Azure-hosted Geo SCADA deployment.
Frequently Asked Questions
Yes. Geo SCADA Expert is supported on Azure virtual machines to the same extent as physical servers, running the same Windows Server and SQL Server stack. The main Azure-specific considerations are instance-based licensing with fixed MAC and disk ID pinning for soft-key licenses, secure connectivity from field devices, and selecting an appropriately sized VM and disk tier for your database and historian load.
Sizing follows the same approach as on-premise servers and is driven mainly by database object count, point count, historian throughput, and client load. Calculate resources from Schneider's recommended server configuration for your object count, then map that to an equivalent Azure VM SKU and managed-disk tier, using premium SSD for historian performance. Aggregate requirements if you consolidate multiple servers on shared infrastructure.
Geo SCADA Expert uses instance-based licensing — a license is required for each running copy, including each Virtual ViewX server and each redundant instance. For soft-key license files in the cloud, the VM is typically pinned to a fixed MAC address and system disk ID to keep the license valid. These rules are set and enforced by Schneider Electric and change over time, so confirm current terms before migrating.