
seoheel.92373 (Customer) asked a question.
Inquiry Regarding OPA/OPS VM Deployment and High Availability (HA) Support
Hello,
We are currently reviewing the VM server architecture for deploying the Okta Provisioning Agent (OPA) and Okta On-prem SCIM Server (OPS) in a customer environment.
The customer has asked whether a two-VM high availability (HA) configuration is mandatory and whether VMware virtualization HA features can be used as an alternative.
We would like to confirm the officially supported deployment options and recommended HA architecture.
[Planned Deployment Environment]
- Components: OPA + OPS (Traditional On-premises Provisioning architecture)
- Deployment Option: Installing both OPA and OPS on a single VM server
- HA Options Under Consideration: Deploying two VM servers for redundancy or utilizing VMware virtualization HA features
[Findings from Okta Official Documentation]
According to Okta's official documentation, the HA configuration requires installing additional OPA and SCIM Connector components on separate servers. The system requirements documentation also specifies a dedicated Linux server for OPS installation.
However, we could not clearly determine whether the proposed single-VM deployment is officially supported or whether VMware virtualization HA features can replace application-level redundancy.
We would appreciate your clarification on the following questions.
[Questions]
1. Single-VM Deployment and HA Requirements
- Is it officially supported to install and operate both OPA and OPS on the same VM server?
- Is a two-VM redundant configuration mandatory for all deployments, or is it required only when implementing high availability?
2. VMware Virtualization HA as an Alternative
- Is a deployment consisting of OPA and OPS on a single VM, protected by VMware HA, officially supported by Okta?
- Can VMware virtualization features, such as VMware HA, vMotion, and Live Migration, replace a separate application-level HA configuration for OPA/OPS?
3. Application-Level High Availability Requirements
- Is the HA architecture described in Okta's documentation intended to protect against both physical server failures and OPA/OPS application-level failures?
- If application-level redundancy is required, what is the officially supported and recommended server architecture?
- Do the HA requirements described in the official documentation for SCIM Connector-based deployments also apply to the OPA + OPS configuration currently under consideration?
If possible, please provide confirmation of the officially supported configurations, recommended architecture, and relevant Okta documentation for each question.
[References – Okta Official Documentation]
- On-premises Provisioning Architecture
- https://help.okta.com/en-us/content/topics/provisioning/opp/opp-architecture.htm
- System Requirements for On-premises Connector – Generic Databases
- https://help.okta.com/en-us/content/topics/provisioning/opc/on-prem-generic-db-sys-req.htm
Thank you for your assistance.

Hello @seoheel.92373 (Customer) Separate servers isolate the two components' failures, resources, lifecycles, and network paths, which makes the deployment easier to operate, scale, and support.
OPA and OPS have different roles. OPA relays provisioning requests from Okta's cloud to the on-premises network. OPS is the SCIM endpoint that receives those requests and writes to your target system. Each role has its own network, resource, and maintenance needs, so combining them on one host creates shared points of failure.
Use one server for OPA and a separate server for OPS, following the separate-server topology described in the On-premises Provisioning Architecture documentation. The main technical reasons are: