Intune Certificate Connectors Test

For Microsoft Intune to support use of certificates for authentication and the signing and encryption of email using S/MIME, administrators use Certificate Connectors. Certificate Connector is installed on an on-premises server to help deliver and manage certificates for Intune-managed devices. Intune supports installing of multiple instances of the connector in a tenant, and each instance can support different features. If multiple connectors that support different features are used, certificate requests are always routed to a relevant connector. The certificate connectors streamline the issuance and management of certificates for devices enrolled in Intune. They help automate the process of requesting, issuing, and distributing certificates to managed devices, ensuring secure access and communication.

If any connector becomes inactive, then the certificates will not be issued to the enrolled devices. As a result, users will not be able to secure access the Intune-managed devices. To avoid such inconveniences, administrators should be able to quickly spot those connectors and investigate the reasons for the same before user experience suffers. The Intune Certificate Connectors test can help administrators in this regard!

This test auto-discovers the connector instances used for Intune, and for each connector instance, reports the current status. This helps administrators to identify active and inactive connector instances instantly.

Target of the Test: Microsoft Azure Intune

Agent deploying the test: A remote agent

Output of the test: One set of results for each connector instance used for the Azure Intune

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 Azure 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 Azure 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.
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

Connector state

Indicates the current status of this connector instance.

The values reported by this measure and its numeric equivalents are mentioned in the table below:

Measure Value	Numeric Value
State not available	0
Active	1
Inactive	2

Note:

By default, this measure reports the Measure Values listed in the table above to indicate the current state of each connector. The graph of this measure however, is represented using the numeric equivalents only - 0 to 2.