{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-193-retain-relevant-nat-gateway-health-history-with-the-incident-record/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260917-193-retain-relevant-nat-gateway-health-history-with-the-incident-record/", "slug": "dse-20260917-193-retain-relevant-nat-gateway-health-history-with-the-incident-record", "url": "https://update.dsesecurity.com/updates/dse-20260917-193-retain-relevant-nat-gateway-health-history-with-the-incident-record/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260917-193-retain-relevant-nat-gateway-health-history-with-the-incident-record.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-193-retain-relevant-nat-gateway-health-history-with-the-incident-record/" }, "title": "Retain relevant NAT Gateway health history with the incident record", "summary": "Preserve the resource-health timeline while it remains available in the portal.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "network-infrastructure", "label": "Networks & infrastructure", "alt": "Resilient network core with engineered blue and gold data paths.", "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "cybersecurity", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "slug": "networks-infrastructure", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "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-17T16:31:47+00:00", "modified_at": "2026-09-17T16:46:30+00:00", "reviewed_on": "2026-09-17", "reading_minutes": 1, "word_count": 204, "potentially_affected": "Use this review when investigating an outbound-connectivity incident involving NAT Gateway. Identify the correct gateway and incident interval. Keep its resource-health observations distinct from application logs, client tests and the state of the remote destination.", "dse_recommendation": "DSE recommends attaching the relevant resource-health timeline to the incident record while the documented history is available.", "primary_source": { "name": "Azure NAT Gateway Resource Health - Azure NAT Gateway | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/nat-gateway/resource-health", "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

Microsoft’s NAT Gateway Resource Health guide says the health-history section exposes up to 30 days of events. Resource health is evaluated from the gateway endpoint’s datapath availability. The guidance also describes alerts for changes to Degraded or Unavailable states, giving operators a separate notification path from manually reviewing history. Microsoft Learn.

\n

Applicability

\n

Use this review when investigating an outbound-connectivity incident involving NAT Gateway. Identify the correct gateway and incident interval. Keep its resource-health observations distinct from application logs, client tests and the state of the remote destination.

\n

DSE recommendation

\n

DSE recommends attaching the relevant resource-health timeline to the incident record while the documented history is available. Record the resource identity and observation time, and compare the events with application symptoms. Review whether a suitable health-state alert and responsible recipient are configured. Choose incident-evidence retention according to the organization’s approved requirements.

\n

Verification

\n

Reconcile the retained health events with notification timestamps and representative application observations. Confirm the record identifies the gateway and time zone clearly enough for another operator to repeat the comparison. Preserve discrepancies as findings. An Available resource state should not be presented as proof that every application destination or authentication path was working.

\n

Official references

\n

Microsoft Learn: Azure NAT Gateway Resource Health.

", "content_text": "Source facts\nMicrosoft’s NAT Gateway Resource Health guide says the health-history section exposes up to 30 days of events. Resource health is evaluated from the gateway endpoint’s datapath availability. The guidance also describes alerts for changes to Degraded or Unavailable states, giving operators a separate notification path from manually reviewing history. Microsoft Learn.\nApplicability\nUse this review when investigating an outbound-connectivity incident involving NAT Gateway. Identify the correct gateway and incident interval. Keep its resource-health observations distinct from application logs, client tests and the state of the remote destination.\nDSE recommendation\nDSE recommends attaching the relevant resource-health timeline to the incident record while the documented history is available. Record the resource identity and observation time, and compare the events with application symptoms. Review whether a suitable health-state alert and responsible recipient are configured. Choose incident-evidence retention according to the organization’s approved requirements.\nVerification\nReconcile the retained health events with notification timestamps and representative application observations. Confirm the record identifies the gateway and time zone clearly enough for another operator to repeat the comparison. Preserve discrepancies as findings. An Available resource state should not be presented as proof that every application destination or authentication path was working.\nOfficial references\nMicrosoft Learn: Azure NAT Gateway Resource Health.", "content_markdown": "## Source facts\n\nMicrosoft’s NAT Gateway Resource Health guide says the health-history section exposes up to 30 days of events. Resource health is evaluated from the gateway endpoint’s datapath availability. The guidance also describes alerts for changes to Degraded or Unavailable states, giving operators a separate notification path from manually reviewing history. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/nat-gateway/resource-health).\n\n## Applicability\n\nUse this review when investigating an outbound-connectivity incident involving NAT Gateway. Identify the correct gateway and incident interval. Keep its resource-health observations distinct from application logs, client tests and the state of the remote destination.\n\n## DSE recommendation\n\nDSE recommends attaching the relevant resource-health timeline to the incident record while the documented history is available. Record the resource identity and observation time, and compare the events with application symptoms. Review whether a suitable health-state alert and responsible recipient are configured. Choose incident-evidence retention according to the organization’s approved requirements.\n\n## Verification\n\nReconcile the retained health events with notification timestamps and representative application observations. Confirm the record identifies the gateway and time zone clearly enough for another operator to repeat the comparison. Preserve discrepancies as findings. An Available resource state should not be presented as proof that every application destination or authentication path was working.\n\n## Official references\n\n[Microsoft Learn: Azure NAT Gateway Resource Health](https://learn.microsoft.com/en-us/azure/nat-gateway/resource-health)." }, "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-20260917-193-retain-relevant-nat-gateway-health-history-with-the-incident-record/", "url": "https://update.dsesecurity.com/updates/dse-20260917-193-retain-relevant-nat-gateway-health-history-with-the-incident-record/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-17" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260917-193-retain-relevant-nat-gateway-health-history-with-the-incident-record/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Retain relevant NAT Gateway health history with the incident record", "item": "https://update.dsesecurity.com/updates/dse-20260917-193-retain-relevant-nat-gateway-health-history-with-the-incident-record/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260917-193-retain-relevant-nat-gateway-health-history-with-the-incident-record/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260917-193-retain-relevant-nat-gateway-health-history-with-the-incident-record/", "url": "https://update.dsesecurity.com/updates/dse-20260917-193-retain-relevant-nat-gateway-health-history-with-the-incident-record/", "headline": "Retain relevant NAT Gateway health history with the incident record", "description": "Preserve the resource-health timeline while it remains available in the portal.", "abstract": "Preserve the resource-health timeline while it remains available in the portal.", "articleBody": "Source facts\nMicrosoft’s NAT Gateway Resource Health guide says the health-history section exposes up to 30 days of events. Resource health is evaluated from the gateway endpoint’s datapath availability. The guidance also describes alerts for changes to Degraded or Unavailable states, giving operators a separate notification path from manually reviewing history. Microsoft Learn.\nApplicability\nUse this review when investigating an outbound-connectivity incident involving NAT Gateway. Identify the correct gateway and incident interval. Keep its resource-health observations distinct from application logs, client tests and the state of the remote destination.\nDSE recommendation\nDSE recommends attaching the relevant resource-health timeline to the incident record while the documented history is available. Record the resource identity and observation time, and compare the events with application symptoms. Review whether a suitable health-state alert and responsible recipient are configured. Choose incident-evidence retention according to the organization’s approved requirements.\nVerification\nReconcile the retained health events with notification timestamps and representative application observations. Confirm the record identifies the gateway and time zone clearly enough for another operator to repeat the comparison. Preserve discrepancies as findings. An Available resource state should not be presented as proof that every application destination or authentication path was working.\nOfficial references\nMicrosoft Learn: Azure NAT Gateway Resource Health.", "datePublished": "2026-09-17T16:31:47+00:00", "dateModified": "2026-09-17T16:46:30+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260917-193-retain-relevant-nat-gateway-health-history-with-the-incident-record/" }, "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-20260917-193-retain-relevant-nat-gateway-health-history-with-the-incident-record/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Retain relevant NAT Gateway health history with the incident record" }, "articleSection": [ "Cybersecurity", "Networks & Infrastructure" ], "keywords": [ "Cybersecurity", "Networks & Infrastructure", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "wordCount": 204, "timeRequired": "PT1M", "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": "Azure NAT Gateway Resource Health - Azure NAT Gateway | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/nat-gateway/resource-health" } } ] } }