Connectivity Issues to Okta From Azure Hosted Services
Last Updated:
Overview
Azure Source Network Address Translation (SNAT) port limits cause intermittent connectivity issues when accessing Okta from Azure network-hosted services. Consult Azure Support to resolve this limitation.
When accessing Okta from Azure network-hosted services, such as Azure Kubernetes Service or Azure App Service, intermittent slow response times or timeout errors occur. Accessing the same Okta resources from non-Azure networks remains unaffected.
The symptoms can include:
- Intermittent slow response times.
- Intermittent 5xx or Bad Gateway errors.
- Intermittent timeout error messages.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Inbound Connections From Azure Services
Cause
According to the Outbound connections in Azure page, Azure uses Source Network Address Translation (SNAT) and load balancers to communicate with public IP addresses. Azure initially allocates 128 SNAT ports to each instance for some Azure technologies. The SNAT port limit affects opening connections to the same address and port combination.
Solution
How is the Azure SNAT client port limitation resolved?
Due to the limitation on the number of Azure SNAT client ports, customers experiencing this issue are advised to consult with Azure Support for a resolution.
