# Inspect the individual connector behind an Intune health summary

> What does a connector health label establish about a failing integration?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-155-inspect-the-individual-connector-behind-an-intune-health-summary/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:29:21+00:00
- Modified: 2026-09-10T00:55:35+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, IT
- Reading time: 2 minutes

## What you need to know

What does a connector health label establish about a failing integration?

## Potentially affected

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.

## Article

## 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](https://learn.microsoft.com/en-us/intune/governance/tenant-status).

## 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](https://learn.microsoft.com/en-us/intune/governance/tenant-status).

## Primary reference

- Name: About the Microsoft Intune tenant status page - Microsoft Intune | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/intune/governance/tenant-status
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Inspect the individual connector behind an Intune health summary,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-155-inspect-the-individual-connector-behind-an-intune-health-summary/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.