Skip to content

Commit ac3c113

Browse files
committed
review team edits
1 parent b162e84 commit ac3c113

File tree

2 files changed

+12
-7
lines changed

2 files changed

+12
-7
lines changed

articles/azure-arc/servers/migrate-AMA-ansible.md renamed to articles/azure-arc/servers/migrate-azure-monitor-agent-ansible.md

Lines changed: 11 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ This article also uses the [Azure Infrastructure Configuration Demo](https://git
7070
**Source Control URL:** https://github.com/ansible-content-lab/azure.infrastructure_config_demos.git
7171

7272
1. Select **Save**.
73-
:::image type="content" source="media/migrate-ama/configure-content.png" alt-text="Screenshot of Projects window to edit details":::
73+
:::image type="content" source="media/migrate-ama/configure-content.png" alt-text="Screenshot of Projects window to edit details." lightbox="media/migrate-ama/configure-content.png":::
7474

7575
Once saved, the project should be synchronized with the automation controller.
7676

@@ -86,10 +86,10 @@ We will create a workflow that leverages the following playbooks to install the
8686

8787
This workflow performs the following tasks:
8888

89-
1. Installs the Azure Connected Machine agent on all of the VMs identified in inventory.
90-
1. Enables the Azure Monitor agent extension via Azure Arc.
91-
1. Disables the Azure Log Analytics agent extension via Azure Arc.
92-
1. Uninstalls the Azure Log Analytics agent if flagged.
89+
- Installs the Azure Connected Machine agent on all of the VMs identified in inventory.
90+
- Enables the Azure Monitor agent extension via Azure Arc.
91+
- Disables the Azure Log Analytics agent extension via Azure Arc.
92+
- Uninstalls the Azure Log Analytics agent if flagged.
9393

9494
### Create template to install Azure Connected Machine agent
9595

@@ -228,7 +228,7 @@ An automation controller workflow allows you to construct complex automation by
228228
1. Select **Save** at the top right corner of the workflow designer.
229229

230230
You will now have a workflow that looks like the following:
231-
:::image type="content" source="media/migrate-ama/workflow.png" alt-text="Diagram showing workflow of azure monitor agent migration process":::
231+
:::image type="content" source="media/migrate-ama/workflow.png" alt-text="Diagram showing workflow of azure monitor agent migration process.":::
232232

233233
### Add a survey to the workflow
234234

@@ -283,3 +283,8 @@ Now that you have the workflow created, you can run the workflow at any time. Wh
283283
## Conclusion
284284

285285
After following the steps in this article, you have created an automation workflow that migrates your Linux machines from the Azure Log Analytics agent to the Azure Monitor agent. This workflow will onboard the Linux machine to Azure Arc-enabled servers. This example uses the Ansible Content Lab for Cloud Automation to make implementation fast and easy.
286+
287+
## Next steps
288+
289+
Learn more about [connecting machines using Ansible playbooks](onboard-ansible-playbooks.md).
290+

articles/azure-arc/servers/toc.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -108,7 +108,7 @@
108108
- name: Onboard to Microsoft Sentinel
109109
href: scenario-onboard-azure-sentinel.md
110110
- name: Migrate to Azure Monitor Agent using Ansible
111-
href: migrate-AMA-ansible.md
111+
href: migrate-azure-monitor-agent-ansible.md
112112
- name: Onboard to Microsoft Defender for Cloud
113113
href: ../../defender-for-cloud/quickstart-onboard-machines.md?toc=/azure/azure-arc/servers/toc.json&bc=/azure/azure-arc/servers/breadcrumb/toc.json
114114
- name: Manage with Windows Admin Center

0 commit comments

Comments
 (0)