Choose the appliance route when you need a self-contained, customer-managed deployment with strong governance and offline readiness.
The overview below highlights the deployment posture, the architecture pattern, and the operating model for MSC in on-premises environments.
The same 4-Stage Cycle and evidence-led approach inform both deployment routes. In the hosted portal, MSC processes run data and holds operational results while customer-owned output delivery is being validated. Available scenarios and storage options depend on the route.
This view makes the deployment boundaries explicit so reviewers can see how MSC uses Microsoft Azure services, the customer environment, and the on-premises estate.
The diagram highlights the Azure cloud boundary, the customer and partner environment, the on-premises estate, and the reusable IP module that powers the repeatable solution logic.
MSC solution framework map
Trace frameworks, module families, evidence, intelligence, and customer outputs. Select a pipeline, expand a node, drag to orbit, or scroll to zoom.
Shared scenario identity, stage gates, evidence semantics, observables, knowledge bindings, and artifacts.
For air-gapped, regulated, or sovereignty-sensitive environments, MSC can be deployed as a self-contained virtual appliance on Azure Local (formerly Azure Stack HCI), Hyper-V, or VMware infrastructure.
| Feature | Cloud (SWA) | On-Prem Appliance |
|---|---|---|
| Deployment | Azure Static Web Apps | VM on Azure Local / Hyper-V / VMware |
| Internet Required | Yes (always) | Optional (air-gap supported) |
| Scheduling | Azure Functions timer triggers | Hangfire on local server |
| Data Residency | Azure region | Customer premises (full control) |
| Multi-User | Via Entra ID | Local accounts or AD/Entra |
| AI Integration | Azure OpenAI / external | Optional local LLM (Ollama/vLLM) |