[bragi92]

🤖 PR Validation — ⚠️ Review suggested

Breaking Changes	Tests
⚠️ None	️✔️ 130/130

⚠️AzureCLI-BreakingChangeTest

⚠️monitor

rule	cmd_name	rule_message	suggest_message
⚠️ 1011 - SubgroupAdd	monitor account trace-container	sub group monitor account trace-container added
⚠️ 1011 - SubgroupAdd	monitor trace-association	sub group monitor trace-association added

Related command
az monitor trace-association create/show/list/delete
az monitor account trace-container create/show/update/wait

Description
Adds preview commands for distributed traces in Azure Monitor, on Microsoft.Monitor 2026-09-03-preview.

• az monitor trace-association create --resource-uri <scope> --azure-monitor-workspace <workspace id> routes the traces of an Application Insights component, a resource group or a subscription to an Azure Monitor workspace. One command covers every scope; --resource-uri picks the API path.
  • If the workspace has no trace container, the command creates it first: 30 days retention and trace metrics Enabled unless --trace-retention-days or --trace-metrics say otherwise. An existing container is never changed, and explicit settings that differ from it fail.
  • Replacing the workspace of a resource group or subscription asks for confirmation (--yes skips it), because everything under that scope stops sending traces to the old workspace unless another association routes them there.
  • After the write, the command reports the workspaces that receive the scope's traces. Associations are additive across a component, its resource group and its subscription.
• show returns the association at exactly the scope, list adds the inherited ones, and delete removes only the scope's own association. Deleting at a resource group or subscription asks for confirmation; deleting where nothing is configured is a no-op.
• az monitor account trace-container create/show/update/wait manage the workspace's trace container. create keeps the current value of any setting it is not given, and uses the defaults above for a new container.

Implementation notes:

• AAZ command models: [monitor] Add trace preview atomic command models aaz#1131. The trace container commands are registered. The per-scope association commands (subscription, resource group, Application Insights component) are generated as unregistered helpers, and the --resource-uri commands dispatch to them.
• Follows the az monitor sli onboarding: generated packages keep empty __init__.py files for args-guided loading. The trace-container create override lives in the operations/latest tree.

Testing Guide

az monitor account trace-container create -g MyResourceGroup -w MyWorkspace
az monitor trace-association create --resource-uri /subscriptions/{subscriptionID}/resourceGroups/MyResourceGroup --azure-monitor-workspace /subscriptions/{subscriptionID}/resourceGroups/MyResourceGroup/providers/Microsoft.Monitor/accounts/MyWorkspace
az monitor trace-association list --resource-uri /subscriptions/{subscriptionID}/resourceGroups/MyResourceGroup/providers/Microsoft.Insights/components/MyAppInsights
az monitor trace-association delete --resource-uri /subscriptions/{subscriptionID}/resourceGroups/MyResourceGroup --yes

• test_monitor_trace_scenario.py: two scenario tests, recorded live in eastus2euap. Trace containers and Application Insights trace associations are only created in regions with traces enabled, and canary regions get them first.
• test_monitor_unittest.py: unit tests for --resource-uri parsing, workspace ID validation and container settings.
• azdev linter monitor passes. flake8 and pylint are clean on the changed files.

History Notes
[Monitor] az monitor trace-association: Add preview command group to route distributed traces from an Application Insights component, resource group or subscription to an Azure Monitor workspace
[Monitor] az monitor account trace-container: Add preview command group to manage the trace container of an Azure Monitor workspace

---

This checklist is used to make sure that common guidelines for a pull request are followed.

• The PR title and description has followed the guideline in Submitting Pull Requests.

• I adhere to the Command Guidelines.

• I adhere to the Error Handling Guidelines.

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[Aditya Pujara (a0x1ab)]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 3 pipeline(s).

[x-engineering-agent]

Hi bragi92,
Since the current milestone time is less than 7 days, this pr will be reviewed in the next milestone.

[Aditya Pujara (a0x1ab)]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 3 pipeline(s).