Deployment
Cloud or on-premises. Same application, same level of detail.
CONOPS | MOS (Manufacturing Operating System) runs as a Windows service against Azure SQL in Azure Government, or against SQL Server 2022 on your hardware. Neither option is second class, and in both the ERP is only ever read.
Side by side
The comparison your IT and compliance teams asked for
| Cloud · Azure Government (GCC High) | On-Premises · Windows Server + SQL Server 2022 | |
|---|---|---|
| Where the app runs | A Windows or Linux VM in your Azure Government subscription, or a plant server, running the standalone build as a service | One Windows Server on your network running the standalone build as a boot-start service behind an IIS HTTPS reverse proxy |
| Where the database runs | Azure SQL Database (General Purpose, serverless) in Azure Government, in your subscription | SQL Server 2022 on your hardware; application and warehouse databases on the same instance |
| Where files live | SharePoint Online in your GCC High tenant, via Graph API on graph.microsoft.us | SharePoint Online in your tenant; an on-premises file-share option for air-gapped sites is scoped as a service |
| Identity provider | Your Entra ID on login.microsoftonline.us; single sign-on, six roles | Your Entra ID (hybrid) unless scoped otherwise; single sign-on, six roles |
| Who holds the admin credentials | You. We never hold a tenant or a subscription for you | You. Service accounts and SQL logins are created and owned by your IT |
| Network exposure | Private endpoint or VNet-integrated; HTTPS only; outbound only to Microsoft Graph and SMTP in your tenant | Internal only behind IIS; outbound only to Microsoft Graph and SMTP in your tenant; no vendor telemetry |
| Backup and restore | Point-in-time restore, 7-day retention by default, long-term retention optional | Your SQL Server backup policy; we provide the restore runbook and verify reports |
| Update mechanism | Ordered, idempotent SQL scripts run by your DBA or by us under escort, then one web deploy | Ordered, idempotent SQL scripts run by your DBA or by us under escort, then one web deploy |
| Typical go-live time | 6 to 9 weeks from discovery for the first site; environments provisioned in the first week | 7 to 10 weeks from discovery for the first site; server and SQL provisioning on your IT calendar |
| What your IT must provide | A GCC High tenant, an Azure Government subscription, an app registration, a VM or App Service, network rules | A Windows Server, a SQL Server 2022 instance, a TLS certificate, linked-server access to each ERP, a service account |
Decision guide
Which one, in two sentences
Choose Cloud when
You already have the tenant and the subscription.
- You have a GCC High tenant and an Azure Government subscription today
- You want point-in-time restore and elastic compute without owning a server
- Sites are on different networks and need one reachable service
Choose On-Premises when
Policy or the network says so.
- Policy forbids any cloud database, even in Azure Government
- The plant network is isolated or air-gapped
- You already run SQL Server 2022 and want the warehouse next to the ERP
Questions IT asks first
Deployment FAQ
Is CONOPS | MOS a hosted SaaS?
No. It runs in your Azure Government subscription or on your own Windows Server and SQL Server 2022. There is no vendor-hosted multi-tenant service, and CONOPS never holds a tenant or credentials for you.
Does it write to our ERP?
No. A metadata-driven warehouse pulls change-only loads nightly from each site's ERP over a linked server. Nothing is written back. Infor VISUAL and Infor SyteLine are mapped today; other ERPs are scoped as a fit assessment.
What outbound connections does the service make?
Microsoft Graph (SharePoint attachments) and SMTP (Exchange Online) in your tenant, on the .us endpoints for GCC High. There is no telemetry to CONOPS.
How are updates applied?
Ordered, idempotent SQL scripts with a migration manifest and verify reports, run by your DBA in SSMS or by us under escort, followed by one web deploy. No CI/CD pipeline needs access to your environment.
Can we move from one option to the other later?
Yes. The application is identical; a move is a database backup and restore plus reconfiguration of connection strings, identity redirect URIs and file storage.
Next step
Request a readiness review for the option you lean toward.
A 45-minute call with the engineer who will run your deployment. We check tenant, subscription, SQL Server, network and ERP access, and give you a written list of what to provision.