Skip to content

Commit e868d2c

Browse files
committed
added about DINE
1 parent 91efc2b commit e868d2c

File tree

1 file changed

+32
-4
lines changed

1 file changed

+32
-4
lines changed

articles/automation/change-tracking/enable-vms-monitoring-agent.md

Lines changed: 32 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Enable Azure Automation Change Tracking for single machine and multiple m
33
description: This article tells how to enable the Change Tracking feature for single machine and multiple machines at scale from the Azure portal.
44
services: automation
55
ms.subservice: change-inventory-management
6-
ms.date: 11/24/2022
6+
ms.date: 12/14/2022
77
ms.topic: conceptual
88
---
99

@@ -35,7 +35,7 @@ This section provides detailed procedure on how you can enable change tracking o
3535

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

38-
This will initiate the deployment and the notification appears on the top right corner of the screen. You can also [change the workspace](manage-change-tracking-monitoring-agent.md#change-a-workspace) from this screen.
38+
This will initiate the deployment and the notification appears on the top right corner of the screen.
3939

4040
:::image type="content" source="media/enable-vms-monitoring-agent/deployment-success-inline.png" alt-text="Screenshot showing the notification of deployment." lightbox="media/enable-vms-monitoring-agent/deployment-success-expanded.png":::
4141

@@ -65,8 +65,36 @@ This section provides detailed procedure on how you can enable change tracking o
6565
1. A notification appears on the top right corner of the screen indicating the status of deployment.
6666
---
6767

68-
> [!NOTE]
69-
> 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. For more information, see [Configure data collection rule](manage-change-tracking-monitoring-agent.md#configure-data-collection-rule).
68+
>[!NOTE]
69+
>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.
70+
71+
## Enable Change Tracking at scale using Azure Monitoring Agent
72+
73+
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.
74+
75+
1. In Azure portal, select **Policy**.
76+
1. In the **Policy|Definitions** page, in **Authoring**, select **Definitions**
77+
1. In the **Definition Type** category, select **Initiative** and in **Category**, select **ChangeTracking andInventory**
78+
You will see a list of three policies:
79+
- Enable ChangeTracking and inventory for virtual machine scale sets
80+
- Enable ChangeTracking and inventory for virtual machines
81+
- Enable ChangeTracking and inventory for Arc-enabled virtual machines
82+
1. Select **Enable ChangeTracking and Inventory for virtual machines** to enable the change tracking on Azure virtual machines.
83+
This initiative consists of three policies:
84+
- Assign Built in User-Assigned Managed identity to Virtual machines
85+
- Configure ChangeTracking Extension for Windows virtual machines
86+
- Configure ChangeTracking Extension for Linux virtual machines
87+
1. Select **Assign** to assign the policy to a resource group. For example, **Assign Built in User-Assigned Managed identity to virtual machines**.
88+
>[!NOTE]
89+
>The Resource group contains virtual machines and when you assign the policy, it
90+
will enable change tracking at scale to a resource group. The virtual machines
91+
that are on-boarded to the same resource group will automatically have the
92+
change tracking feature enabled.
93+
1. In the **Enable ChangeTracking and Inventory for virtual machines** page, enter the following options:
94+
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**.
95+
1. In **Parameters**, select the option in the **Bring your own user assigned managed identity**.
96+
1. Provide the **Data Collection Rule Resource id**.
97+
1. Select **Review + create**.
7098

7199

72100
## Next steps

0 commit comments

Comments
 (0)