Hosting eForms Mobile Replicate on Azure is a popular choice for scalability. While the core installation process remains the same as an on-premise server, there are specific networking and database considerations unique to the Azure ecosystem.
Azure Hosting Guide
Supported Environments
Azure Virtual Machines (VM): Fully supported. Ensure your VM uses a compatible Windows Server image.
Azure App Service / Cloud Services: Not currently supported.
Administrator Access Required: You must have Administrator-level privileges on the target VM. Several installation steps require deep system access that cannot be bypassed.
Database Options on Azure
You have two primary paths for satisfying the SQL Server requirement:
Managed Service: Azure SQL Database
This is Microsoft’s managed “Database-as-a-Service.”
- Pros: High availability, zero server maintenance, and fast setup.
- Cons: Performance can vary by pricing tier; it may be more expensive.
- Recommendation: Start here for simplicity. If the price-to-performance ratio doesn’t meet your needs, you can export your data to a dedicated SQL VM later.
Self-Hosted: SQL Server on a VM
You can install SQL Server (Express or higher) directly on the same VM as Replicate, or on a separate dedicated VM.
- Pros: Total control over configuration and costs.
- Cons: Requires manual updates and management.
- Recommendation: Use a dedicated SQL VM if you expect to process several thousand rows per day.
Networking & Firewall Configuration
Since your infrastructure is cloud-based, you must configure communication “tunnels” between your VM and the database.
Connecting to Azure SQL Database
To ensure eForms Mobile Replicate can talk to your Azure SQL instance, follow these steps:
- On the Database Side:
- Simple Method: Enable the “Allow Azure Services and resources to access this server” (formerly “Allow Azure Connections”) toggle in the SQL Database firewall settings.
- Secure Method: Assign a Static IP to your Replicate VM and whitelist that specific IP in the SQL Database firewall.
- On the VM Side:
- Opening the firewall for the SQL Gateway IP is not enough. Azure SQL establishes an initial connection via a gateway but then redirects traffic to a specific Database Cluster IP.
- Action: You must allow outbound traffic on your VM firewall for both the Azure SQL Gateway IP and the specific IP of your database cluster.
Resource: For a list of Gateway IPs and deep dives into connectivity, refer to the Microsoft Azure SQL Connectivity Architecture documentation.
Azure Deployment: Pre-Flight Checklist
Before running the eForms Mobile Replicate installer on your Azure VM, ensure the following are configured:
- Public IP: Your VM has a Static Public IP or a Reserved DNS name.
- NSG Rules: Your Azure Network Security Group has Port 443 (HTTPS) open for inbound traffic.
- SQL Auth: Your SQL Server (Managed or VM) is set to SQL Server Authentication mode (Replicate requires a username and password).
- IIS Features: The “Web Server” role is installed on the VM with ASP.NET 4.8 and Management Service enabled.