Enable AOT compatibility validation for Azure Monitor OpenTelemetry Exporter

[xiang17]

Summary

• Remove AotCompatOptOut from Azure Monitor OpenTelemetry Exporter.
• Enable the repository's AOT analyzers and CI Native AOT publish check.
• Suppress IL2072 for the existing Live Metrics property traversal, where public properties on the known DocumentIngress model hierarchy are explicitly preserved.

Previously, the CI compatibility script detected the opt-out and returned success without analyzing or publishing the exporter.

Testing

• Ran Check-AOT-Compatibility.ps1 for the exporter with no IL warnings.
• Published the exporter AOT compatibility test app for win-x64.
• Ran the generated native executable successfully.
• Confirmed:
  • AotCompatOptOut=false
  • AotAnalyzersOptOut=false
  • IsAotCompatible=true

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
12 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[Copilot]

🟡 Changes recommended

The suppression hides unsafe reflection over unpreserved nested property types.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Enables Native AOT validation for the Azure Monitor OpenTelemetry Exporter.

Changes:

• Removes the AOT compatibility opt-out.
• Suppresses an existing trimming warning in Live Metrics filtering.
• Documents the validation change.

File summaries

File	Description
Filter.cs	Adds the IL2072 suppression.
Azure.Monitor.OpenTelemetry.Exporter.csproj	Enables repository AOT checks.
CHANGELOG.md	Records AOT validation support.

Review details

• Files reviewed: 3/3 changed files
• Comments generated: 1
• Review effort level: Balanced

---

💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.