Inspect the individual connector behind an Intune health summary

Source facts

Intune connector status uses the last successful synchronization for service connections and expiry timestamps for certificates or credentials. Where several connectors share a type, the summary shows the least healthy one. Microsoft warns that a connector can report Healthy or Connected while not functioning correctly. Selecting the connector opens its own management page for further inspection. Microsoft Learn.

Applicability

Identify the actual connector instance used by the failing workflow. Separate an integration’s synchronization or credential condition from a wider Microsoft service incident.

DSE recommendation

Record the connector type, instance, last relevant synchronization, and credential expiry without copying the credential itself. Open the underlying connector record before renewing or replacing anything. Have the integration owner compare the failed transaction with the connector’s own evidence. Do not clear an incident solely because the tenant overview contains a reassuring label.

Verification

Rehearse an approved representative operation through the intended integration and check its result at the receiving service. If the grouped status is unhealthy, identify which member produced that result rather than assuming all instances failed. If the label remains healthy while the operation fails, preserve connector-specific logs and the failure time for escalation. Record the actual operation’s success separately from the overview status so future troubleshooting can distinguish a useful health signal from end-to-end proof.

Official references

Microsoft Learn: About the Microsoft Intune tenant status page.