ADFS Synthetic Status Test

An unavailable/latent AD FS server can either delay or deny users access to critical applications. This is why, it is important that administrators are promptly notified when the AD FS server is inaccessible / not responsive.

This test emulates a user connecting to the AD FS server to have a request authenticated. In the process, the test reports the availability of the server and its responsiveness to authentication requests.

Target of the test : An AD FS server

Agent deploying the test : An external agent.

Outputs of the test : One set of results for the AD FS server being monitored

Configurable parameters for the test
Parameters Description

Test Period

How often should the test be executed.


The host for which the test is to be configured.


The port at which the AD FS server listens.

Base URI

Specify the URL to connect to the AD FS server.


The relying party identifier uniquely identifies an AD FS-federated application so that another claims provider can authenticate users seeking access to the application. To fully emulate an authentication request to the AD FS server, the test needs to connect to the server as an AD FS-federated application. For this, you need to configure the test with a valid relying party Identifier.

Username and Password

The test needs to be configured with the login credentials that the server should authenticate. Specify these credentials against Username and Password.

Measurements made by the test
Measurement Description Measurement Unit Interpretation


Indicates whether/not the ADFS server is available.


The value 100 for this measure indicates that the server is available, and the value 0 indicates that it is not.

Response time

Indicates the average time taken by the server to authenticate a request.


A high value for this measure is indicative of poor responsiveness, which in turn can cause delays in authentication.