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
You can imagine each configuration as an additional set of properties
19
+
for the machine. Configurations can include settings such as:
20
+
21
+
- Operating system settings
22
+
- Application configuration or presence
23
+
- Environment settings
24
+
16
25
Configurations are distinct from policy definitions. Guest configuration
17
26
utilizes Azure Policy to dynamically assign configurations
18
27
to machines. You can also assign configurations to machines
@@ -24,19 +33,10 @@ Examples of each scenario are provided in the following table.
24
33
25
34
| Type | Description | Example story |
26
35
| - | - | - |
27
-
|**Configuration management**| You want to deploy configurations to one machine to define an end state and make the change now. | "this machine should be a web server and configure settings for a website" |
28
-
|**Compliance**| You want to audit or deploy settings to all machines in scope either reactively to existing machines or proactively to new machines as they are deployed. | "all machines should use TLS 1.2 and if they don't, I want to fix that in a controlled way, at scale" |
29
-
30
-
Configuration resources in Azure are designed as an
You can imagine each configuration as an additional set of properties
33
-
for the machine. Configurations can include settings such as:
34
-
35
-
- Operating system settings
36
-
- Application configuration or presence
37
-
- Environment settings
36
+
|[Configuration management](/guest-configuration-assignments.md)| You want a complete representation of a server or servers, 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." |
37
+
|[Compliance](../assign-policy-portal.md)| You want to audit or deploy settings to all machines in scope either reactively to existing machines or proactively to new machines as they are deployed. | "All machines should use TLS 1.2. Audit existing machines so I can release change where it is needed, in a controlled way, at scale. For new machines, enforce the setting when they are deployed." |
38
38
39
-
The results from each configurations can be viewed either in the
39
+
The per-setting results from configurations can be viewed either in the
0 commit comments