Merge pull request #177600 from mgreenegit/patch-26

scenarios

Author: PRMerger13

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

@@ -13,13 +13,6 @@ both for machines running in Azure and hybrid
 The feature can be used directly per-machine,
 or at-scale orchestrated by Azure Policy.
 
-Configurations are distinct from policy definitions. Guest configuration
-utilizes Azure Policy to dynamically assign configurations
-to machines. You can also assign configurations to machines
-[manually](/azure/governance/policy/concepts/guest-configuration-assignments#manually-creating-guest-configuration-assignments),
-or by using other Azure services such as
-[AutoManage](../../../automanage/automanage-virtual-machines.md).
-
 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
@@ -29,13 +22,27 @@ for the machine. Configurations can include settings such as:
 - Application configuration or presence
 - Environment settings
 
-The results from each configurations can be viewed either in the
+Configurations are distinct from policy definitions. Guest configuration
+utilizes Azure Policy to dynamically assign configurations
+to machines. You can also assign configurations to machines
+[manually](guest-configuration-assignments.md#manually-creating-guest-configuration-assignments),
+or by using other Azure services such as
+[AutoManage](../../../automanage/automanage-virtual-machines.md).
+
+Examples of each scenario are provided in the following table.
+
+| Type | Description | Example story |
+| - | - | - |
+| [Configuration management](guest-configuration-assignments.md) | 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." |
+| [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." |
+
+The per-setting results from configurations can be viewed either in the
 [Guest assignments page](../how-to/determine-non-compliance.md#compliance-details-for-guest-configuration)
 or if the configuration is orchestrated by an Azure Policy assignment,
 by clicking on the "Last evaluated resource" link on the
 ["Compliance details" page](../how-to/determine-non-compliance.md#view-configuration-assignment-details-at-scale).
 
-[A video walk-through of this document is available](https://youtu.be/t9L8COY-BkM).
+[A video walk-through of this document is available](https://youtu.be/t9L8COY-BkM). (update coming soon)
 
 ## Enable guest configuration
 
@@ -270,10 +277,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