Skip to content

Commit a56c407

Browse files
Update create-policy-definition.md
1 parent 4648ab2 commit a56c407

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/governance/machine-configuration/how-to/create-policy-definition.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -117,8 +117,8 @@ Parameters of the `New-GuestConfigurationPolicy` cmdlet:
117117
- **`-ExcludeArcMachines`** (Optional) - A flag to exclude Arc machines from the generated Policy definition (Required if you are using a User Assigned Managed Identity to provide access to an Azure Storge blob)
118118

119119
> [!IMPORTANT]
120-
> Please note that, unlike Azure VMs, Arc-connected machines currently do not support User Assigned Managed Identities. As a result, the `-ExcludeArcMachines` flag is required to ensure the exclusion of those machines from the policy definition.
121-
> Additionally, for the Azure VM to download the assigned package and apply the policy, the Guest Configuration Windows Agent Version 1.29.82.0 OR Linux Agent Version 1.26.76.0 is required
120+
> - Please note that, unlike Azure VMs, Arc-connected machines currently do not support User Assigned Managed Identities. As a result, the `-ExcludeArcMachines` flag is required to ensure the exclusion of those machines from the policy definition.
121+
> - Additionally, for the Azure VM to download the assigned package and apply the policy, the Guest Configuration Windows Agent Version 1.29.82.0 OR Linux Agent Version 1.26.76.0 is required
122122
123123
For more information about the **Mode** parameter, see the page
124124
[How to configure remediation options for machine configuration][02].

0 commit comments

Comments
 (0)