Merge pull request #189673 from bwren/ama-fixes

Azure Monitor agent replace updates that got removed

Author: PRMerger-2

articles/azure-monitor/agents/azure-monitor-agent-overview.md

@@ -120,7 +120,7 @@ There's no cost for the Azure Monitor agent, but you might incur charges for the
 The Azure Monitor agent doesn't require any keys but instead requires a [system-assigned managed identity](../../active-directory/managed-identities-azure-resources/qs-configure-portal-windows-vm.md#system-assigned-managed-identity). You must have a system-assigned managed identity enabled on each virtual machine before you deploy the agent.
 
 ## Networking
-The Azure Monitor agent supports Azure service tags (both AzureMonitor and AzureResourceManager tags are required). It supports connecting via **direct proxies, Log Analytics gateway and private links** as described below.
+The Azure Monitor agent supports Azure service tags (both AzureMonitor and AzureResourceManager tags are required). It supports connecting via **direct proxies, Log Analytics gateway, and private links** as described below.
 
 ### Proxy configuration
 If the machine connects through a proxy server to communicate over the internet, review requirements below to understand the network configuration required.
@@ -176,6 +176,18 @@ New-AzConnectedMachineExtension -Name AzureMonitorLinuxAgent -ExtensionType Azur
 
 ---
 
+### Log Analytics gateway configuration
+1. Follow the instructions above to configure proxy settings on the agent and provide the IP address and port number corresponding to the gateway server. If you have deployed multiple gateway servers behind a load balancer, the agent proxy configuration is the virtual IP address of the load balancer instead.  
+2. Add the **configuration endpoint URL** to fetch data collection rules to the allow list for the gateway  
+   `Add-OMSGatewayAllowedHost -Host global.handler.control.monitor.azure.com`  
+   `Add-OMSGatewayAllowedHost -Host <gateway-server-region-name>.handler.control.monitor.azure.com`  
+   (If using private links on the agent, you must also add the [dce endpoints](../essentials/data-collection-endpoint-overview.md#components-of-a-data-collection-endpoint))  
+3. Add the **data ingestion endpoint URL** to the allow list for the gateway  
+   `Add-OMSGatewayAllowedHost -Host <log-analytics-workspace-id>.ods.opinsights.azure.com`  
+3. Restart the **OMS Gateway** service to apply the changes  
+   `Stop-Service -Name <gateway-name>`  
+   `Start-Service -Name <gateway-name>` 
+
 ## Private link configuration
 To configure the agent to use private links for network communications with Azure Monitor, you can use [Azure Monitor Private Links Scopes (AMPLS)](../logs/private-link-security.md) and [data collection endpoints](azure-monitor-agent-data-collection-endpoint.md) to enable required network isolation. 
 

articles/azure-monitor/agents/resource-manager-agent.md

@@ -53,7 +53,7 @@ The following sample installs the Azure Monitor agent on a Windows Azure virtual
               "type": "AzureMonitorWindowsAgent",
               "typeHandlerVersion": "1.0",
               "autoUpgradeMinorVersion": true,
-			  "enableAutomaticUpgrade":true
+              "enableAutomaticUpgrade":true
           }
       }
   ]

articles/azure-monitor/essentials/data-collection-rule-overview.md

@@ -59,7 +59,10 @@ See the following resources for programmatically working with DCRs.
 
 
 ## Data resiliency and high availability
-Data collection rules are stored regionally, and are available in all public regions where Log Analytics is supported. Government regions and clouds are not currently supported. A rule gets created and stored in the region you specify, and is backed up to the [paired-region](../../availability-zones/cross-region-replication-azure.md#azure-cross-region-replication-pairings-for-all-geographies) within the same geography. The service is deployed to all three [availability zones](../../availability-zones/az-overview.md#availability-zones) within the region, making it a **zone-redundant service** which further adds to high availability.
+A rule gets created and stored in the region you specify, and is backed up to the [paired-region](../../availability-zones/cross-region-replication-azure.md#azure-cross-region-replication-pairings-for-all-geographies) within the same geography. The service is deployed to all three [availability zones](../../availability-zones/az-overview.md#availability-zones) within the region, making it a **zone-redundant service** which further adds to high availability.
+
+## Supported regions
+Data collection rules are stored regionally, and are available in all public regions where Log Analytics is supported, as well as the Azure Government and China clouds. Air-gapped clouds are not yet supported.
 
 ### Single region data residency
 This is a preview feature to enable storing customer data in a single region is currently only available in the Southeast Asia Region (Singapore) of the Asia Pacific Geo and Brazil South (Sao Paulo State) Region of Brazil Geo. Single region residency is enabled by default in these regions.

articles/azure-monitor/essentials/data-collection-rule-structure.md

@@ -39,7 +39,7 @@ Each data source has a data source type. Each type defines a unique set of prope
 
 | Data source type | Description | 
 |:---|:---|
-| extension | VM extension-based data source |
+| extension | VM extension-based data source, used exclusively by Log Analytics solutions and Azure services ([View agent supported services and solutions](../agents/azure-monitor-agent-overview.md#supported-services-and-features)) |
 | performanceCounters | Performance counters for both Windows and Linux |
 | syslog | Syslog events on Linux |
 | windowsEventLogs | Windows event log |