What you need to know
When does AMA-based OTLP ingestion require the microsoft.applicationId resource attribute?
Potentially affected
Nonproduction evaluations of preview AMA-based OTLP ingestion using a DCR that references Application Insights.
DSE recommendation
Map the application attribute to the intended Application Insights resource before evaluating whether the test data is correctly separated.
Source facts
AMA-based OTLP ingestion is preview and Microsoft does not recommend it for production workloads. Its application configuration requires microsoft.applicationId when Application Insights created the DCR or when a manually created DCR includes an Application Insights ID. The attribute uses the GUID after InstrumentationKey= in the connection string, enabling separation by Application Insights resource. The source specifies AMA 1.38.1 or later on Windows and 1.37.0 or later on Linux. Microsoft Learn.
Applicability
Use this attribution check in a bounded preview evaluation with an Application Insights-linked DCR. Do not extend the attribute requirement to every manually orchestrated ingestion arrangement without checking whether that linkage exists.
DSE recommendation
Map the application attribute to the intended Application Insights resource before evaluating whether the test data is correctly separated. Have the application owner compare the actual runtime attribute with the chosen resource, rather than copying an identifier from another environment. Record the DCR linkage and installed agent version with the test configuration. Keep this identity mapping separate from network reachability.
Verification
Send an approved recognizable test event and inspect the configured attribute and expected Application Insights destination. Where two applications share infrastructure, test each intended attribution separately and check for misplaced records. Preserve the event identity, configuration and observed destination without copying unnecessary connection details into broadly shared evidence. Accept the mapping only after the intended resource can be distinguished from another test environment.
Official references
Microsoft Learn: AMA OTLP ingestion, preview. Source reviewed September 9, 2026.
Review the official source
Ingest OTLP Data into Azure Monitor with AMA (Preview) - Azure Monitor | Microsoft Learn · Verified September 9, 2026
Need help applying this guidance safely?
DSE can help confirm applicability, protect service continuity, and validate the result across physical security and IT systems.
Talk with DSE