You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/governance/machine-configuration/overview.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ Examples of each scenario are provided in the following table.
33
33
|[Configuration management][05]| You want a complete representation of a server, as code in source control. The deployment should include properties of the server (size, network, storage) and configuration of operating system and application settings. | "This machine should be a web server configured to host my website." |
34
34
|[Compliance][06]| You want to audit or deploy settings to all machines in scope either reactively to existing machines or proactively to new machines as they're deployed. | "All machines should use TLS 1.2. Audit existing machines so I can release change where it's needed, in a controlled way, at scale. For new machines, enforce the setting when they're deployed." |
35
35
36
-
You can view the per-setting results from configurations in the [Guest assignments page][07]. If an
36
+
You can view the per-setting results from configurations in the [Guest assignments page][44]. If an
37
37
Azure Policy assignment orchestrated the configuration is orchestrated, you can select the "Last
38
38
evaluated resource" link on the ["Compliance details" page][07].
39
39
@@ -473,9 +473,10 @@ Machine configuration built-in policy samples are available in the following loc
0 commit comments