Skip to content

Commit 86992e3

Browse files
committed
Address editor comments
1 parent 2a682a6 commit 86992e3

File tree

4 files changed

+7
-7
lines changed

4 files changed

+7
-7
lines changed

articles/automanage/how-to-disable-automanage.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,11 +17,11 @@ You may decide one day to disable Automanage on certain VMs. For instance, your
1717

1818
To do that in the Azure portal, go to the **Automanage – Azure machine best practices** page that lists all of your auto-managed VMs. Select the checkbox next to the virtual machine you want to disable from Automanage, then click on the **Disable automanagment** button.
1919

20-
[ ![Screenshot of disabling Automanage on a virtual machine.](./media/automanage-virtual-machines/disable-step-1.png) ](./media/automanage-virtual-machines/disable-step-1.png)
20+
[ ![Screenshot of disabling Automanage on a virtual machine.](./media/automanage-virtual-machines/disable-step-1.png) ](./media/automanage-virtual-machines/disable-step-1.png#lightbox)
2121

2222
Read carefully through the messaging in the resulting pop-up before agreeing to **Disable**.
2323

24-
[ ![Screenshot of disabling Automanage on a virtual machine confirmation.](./media/automanage-virtual-machines/disable-step-2.png) ](./media/automanage-virtual-machines/disable-step-2.png)
24+
[ ![Screenshot of disabling Automanage on a virtual machine confirmation.](./media/automanage-virtual-machines/disable-step-2.png) ](./media/automanage-virtual-machines/disable-step-2.png#lightbox)
2525

2626
> [!NOTE]
2727
> Disabling automanagement in a VM results in the following behavior:

articles/automanage/overview-about.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ The Automanage service will grant **Contributor** permission to this first party
6565
6666
## Participating services
6767

68-
:::image type="content" source="media\automanage-virtual-machines\intelligently-onboard-services-1.png" alt-text="Intelligently onboard services.":::
68+
:::image type="content" source="media\automanage-virtual-machines\intelligently-onboard-services-1.png" alt-text="Diagram of intelligently onboard services.":::
6969

7070
For the complete list of participating Azure services, as well as their supported profile, see the following:
7171
- [Automanage for Linux](automanage-linux.md)

articles/automanage/overview-configuration-profiles.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,11 +10,11 @@ ms.author: memccror
1010
ms.custom: references_regions
1111
---
1212

13-
# Configuration Profiles
13+
# Configuration profiles
1414

1515
When you are enabling Automanage for your machine, a configuration profile is required. Configuration profiles are the foundation of this service. They define which services we onboard your machines to and to some extent what the configuration of those services would be.
1616

17-
## Best Practice Configuration Profiles
17+
## Best practice configuration profiles
1818

1919
There are two best practice configuration profiles currently available.
2020

@@ -23,7 +23,7 @@ There are two best practice configuration profiles currently available.
2323

2424
The reason for this differentiator is because certain services are recommended based on the workload running. For instance, in a Production machine we will automatically onboard you to Azure Backup. However, for a Dev/Test machine, a backup service would be an unnecessary cost, since Dev/Test machines are typically lower business impact.
2525

26-
## Custom Profiles
26+
## Custom profiles
2727

2828
Custom profiles allow you to customize the services and settings that you want to apply to your machines. This is a great option if your IT requirements differ from the best practices. For instance, if you do not want to use the Microsoft Antimalware solution because your IT organization requires you to use a different antimalware solution, then you can simply toggle off Microsoft Antimalware when creating a custom profile.
2929

articles/automanage/overview-vm-status.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.custom: references_regions
1414

1515
In the Azure portal, go to the **Automanage – Azure machine best practices** page which lists all of your automanage machines. Here you will see the overall status of each machine.
1616

17-
[ ![Screenshot of a list of automanaged enabled virtual machines.](./media/automanage-virtual-machines/configured-status.png) ](./media/automanage-virtual-machines/configured-status.png)
17+
[ ![Screenshot of a list of automanaged enabled virtual machines.](./media/automanage-virtual-machines/configured-status.png) ](./media/automanage-virtual-machines/configured-status.png#lightbox)
1818

1919
For each listed machine, the following details are displayed: Name, Configuration profile, Status, Resource type, Resource group, Subscription.
2020

0 commit comments

Comments
 (0)