{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-155-inspect-the-individual-connector-behind-an-intune-health-summary/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260909-155-inspect-the-individual-connector-behind-an-intune-health-summary/", "slug": "dse-20260909-155-inspect-the-individual-connector-behind-an-intune-health-summary", "url": "https://update.dsesecurity.com/updates/dse-20260909-155-inspect-the-individual-connector-behind-an-intune-health-summary/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260909-155-inspect-the-individual-connector-behind-an-intune-health-summary.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-155-inspect-the-individual-connector-behind-an-intune-health-summary/" }, "title": "Inspect the individual connector behind an Intune health summary", "summary": "What does a connector health label establish about a failing integration?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "identity-cloud", "label": "Identity & cloud", "alt": "Governed cloud identity system with connected service and lifecycle nodes.", "card_url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "business-continuity", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-09-10T00:29:21+00:00", "modified_at": "2026-09-10T00:55:35+00:00", "reviewed_on": "2026-09-09", "reading_minutes": 2, "word_count": 229, "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.", "primary_source": { "name": "About the Microsoft Intune tenant status page - Microsoft Intune | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/intune/governance/tenant-status", "published_on": null, "authority": "Microsoft Learn" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Source facts

\n

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.

\n

Applicability

\n

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

\n

DSE recommendation

\n

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.

\n

Verification

\n

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.

\n

Official references

\n

Microsoft Learn: About the Microsoft Intune tenant status page.

", "content_text": "Source facts\nIntune 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.\nApplicability\nIdentify the actual connector instance used by the failing workflow. Separate an integration’s synchronization or credential condition from a wider Microsoft service incident.\nDSE recommendation\nRecord 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.\nVerification\nRehearse 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.\nOfficial references\nMicrosoft Learn: About the Microsoft Intune tenant status page.", "content_markdown": "## Source facts\n\nIntune 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).\n\n## Applicability\n\nIdentify the actual connector instance used by the failing workflow. Separate an integration’s synchronization or credential condition from a wider Microsoft service incident.\n\n## DSE recommendation\n\nRecord 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.\n\n## Verification\n\nRehearse 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.\n\n## Official references\n\n[Microsoft Learn: About the Microsoft Intune tenant status page](https://learn.microsoft.com/en-us/intune/governance/tenant-status)." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/dse-20260909-155-inspect-the-individual-connector-behind-an-intune-health-summary/", "url": "https://update.dsesecurity.com/updates/dse-20260909-155-inspect-the-individual-connector-behind-an-intune-health-summary/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-09" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260909-155-inspect-the-individual-connector-behind-an-intune-health-summary/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Inspect the individual connector behind an Intune health summary", "item": "https://update.dsesecurity.com/updates/dse-20260909-155-inspect-the-individual-connector-behind-an-intune-health-summary/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260909-155-inspect-the-individual-connector-behind-an-intune-health-summary/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260909-155-inspect-the-individual-connector-behind-an-intune-health-summary/", "url": "https://update.dsesecurity.com/updates/dse-20260909-155-inspect-the-individual-connector-behind-an-intune-health-summary/", "headline": "Inspect the individual connector behind an Intune health summary", "description": "What does a connector health label establish about a failing integration?", "abstract": "What does a connector health label establish about a failing integration?", "articleBody": "Source facts\nIntune 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.\nApplicability\nIdentify the actual connector instance used by the failing workflow. Separate an integration’s synchronization or credential condition from a wider Microsoft service incident.\nDSE recommendation\nRecord 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.\nVerification\nRehearse 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.\nOfficial references\nMicrosoft Learn: About the Microsoft Intune tenant status page.", "datePublished": "2026-09-10T00:29:21+00:00", "dateModified": "2026-09-10T00:55:35+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260909-155-inspect-the-individual-connector-behind-an-intune-health-summary/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/dse-20260909-155-inspect-the-individual-connector-behind-an-intune-health-summary/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/identity-cloud-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Inspect the individual connector behind an Intune health summary" }, "articleSection": [ "Business Continuity", "IT" ], "keywords": [ "Business Continuity", "IT", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 229, "timeRequired": "PT2M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "About the Microsoft Intune tenant status page - Microsoft Intune | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/intune/governance/tenant-status" } } ] } }