scenarios

Author: mgreenegit

articles/governance/policy/concepts/guest-configuration.md

@@ -20,6 +20,17 @@ to machines. You can also assign configurations to machines
 or by using other Azure services such as
 [AutoManage](../../../automanage/automanage-virtual-machines.md).
 
+Examples of each scenario:
+
+- **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"
+- **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"
+
 Configuration resources in Azure are designed as an
 [extension resource](../../../azure-resource-manager/management/extension-resource-types.md).
 You can imagine each configuration as an additional set of properties
@@ -270,10 +281,7 @@ Management Groups.
 
 The guest configuration extension writes log files to the following locations:
 
-Windows:
-
-- Azure VM: `C:\ProgramData\GuestConfig\gc_agent_logs\gc_agent.log`
-- Arc-enabled server: `C:\ProgramData\GuestConfig\arc_policy_logs\gc_agent.log`
+Windows: `C:\ProgramData\GuestConfig\gc_agent_logs\gc_agent.log`
 
 Linux