- Verify if the network latency between the Federation Proxy Server and the Federation Servers falls within the acceptable range. Refer to the Monitoring Section for trending values of the "Token Request Latency". A latency greater than [1500 ms] should be considered as high latency.If high latency is observed, ensure the network between AD FS and AD FS Proxy servers does not have any connectivity issues.
- Ensure Federation Servers are not overloaded with authentication requests. Monitoring Section provides trending views for Token Requests per second, CPU utilization and Memory consumption.
- If the above items have been verified and this issue is still seen, adjust the congestion avoidance setting on each of the Federation Proxy Servers as per the guidance from the related links.
Using Microsoft Network Monitor, validate that network traffic is mirrored from the Domain Controllers to the Gateway. For ...
Using our identity platform allows you to access a wealth of powerful data and functionality through the various Microsoft ...
Using {0} with Windows Hello or a PIN makes signing in to apps easier. If you can't do this right now, we'll still add your ...
Vault name must be between 3-24 alphanumeric characters. The name must begin with a letter, end with a letter or digit, and ...
Verify if the network latency between the Federation Proxy Server and the Federation Servers falls within the acceptable ...
Verify if the service account used to run synchronization service exists in your Active Directory. 2. Verify that the service ...
Verify if the service account used to run synchronization service exists in your Active Directory. 2. Verify that the service ...
Verify that port mirroring is configured properly on your network devices. For more information on ATA's requirements for ...
Verify the syslog server is only forwarding required events to the Gateway. Forward some of the events to another Gateway. ...