Clarification on Assign Built in User-Assigned Managed Identity to Virtual Machines is optional on Enable Azure Automation Change Tracking using AMA at scale

[nickylian1]

• Documentation mentions for enabling at scale to use Azure Policy Initiative with one of the Policy Definitions Assign Built in User-Assigned Managed identity to virtual machines. Link to documentation: https://learn.microsoft.com/en-us/azure/automation/change-tracking/enable-vms-monitoring-agent?tabs=singlevm%2Cvm#enable-change-tracking-at-scale-using-azure-monitoring-agent

Ask:

• Customers can choose to assign User-Assigned Managed Identity or System-Assigned Managed Identity (default) for AMA. No identity is required for Change Tracking extension.
• Perhaps it helps to clarify mentioning this in documentation.

Thanks.

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: b493df17-cc47-7e08-243a-81529db45092
• Version Independent ID: 655d96db-77dd-df0a-54be-77487158cdfe
• Content: Enable Azure Automation Change Tracking for single machine and multiple machines from the portal.
• Content Source: articles/automation/change-tracking/enable-vms-monitoring-agent.md
• Service: automation
• Sub-service: change-inventory-management
• GitHub Login: @SnehaSudhirG
• Microsoft Alias: sudhirsneha

[AjayBathini-MSFT]

@nickylian1 Thanks for your feedback! We will investigate and update as appropriate.

[SnehaSudhirG]

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. The requested updates have not been made since the creation of this issue, and the timeline for resolution may vary based on resourcing, so we've created an internal work item to incorporate your suggestions. We are closing this issue for now, but feel free to comment here as necessary.

please-close