Skip to content

Commit cdeee15

Browse files
Clarify language regarding multiple policy assignment
1 parent 2a5914a commit cdeee15

File tree

1 file changed

+3
-5
lines changed

1 file changed

+3
-5
lines changed

articles/governance/machine-configuration/overview.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Understand Azure Automanage Machine Configuration
33
description: Learn how Azure Policy uses the machine configuration feature to audit or configure settings inside virtual machines.
44
author: timwarner-msft
5-
ms.date: 01/03/2023
5+
ms.date: 03/01/2023
66
ms.topic: conceptual
77
ms.author: timwarner
88
ms.service: machine-configuration
@@ -329,11 +329,9 @@ For more information about troubleshooting machine configuration, see
329329

330330
### Multiple assignments
331331

332-
Guest Configuration policy definitions now support assigning the same
333-
guest assignment to more than once per machine when the policy assignment uses different
334-
parameters.
332+
At this time, only some built-in Guest Configuration policy definitions support multiple assignments. However, all custom policies support multiple assignments by default if you used the latest version of [the `GuestConfiguration` PowerShell module](/azure/governance/machine-configuration/machine-configuration-create-setup) to create Guest Configuration packages and policies.
335333

336-
### Assignments to Azure Management Groups
334+
### Assignments to Azure management groups
337335

338336
Azure Policy definitions in the category `Guest Configuration` can be assigned
339337
to management groups when the effect is `AuditIfNotExists` or `DeployIfNotExists`.

0 commit comments

Comments
 (0)