Enable Change Tracking and Inventory using Azure Monitoring Agent (Preview)

Applies to: ✔️ Windows VMs ✔️ Linux VMs ✔️ Windows Registry ✔️ Windows Files ✔️ Linux Files ✔️ Windows Software

Important

Currently, the policies to enable Change tracking and inventory with Azure monitoring Agent are in preview. For a seamless policy experience, we recommend that you begin by enabling the Microsoft.Compute/AutomaticExtensionUpgradePreview feature flag for your specific subscription. To register for this feature flag, go to Azure portal > Subscriptions > Select specific subscription name. In the Preview features, select Automatic Extension Upgrade Preview and then select Register.

This article describes how you can enable Change Tracking and Inventory for single and multiple Azure Virtual Machines (VMs) from the Azure portal.

Prerequisites

• An Azure subscription. If you don't have one yet, you can activate your MSDN subscriber benefits or sign up for a free account.
• A virtual machine configured in the specified region.

Enable Change Tracking and Inventory

This section provides detailed procedure on how you can enable change tracking on a single VM and multiple VMs.

For a single VM

1. Sign in to Azure portal and navigate to Virtual machines.

   

2. Select the virtual machine for which you want to enable Change Tracking.

3. In the search, enter Change tracking to view the change tracking and inventory page.

   

4. In the Stay up-to-date with all changes layout, select Enable using AMA agent (Recommended) option and Enable.

   It will initiate the deployment and the notification appears on the top right corner of the screen.

   

For multiple VMs

1. Sign in to Azure portal and navigate to Virtual machines.

   

2. Select the virtual machines to which you intend to enable change tracking and select Services > Change Tracking.

   

   Note

   You can select upto 250 virtual machines at a time to enable this feature.

3. In Enable Change Tracking page, select the banner at the top of the page, Click here to try new change tracking and inventory with Azure Monitoring Agent (AMA) experience.

   

4. In Enable Change Tracking page, you can view the list of machines that are enabled, ready to be enabled and the ones that you can't enable. You can use the filters to select the Subscription, Location, and Resource groups. You can select a maximum of three resource groups.

   

5. Select Enable to initiate the deployment.

6. A notification appears on the top right corner of the screen indicating the status of deployment.

Note

It usually takes up to two to three minutes to successfully onboard and enable the virtual machine(s). After you enable a virtual machine for change tracking, you can make changes to the files, registries, or software for the specific VM.

Enable Change Tracking at scale using Azure Monitoring Agent

Using the Deploy if not exist (DINE) policy, you can enable Change tracking with Azure Monitoring Agent at scale and in the most efficient manner.

1. In Azure portal, select Policy.
2. In the Policy|Definitions page, in Authoring, select Definitions
3. In the Definition Type category, select Initiative and in Category, select ChangeTracking andInventory You'll see a list of three policies:
   • Enable ChangeTracking and inventory for Virtual Machine Scale Sets
   • Enable ChangeTracking and inventory for virtual machines
   • Enable ChangeTracking and inventory for Arc-enabled virtual machines
4. Select Enable ChangeTracking and Inventory for virtual machines to enable the change tracking on Azure virtual machines. This initiative consists of three policies:
   • Assign Built in User-Assigned Managed identity to Virtual machines
   • Configure ChangeTracking Extension for Windows virtual machines
   • Configure ChangeTracking Extension for Linux virtual machines
5. Select Assign to assign the policy to a resource group. For example, Assign Built in User-Assigned Managed identity to virtual machines.

   Note

   The Resource group contains virtual machines and when you assign the policy, it will enable change tracking at scale to a resource group. The virtual machines that are on-boarded to the same resource group will automatically have the change tracking feature enabled.

6. In the Enable ChangeTracking and Inventory for virtual machines page, enter the following options:
   1. In Basics, you can define the scope. Select the three dots to configure a scope. In the Scope page, provide the Subscription and Resource group.
   2. In Parameters, select the option in the Bring your own user assigned managed identity.
   3. Provide the Data Collection Rule Resource id. Learn more on how to obtain the Data Collection Rule Resource ID after you create the Data collection rule.
   4. Select Review + create.

Create data collection rule

1. Download CtDcrCreation.json file on your machine.

2. Go to Azure portal and in the search, enter Deploy a custom template.

3. In the Custom deployment page > select a template, select Build your own template in the editor.

4. In the Edit template, select Load file to upload the CtDcrCreation.json file.

5. Select Save.

6. In the Custom deployment > Basics tab, provide Subscription and Resource group where you want to deploy the Data Collection Rule. The Data Collection Rule Name is optional.

   Note

   • Ensure that the name of your Data Collection Rule is unique in that resource group, else the deployment will overwrite the existing Data Collection Rule.
   • The Log Analytics Workspace Resource Id specifies the Azure resource ID of the Log Analytics workspace used to store change tracking data. Ensure that location of workspace is from the Change tracking supported regions

7. Select Review+create > Create to initiate the deployment of CtDcrCreation.

8. After the deployment is complete, select CtDcr-Deployment to see the DCR Name. Use the Resource ID of the newly created Data Collection Rule for Change tracking and inventory deployment through policy.

   

Next steps

• For details of working with the feature, see Manage Change Tracking.
• To troubleshoot general problems with the feature, see Troubleshoot Change Tracking and Inventory issues.