Skip to content

Commit 752fa36

Browse files
committed
fixed blocking issues
1 parent 217d821 commit 752fa36

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/automation/change-tracking/guidance-migration-log-analytics-monitoring-agent.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -82,13 +82,13 @@ To onboard through Azure portal, follow these steps:
8282

8383
1. Select the specific Arc machine with Change Tracking V1 enabled that needs to be migrated to Change Tracking V2.
8484

85-
1. Select **Migrate to Change Tracking with AMA** and in the **Configure with Azure monitor agent**, provide the resource id in the **Log analytics workspace** and select **Migrate** to initiate the deployment.
85+
1. Select **Migrate to Change Tracking with AMA** and in the **Configure with Azure monitor agent**, provide the resource ID in the **Log analytics workspace** and select **Migrate** to initiate the deployment.
8686

8787
:::image type="content" source="media/guidance-migration-log-analytics-monitoring-agent/onboarding-single-arc-vm.png" alt-text="Screenshot of onboarding a single Arc VM to Change tracking and inventory using Azure monitoring agent." lightbox="media/guidance-migration-log-analytics-monitoring-agent/onboarding-single-arc-vm.png":::
8888

8989
1. Select **Manage Activity log connection** to evaluate the incoming events and logs across LA agent and AMA version.
9090

91-
### [Log Analytics Workspace - Powershell Script ](#tab/ps-policy)
91+
### [Log Analytics Workspace - PowerShell Script ](#tab/ps-policy)
9292

9393
#### Prerequisites
9494

0 commit comments

Comments
 (0)