Skip to content

Commit 6239f1a

Browse files
authored
Apply suggestions from code review
Acrolinx fixes
1 parent 2effcd8 commit 6239f1a

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

articles/automanage/automanage-virtual-machines.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -160,7 +160,7 @@ For each listed machine, the following details are displayed: Name, Configuratio
160160
The **Status** column can display the following states:
161161
- *In progress* - the VM is being configured
162162
- *Conformant* - the VM is configured and no drift is detected
163-
- *Not conformant* - the VM has drifted and Automanage was unable to correct one or more services to the assiged configuration profile
163+
- *Not conformant* - the VM has drifted and Automanage was unable to correct one or more services to the assigned configuration profile
164164
- *Needs upgrade* - the VM is onboarded to an earlier version of Automanage and needs to be [upgraded](automanage-upgrade.md) to the latest version
165165
- *Unknown* - the Automanage service is unable to determine the desired configuration of the machine. This is usually because the VM agent is not installed or the machine is not running. It can also indicate that the Automanage service does not have the necessary permissions that it needs to determine the desired configuration
166166
- *Error* - the Automanage service encountered an error while attempting to determine if the machine conforms with the desired configuration

articles/automanage/virtual-machines-policy-enable.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ If you don't have an Azure subscription, [create an account](https://azure.micro
2828
## Direct link to Policy
2929
There are two Automanage built-in policies:
3030
1. Built-in Automanage profiles (dev/test and production): The Automanage policy definition can be found in the Azure portal by the name of [Configure virtual machines to be onboarded to Azure Automanage](https://portal.azure.com/#blade/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Ff889cab7-da27-4c41-a3b0-de1f6f87c550).
31-
1. Custom configuration profiles : The Automanage policy definition can be found in the Azure portal by the name of [Configure virtual machines to be onboarded to Azure Automanage with Custom Configuration Profile](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Fb025cfb4-3702-47c2-9110-87fe0cfcc99b0).
31+
1. Custom configuration profiles: The Automanage policy definition can be found in the Azure portal by the name of [Configure virtual machines to be onboarded to Azure Automanage with Custom Configuration Profile](https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Fb025cfb4-3702-47c2-9110-87fe0cfcc99b0).
3232

3333
If you click on this link, skip directly to step 8 in [Locate and assign the policy](#locate-and-assign-the-policy) below.
3434

0 commit comments

Comments
 (0)