# Match platform-metric export placement to the destination type

> Can a platform-metric export rule send resources from other regions to its chosen destination?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-163-match-platform-metric-export-placement-to-the-destination-type/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:29:13+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

Can a platform-metric export rule send resources from other regions to its chosen destination?

## 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.

## Article

## Source facts

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](https://learn.microsoft.com/en-us/azure/azure-monitor/data-collection/metrics-export-create).

## Applicability

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.

## DSE recommendation

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.

## Verification

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.

## Official references

[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.

## Primary reference

- Name: Metrics export using data collection rules - Azure Monitor | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/azure-monitor/data-collection/metrics-export-create
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Match platform-metric export placement to the destination type,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-163-match-platform-metric-export-placement-to-the-destination-type/
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.