Skip to content

Commit f23515e

Browse files
authored
Merge pull request #99994 from mgreenegit/patch-9
Consistency of configuration naming
2 parents 173dcce + ef5b29d commit f23515e

File tree

1 file changed

+10
-1
lines changed

1 file changed

+10
-1
lines changed

articles/governance/policy/how-to/guest-configuration-create.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -78,6 +78,15 @@ Manager status for the Guest Assignment should be Compliant/Not-Compliant. If th
7878
`$false` for any resource in the configuration, then the provider will run `Get-TargetResource`. If
7979
the boolean is `$true` then `Get-TargetResource` isn't called.
8080

81+
#### Configuration requirements
82+
83+
The only requirement for Guest Configuration to use a custom configuration is for the name
84+
of the configuration to be consistent everywhere it is used. This includes the name of the .zip file
85+
for the content package, the configuration name in the mof file stored inside the content package,
86+
and the configuration name used in ARM as the guest assignment name.
87+
88+
#### Get-TargetResource requirements
89+
8190
The function `Get-TargetResource` has special requirements for Guest Configuration that haven't been
8291
needed for Windows Desired State Configuration.
8392

@@ -555,4 +564,4 @@ recent information.
555564

556565
- Learn about auditing VMs with [Guest Configuration](../concepts/guest-configuration.md).
557566
- Understand how to [programmatically create policies](programmatically-create.md).
558-
- Learn how to [get compliance data](get-compliance-data.md).
567+
- Learn how to [get compliance data](get-compliance-data.md).

0 commit comments

Comments
 (0)