Windows 365 Devices by User Experience Test

This test ensures that devices maintain optimal performance and responsiveness when connecting to security services and during user sign-in. Delays or poor responsiveness can slow down the application of security policies, delay threat detection, and reduce overall system effectiveness. These performance bottlenecks can leave devices vulnerable to security risks, cause frustration for users, and make it difficult for administrators to identify underlying network or configuration issues. By monitoring these performance indicators, administrators can proactively detect bottlenecks, optimize network and security configurations, and ensure timely policy enforcement, maintaining both security posture and a smooth user experience.

Target of the Test: Microsoft Intune

Agent deploying the test: A remote agent

Output of the test: One set of results for the Intune being monitored

Configurable parameters for the test
Parameters Description

Test Period

How often should the test be executed.

Host

The host for which the test is to be configured.

Tenant ID

Specify the Directory ID of the Azure AD tenant to which the target subscription belongs. To know how to determine the Directory ID, refer to Configuring the eG Agent to Monitor Microsoft Intune Using Intune REST API.

Client ID, Client Password, and Confirm Password

To connect to the target subscription, the eG agent requires an Access token in the form of an Application ID and the client secret value. For this purpose, you should register a new application with the Azure AD tenant. To know how to create such an application and determine its Application ID and client secret, refer to Configuring the eG Agent to Monitor Microsoft Intune Using Intune REST API. Specify the Application ID of the created Application in the Client ID text box and the client secret value in the Client Password text box. Confirm the Client Password by retyping it in the Confirm Password text box.

ProxyHost and ProxyPort

In some environments, all communication with the Azure cloud be routed through a proxy server. In such environments, you should make sure that the eG agent connects to the cloud via the proxy server and collects metrics. To enable metrics collection via a proxy, specify the IP address of the proxy server and the port at which the server listens against the ProxyHost and ProxyPort parameters. By default, these parameters are set to none, indicating that the eG agent is not configured to communicate via a proxy, by default.

ProxyUsername, ProxyPassword, Confirm Password

If the proxy server requires authentication, then, specify a valid proxy user name and password in the Proxy Username and Proxy Password parameters, respectively. Then, confirm the password by retyping it in the Confirm Password text box.

If no proxy server is used, or if the proxy server used does not require authentication, then the default setting - none - of these parameters, need not be changed.

Is DD Required for Good RTT

By default, this flag is set to No. This implies that by default, detailed metrics will not be available for the Devices with good RTT measure of this test. To enable detailed diagnosis for this measure, you can set this flag to Yes. In this case, you will be able to view the complete details of all devices that are experiencing good round-trip time (RTT), as part of detailed diagnostics.

Is DD Required for Good Signin

By default, this flag is set to No. This implies that by default, detailed metrics will not be available for the Devices with good sign-in duration measure of this test. To enable detailed diagnosis for this measure, you can set this flag to Yes. In this case, you will be able to view the complete details of all devices where users successfully signed-in within the permissible duration, as part of detailed diagnostics.

Is DD Required for Average RTT

By default, this flag is set to No. This implies that by default, detailed metrics will not be available for the Devices with average RTT measure of this test. To enable detailed diagnosis for this measure, you can set this flag to Yes. In this case, you will be able to view the complete details of all devices that are experiencing average round-trip time (RTT), as part of detailed diagnostics.

Is DD Required for Average Signin

By default, this flag is set to No. This implies that by default, detailed metrics will not be available for the Devices with average sign-in duration measure of this test. To enable detailed diagnosis for this measure, you can set this flag to Yes. In this case, you will be able to view the complete details of all devices where users experienced average sign-in duration, as part of detailed diagnostics.

DD Frequency

Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD frequency.

Detailed Diagnosis

To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.

The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability
  • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.
Measurements reported by the test
Measurement Description Measurement Unit Interpretation

Number of devices with poor RTT

Indicates the total number of devices that are experiencing poor round-trip time (RTT).

Number

A high value for this measure may indicate network performance issues, latency in applying security policies, or potential exposure due to delayed threat detection and response.

Number of devices with good RTT

Indicates the total number of devices that are experiencing good round-trip time (RTT).

Number

Ideally, a high value is desired for this measure.

Number of devices with average RTT

Indicates the total number of devices that are experiencing average round-trip time (RTT).

Number

 

Devices with poor RTT

Indicates the percentage of devices that are experiencing poor round-trip time (RTT).

Percent

A low value is desired for this measure.

The detailed diagnosis of this measure displays the device ID, device name, user name, the timestamp at which the device was last used, round-trip time, median latency, UDP usage, bandwidth, average sign-in duration, connection gateway, protocol used, and client IP.

Devices with average RTT

Indicates the percentage of devices that are experiencing average round-trip time (RTT).

Percent

The detailed diagnosis of this measure displays the device ID, device name, user name, the timestamp at which the device was last used, round-trip time, median latency, UDP usage, bandwidth, average sign-in duration, connection gateway, protocol used, and client IP.

Devices with good RTT

Indicates the percentage of devices that are experiencing good round-trip time (RTT).

Percent

Ideally, a high value is desired for this measure.

The detailed diagnosis of this measure displays cloud PC ID, device name, user name, the timestamp at which the device was last used, round-trip time, median latency, UDP usage, bandwidth, average sign-in duration, connection gateway, protocol used, and client IP.

Median RTT

Indicates the median round-trip time (RTT) across all devices managed on Microsoft Intune.

Milliseconds

 

95th percentile of RTT

Indicates the round-trip time (RTT) value below which 95 percentage of devices may fall while communicating with security services.

Percent

If the value of this measure is high, it means that many devices are experiencing noticeable delays in applying security policies, receiving updates, or sending telemetry, which could weaken timely threat detection and response.

Number of devices with poor sign-in duration

Indicates the number of devices where users experienced longer sign-in duration.

Number

A high value for this measure may point to performance bottlenecks, misconfigured policies, or security checks causing delays.

Number of devices with good sign-in duration

Indicates the number of devices where users successfully signed-in within the permissible duration.

Number

 

Number of devices with average sign-in duration

Indicates the number of devices where users experienced average sign-in duration.

Number

 

Devices with poor sign-in duration

Indicates the percentage of devices where users experienced longer sign-in duration.

Percent

The detailed diagnosis of this measure displays device ID, device name, user name, the timestamp at which the device was last used, round-trip time, median latency, UDP usage, bandwidth, average sign-in duration, connection gateway, protocol used, and client IP.

Devices with good sign-in duration

Indicates the percentage of devices where users successfully signed-in within the permissible duration.

Percent

The detailed diagnosis of this measure displays the device ID, device name, user name, the timestamp at which the device was last used, round-trip time, median latency, UDP usage, bandwidth, average sign-in duration, connection gateway, protocol used, and client IP.

Devices with average sign-in duration

Indicates the percentage of devices where users experienced average sign-in duration.

Percent

The detailed diagnosis of this measure displays the device ID, device name, user name, the timestamp at which the device was last used, round-trip time, median latency, UDP usage, bandwidth, average sign-in duration, connection gateway, protocol used, and client IP.

Median sign-in duration

Indicates the median time taken for users to sign in across all devices.

Sec

 

95th percentile of sign-in duration

Indicates the sign-in duration below which 95 percentage of devices fall.

Sec