fixes

Author: bwren

.openpublishing.redirection.azure-monitor.json

@@ -6631,7 +6631,7 @@
         },
         {
             "source_path_from_root": "/articles/azure-monitor/essentials/data-collection.md",
-            "redirect_url": "/azure/azure-monitor/essentials/data-collection-rules",
+            "redirect_url": "/azure/azure-monitor/essentials/data-collection-rule-overview",
             "redirect_document_id": false
         },
         {

articles/azure-monitor/essentials/data-collection-rule-create-edit.md

@@ -19,7 +19,7 @@ This article describes the different methods for creating and editing a DCR. For
 
 | Built-in role | Scopes | Reason |
 |:---|:---|:---|
-| [Monitoring Contributor](../../role-based-access-control/built-in-roles.md#monitoring-contributor) | <ul><li>Subscription and/or</li><li>Resource group and/or </li><li>An existing DCR</li></ul> | Create or edit DCRs, assign rules to the machine, deploy associations). |
+| [Monitoring Contributor](../../role-based-access-control/built-in-roles.md#monitoring-contributor) | <ul><li>Subscription and/or</li><li>Resource group and/or </li><li>An existing DCR</li></ul> | Create or edit DCRs, assign rules to the machine, deploy associations. |
 | [Virtual Machine Contributor](../../role-based-access-control/built-in-roles.md#virtual-machine-contributor)<br>[Azure Connected Machine Resource Administrator](../../role-based-access-control/built-in-roles.md#azure-connected-machine-resource-administrator)</li></ul> | <ul><li>Virtual machines, virtual machine scale sets</li><li>Azure Arc-enabled servers</li></ul> | Deploy agent extensions on the VM. |
 | Any role that includes the action *Microsoft.Resources/deployments/** | <ul><li>Subscription and/or</li><li>Resource group and/or </li><li>An existing DCR</li></ul> | Deploy Azure Resource Manager templates. |
 
@@ -75,7 +75,7 @@ az rest --method put --url $ResourceId"?api-version=2022-06-01" --body @$FilePat
 
 ### [ARM](#tab/arm)
 
-See the follow references for defining DCRs and associations in a template.
+See the following references for defining DCRs and associations in a template.
 - [Data collection rules](/azure/templates/microsoft.insights/datacollectionrules)
 - [Data collection rule associations](/azure/templates/microsoft.insights/datacollectionruleassociations)
 

articles/azure-monitor/essentials/data-collection-transformations.md

@@ -4,14 +4,14 @@ description: Use transformations in a data collection rule in Azure Monitor to f
 ms.topic: conceptual
 author: bwren
 ms.author: bwren
-ms.date: 07/17/2023
+ms.date: 03/28/2024
 ms.reviwer: nikeist
 ---
 
 # Data collection transformations in Azure Monitor
 With transformations in Azure Monitor, you can filter or modify incoming data before it's sent to a Log Analytics workspace. This article provides a basic description of transformations and how they're implemented. It provides links to other content for creating a transformation.
 
-Transformations are performed in Azure Monitor in the [data ingestion pipeline](../essentials/data-collection.md) after the data source delivers the data and before it's sent to the destination. The data source might perform its own filtering before sending data but then rely on the transformation for further manipulation before it's sent to the destination.
+Transformations are performed in Azure Monitor in the data ingestion pipeline after the data source delivers the data and before it's sent to the destination. The data source might perform its own filtering before sending data but then rely on the transformation for further manipulation before it's sent to the destination.
 
 Transformations are defined in a [data collection rule (DCR)](data-collection-rule-overview.md) and use a [Kusto Query Language (KQL) statement](data-collection-transformations-structure.md) that's applied individually to each entry in the incoming data. It must understand the format of the incoming data and create output in the structure expected by the destination.
 

articles/azure-monitor/essentials/media/logs-ingestion-api-overview/overview-log-ingestion-api.png

@@ -15,7 +15,7 @@ The application sends data to a [data collection endpoint (DCE)](../essentials/d
 
 The data sent by your application to the API must be formatted in JSON and match the structure expected by the DCR. It doesn't necessarily need to match the structure of the target table because the DCR can include a [transformation](../essentials//data-collection-transformations.md) to convert the data to match the table's structure. You can modify the target table and workspace by modifying the DCR without any change to the API call or source data.
 
-:::image type="content" source="../essentials/media/logs-ingestion-api-overview/overview-log-ingestion-api.png" lightbox="../essentials/media/logs-ingestion-api-overview/overview-log-ingestion-api.png" alt-text="Diagram that shows an overview of logs ingestion API." border="false":::
+:::image type="content" source="../logs/media/logs-ingestion-api-overview/overview-log-ingestion-api.png" lightbox="../logs/media/logs-ingestion-api-overview/overview-log-ingestion-api.png" alt-text="Diagram that shows an overview of logs ingestion API." border="false":::
 
 ## Configuration
 The following table describes each component in Azure that you must configure before you can use the Logs Ingestion API.