{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-163-match-platform-metric-export-placement-to-the-destination-type/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260909-163-match-platform-metric-export-placement-to-the-destination-type/", "slug": "dse-20260909-163-match-platform-metric-export-placement-to-the-destination-type", "url": "https://update.dsesecurity.com/updates/dse-20260909-163-match-platform-metric-export-placement-to-the-destination-type/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260909-163-match-platform-metric-export-placement-to-the-destination-type.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-163-match-platform-metric-export-placement-to-the-destination-type/" }, "title": "Match platform-metric export placement to the destination type", "summary": "Can a platform-metric export rule send resources from other regions to its chosen destination?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "continuity-recovery", "label": "Continuity & recovery", "alt": "Paired infrastructure paths converging on a stable recovered service.", "card_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-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:13+00:00", "modified_at": "2026-09-10T00:55:35+00:00", "reviewed_on": "2026-09-09", "reading_minutes": 2, "word_count": 235, "potentially_affected": "Supported Azure resources using platform-telemetry DCRs to export metrics to Log Analytics, Storage or Event Hubs.", "dse_recommendation": "Draw the resource, DCR and destination region relationship before selecting the metric-export destination.", "primary_source": { "name": "Metrics export using data collection rules - Azure Monitor | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/azure-monitor/data-collection/metrics-export-create", "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

Platform-metric export to Storage or Event Hubs requires the monitored resource, DCR and destination to share a region. Log Analytics differs: its workspace and DCR must share a region, but monitored resources may be elsewhere. A metrics-export DCR permits one destination type; multiple destinations require multiple DCRs. Storage and Event Hubs also require a DCR managed identity with destination write permission. Microsoft Learn.

\n

Applicability

\n

Confirm the documented resource-type and regional support for this platform-telemetry export feature. This placement rule should not be inferred from another log-export mechanism or from the location of the resource group containing the configuration.

\n

DSE recommendation

\n

Draw the resource, DCR and destination region relationship before selecting the metric-export destination. Ask the monitoring owner to distinguish a centralized Log Analytics requirement from a regional Storage or Event Hubs requirement. Include the specific destination permission in the design review. If the desired topology violates the documented placement rule, resolve the architecture rather than repeatedly recreating the same incompatible association.

\n

Verification

\n

Inspect the actual locations and destination identity grant before testing a representative supported resource. Confirm new metric records reach the intended destination and preserve the corresponding configuration evidence. Where multiple export paths are intended, verify each separately and identify any overlapping collection. Record an unsupported type or region as a design limitation, not a presumed temporary ingestion delay.

\n

Official references

\n

Microsoft Learn: Metrics export using data collection rules. Source reviewed September 9, 2026.

", "content_text": "Source facts\nPlatform-metric export to Storage or Event Hubs requires the monitored resource, DCR and destination to share a region. Log Analytics differs: its workspace and DCR must share a region, but monitored resources may be elsewhere. A metrics-export DCR permits one destination type; multiple destinations require multiple DCRs. Storage and Event Hubs also require a DCR managed identity with destination write permission. Microsoft Learn.\nApplicability\nConfirm the documented resource-type and regional support for this platform-telemetry export feature. This placement rule should not be inferred from another log-export mechanism or from the location of the resource group containing the configuration.\nDSE recommendation\nDraw the resource, DCR and destination region relationship before selecting the metric-export destination. Ask the monitoring owner to distinguish a centralized Log Analytics requirement from a regional Storage or Event Hubs requirement. Include the specific destination permission in the design review. If the desired topology violates the documented placement rule, resolve the architecture rather than repeatedly recreating the same incompatible association.\nVerification\nInspect the actual locations and destination identity grant before testing a representative supported resource. Confirm new metric records reach the intended destination and preserve the corresponding configuration evidence. Where multiple export paths are intended, verify each separately and identify any overlapping collection. Record an unsupported type or region as a design limitation, not a presumed temporary ingestion delay.\nOfficial references\nMicrosoft Learn: Metrics export using data collection rules. Source reviewed September 9, 2026.", "content_markdown": "## Source facts\n\nPlatform-metric export to Storage or Event Hubs requires the monitored resource, DCR and destination to share a region. Log Analytics differs: its workspace and DCR must share a region, but monitored resources may be elsewhere. A metrics-export DCR permits one destination type; multiple destinations require multiple DCRs. Storage and Event Hubs also require a DCR managed identity with destination write permission. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/azure-monitor/data-collection/metrics-export-create).\n\n## Applicability\n\nConfirm the documented resource-type and regional support for this platform-telemetry export feature. This placement rule should not be inferred from another log-export mechanism or from the location of the resource group containing the configuration.\n\n## DSE recommendation\n\nDraw the resource, DCR and destination region relationship before selecting the metric-export destination. Ask the monitoring owner to distinguish a centralized Log Analytics requirement from a regional Storage or Event Hubs requirement. Include the specific destination permission in the design review. If the desired topology violates the documented placement rule, resolve the architecture rather than repeatedly recreating the same incompatible association.\n\n## Verification\n\nInspect the actual locations and destination identity grant before testing a representative supported resource. Confirm new metric records reach the intended destination and preserve the corresponding configuration evidence. Where multiple export paths are intended, verify each separately and identify any overlapping collection. Record an unsupported type or region as a design limitation, not a presumed temporary ingestion delay.\n\n## Official references\n\n[Microsoft Learn: Metrics export using data collection rules](https://learn.microsoft.com/en-us/azure/azure-monitor/data-collection/metrics-export-create). Source reviewed September 9, 2026." }, "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-163-match-platform-metric-export-placement-to-the-destination-type/", "url": "https://update.dsesecurity.com/updates/dse-20260909-163-match-platform-metric-export-placement-to-the-destination-type/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-09" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260909-163-match-platform-metric-export-placement-to-the-destination-type/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Match platform-metric export placement to the destination type", "item": "https://update.dsesecurity.com/updates/dse-20260909-163-match-platform-metric-export-placement-to-the-destination-type/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260909-163-match-platform-metric-export-placement-to-the-destination-type/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260909-163-match-platform-metric-export-placement-to-the-destination-type/", "url": "https://update.dsesecurity.com/updates/dse-20260909-163-match-platform-metric-export-placement-to-the-destination-type/", "headline": "Match platform-metric export placement to the destination type", "description": "Can a platform-metric export rule send resources from other regions to its chosen destination?", "abstract": "Can a platform-metric export rule send resources from other regions to its chosen destination?", "articleBody": "Source facts\nPlatform-metric export to Storage or Event Hubs requires the monitored resource, DCR and destination to share a region. Log Analytics differs: its workspace and DCR must share a region, but monitored resources may be elsewhere. A metrics-export DCR permits one destination type; multiple destinations require multiple DCRs. Storage and Event Hubs also require a DCR managed identity with destination write permission. Microsoft Learn.\nApplicability\nConfirm the documented resource-type and regional support for this platform-telemetry export feature. This placement rule should not be inferred from another log-export mechanism or from the location of the resource group containing the configuration.\nDSE recommendation\nDraw the resource, DCR and destination region relationship before selecting the metric-export destination. Ask the monitoring owner to distinguish a centralized Log Analytics requirement from a regional Storage or Event Hubs requirement. Include the specific destination permission in the design review. If the desired topology violates the documented placement rule, resolve the architecture rather than repeatedly recreating the same incompatible association.\nVerification\nInspect the actual locations and destination identity grant before testing a representative supported resource. Confirm new metric records reach the intended destination and preserve the corresponding configuration evidence. Where multiple export paths are intended, verify each separately and identify any overlapping collection. Record an unsupported type or region as a design limitation, not a presumed temporary ingestion delay.\nOfficial references\nMicrosoft Learn: Metrics export using data collection rules. Source reviewed September 9, 2026.", "datePublished": "2026-09-10T00:29:13+00:00", "dateModified": "2026-09-10T00:55:35+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260909-163-match-platform-metric-export-placement-to-the-destination-type/" }, "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-163-match-platform-metric-export-placement-to-the-destination-type/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Match platform-metric export placement to the destination type" }, "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": 235, "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": "Metrics export using data collection rules - Azure Monitor | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/azure-monitor/data-collection/metrics-export-create" } } ] } }