Merge pull request #222879 from guywi-ms/ama-cross-region-tenant-support

AMA cross-region, cross-tenant support

Author: prmerger-automator[bot]

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

@@ -31,7 +31,10 @@ Azure Monitor Agent replaces the Azure Monitor legacy monitoring agents:
 
 ## Install the agent and configure data collection
 
-Azure Monitor Agent uses [data collection rules](../essentials/data-collection-rule-overview.md), where you define which data you want each agent to collect. Data collection rules let you manage data collection settings at scale and define unique, scoped configurations for subsets of machines. The rules are independent of the workspace and the virtual machine, which means you can define a rule once and reuse it across machines and environments.
+Azure Monitor Agent uses [data collection rules](../essentials/data-collection-rule-overview.md), where you define which data you want each agent to collect. Data collection rules let you manage data collection settings at scale and define unique, scoped configurations for subsets of machines. You can define a rule to send data from multiple machines to multiple destinations across regions and tenants.
+
+> [!NOTE]
+> To send data across tenants, you must first enable [Azure Lighthouse](/azure/lighthouse/overview).
 
 **To collect data using Azure Monitor Agent:**
 

articles/azure-monitor/agents/data-collection-iis.md

@@ -31,7 +31,10 @@ The [data collection rule](../essentials/data-collection-rule-overview.md) defin
 - How Azure Monitor transforms events during ingestion.
 - The destination Log Analytics workspace and table to which Azure Monitor sends the data.
 
-Create the data collection rule in the *same region* as your Log Analytics workspace. You can still associate the rule to machines in other supported regions.
+You can define a data collection rule to send data from multiple machines to multiple Log Analytics workspaces, including workspaces in a different region or tenant. Create the data collection rule in the *same region* as your Log Analytics workspace.
+
+> [!NOTE]
+> To send data across tenants, you must first enable [Azure Lighthouse](/azure/lighthouse/overview).
 
 To create the data collection rule in the Azure portal:
 

articles/azure-monitor/agents/data-collection-rule-azure-monitor-agent.md

@@ -21,8 +21,10 @@ To complete this procedure, you need:
 
 ## Create a data collection rule
 
-Create the data collection rule in the *same region* as your Log Analytics workspace. You can still associate the rule to machines in other supported regions.
+You can define a data collection rule to send data from multiple machines to multiple Log Analytics workspaces, including workspaces in a different region or tenant. Create the data collection rule in the *same region* as your Log Analytics workspace.
 
+> [!NOTE]
+> To send data across tenants, you must first enable [Azure Lighthouse](/azure/lighthouse/overview).
 ### [Portal](#tab/portal)
 
 1. On the **Monitor** menu, select **Data Collection Rules**.
@@ -70,9 +72,6 @@ Create the data collection rule in the *same region* as your Log Analytics works
 1. Select **Add data source** and then select **Review + create** to review the details of the data collection rule and association with the set of virtual machines.
 1. Select **Create** to create the data collection rule.
 
-> [!NOTE]
-> It might take up to 5 minutes for data to be sent to the destinations after you create the data collection rule and associations.
-
 ### [API](#tab/api)
 
 1. Create a DCR file by using the JSON format shown in [Sample DCR](data-collection-rule-sample-agent.md).
@@ -111,6 +110,9 @@ For sample templates, see [Azure Resource Manager template samples for data coll
 
 ---
 
+> [!NOTE]
+> It can take up to 5 minutes for data to be sent to the destinations after you create the data collection rule.
+
 ## Filter events using XPath queries
 
 You're charged for any data you collect in a Log Analytics workspace. Therefore, you should only collect the event data you need. The basic configuration in the Azure portal provides you with a limited ability to filter out events.

articles/azure-monitor/agents/data-collection-text-log.md

@@ -32,10 +32,11 @@ The data collection rule defines:
 - How Azure Monitor transforms events during ingestion.
 - The destination Log Analytics workspace and table to which Azure Monitor sends the data.
 
-Create the data collection rule in the *same region* as your Log Analytics workspace. You can still associate the rule to machines in other supported regions.
+You can define a data collection rule to send data from multiple machines to multiple Log Analytics workspaces, including workspaces in a different region or tenant. Create the data collection rule in the *same region* as your Log Analytics workspace.
 
 > [!NOTE]
-> It can take up to 5 minutes for data to be sent to the destinations after you create the data collection rule.
+> To send data across tenants, you must first enable [Azure Lighthouse](/azure/lighthouse/overview).
+
 ### [Portal](#tab/portal)
 
 To create the data collection rule in the Azure portal:
@@ -282,6 +283,8 @@ To create the data collection rule in the Azure portal:
 
 ---
 
+> [!NOTE]
+> It can take up to 5 minutes for data to be sent to the destinations after you create the data collection rule.
 ## Troubleshoot
 Use the following steps to troubleshoot collection of text logs.