Overview

Okta Access Gateway (OAG) provides a virtual machine image built for deployment in Microsoft Azure. This image also deploys successfully in Hyper-V environments without modification, and Okta extends support coverage to issues arising in both environments.

Applies To

• Okta Access Gateway (OAG)
• Microsoft Azure virtual machine image
• Hyper-V virtual environments
• Okta Identity Engine (OIE)
• Okta Classic Engine

Can the Azure Virtual Machine Image Deploy Directly to Hyper-V?

The Okta Access Gateway virtual machine image, originally built for Microsoft Azure, deploys directly into Hyper-V environments. No modification to the image itself is necessary to achieve compatibility between the two platforms.

What Changes Are Required to the Image Before Using It in Hyper-V?

No changes are required. Administrators use the same Azure virtual machine image for Hyper-V deployments as they use for Azure deployments.

Okta Provides Support for Issues Arising in Both Hyper-V and Azure Environments

Okta provides support coverage for issues that arise from use of the Okta Access Gateway image.

For guidance on connecting a disk to Hyper-V, modifying Hyper-V network configurations, or resolving any inquiries and issues specific to the Hyper-V environment, please contact Microsoft support.

Which logs should be collected for troubleshooting?

Please collect the Okta logs, error messages, screenshots, and the specific steps followed.

Related References

• Okta Access Gateway
• Okta Access Gateway Shows "Too many redirects" Error On Newly Deployed Node
• Microsoft Azure deployment tasks
• Use local resources on Hyper‑V with VMConnect 
• Add storage to Hyper‑V hosts and clusters