CONOPS A product of CONOPS
Cloud deployment

Your GCC High tenant. Your Azure Government subscription. Your credentials.

CONOPS | MOS (Manufacturing Operating System) in the cloud means the service and the database live in your subscription and your tenant. We never hold a tenant for you, and all credentials are yours.

Topology · Azure Government
ComponentWhereEndpoint
Web service Your VM in Azure Government, or a plant server HTTPS, private
Database Azure SQL Database, General Purpose serverless Private endpoint
Files SharePoint Online, your GCC High tenant graph.microsoft.us
Identity Entra ID, your tenant login.microsoftonline.us
Mail Exchange Online SMTP .us
ERP Your ERP server Linked server, read only
Every component sits inside your Microsoft 365 Government boundary or your network.
What you own

Everything with a credential

  • The GCC High tenant, the Azure Government subscription and the app registration
  • The Azure SQL server and databases, including backups and retention settings
  • The SharePoint site, the shared mailbox and the sending identity
  • Network rules, private endpoints and the TLS certificate
  • Role assignment: who is Admin, Manager or Read Only at each site
What we configure

The platform inside it

  • Database schema, migrations, Row-Level Security policies and verify reports
  • Service configuration, connection strings and the Entra ID redirect URIs
  • Warehouse load definitions for each site's ERP and the nightly schedule
  • Sites, departments, workcenters, record types, SLAs, roles and workflow templates
  • The three environments and the promotion path between them
Environments, backup and capacity

Sized for shift change, not for a demo

Three environments
  • Dev for template and configuration work
  • Staging for migration rehearsal against a restored copy
  • Prod with private endpoints and restricted admin access
Backup posture
  • Point-in-time restore on Azure SQL
  • 7-day retention by default
  • Long-term retention optional, set by your policy
Capacity targets the design was sized for
  • About 150 concurrent users at shift change
  • 500 to 1,000 new records per week
  • 1 to 4 vCores, serverless auto-pause outside shifts if you want it
Provisioning checklist

What your IT provides before week one

  1. Tenant and subscription

    A GCC High tenant and an Azure Government subscription with a resource group for the platform.

  2. App registration

    An Entra ID app registration with the redirect URIs we supply, and Graph application permissions for the SharePoint site and shared mailbox.

  3. Compute and database

    A VM or App Service for the web service and an Azure SQL logical server. We supply the sizing sheet.

  4. Network

    Private endpoint or VNet integration, HTTPS certificate, outbound rules for Graph and SMTP on the .us endpoints, and linked-server reachability to each ERP.

  5. Named owners

    A tenant administrator, a DBA and a network contact for the deployment window and for the update escort later.

Next step

Request a cloud readiness review.

We check tenant, subscription, app registration, network and ERP reachability with your IT, and return a written provisioning list.