Merge pull request #1357 from MicrosoftDocs/main

2/28/2025 AM Publish

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

@@ -25,7 +25,7 @@ For a short introduction to the Azure Monitor Agent, including a demo of how to
 
 The Azure Monitor Agent is one method of [data collection for Azure Monitor](../data-sources.md). It's installed on VMs running in Azure, in other clouds, or on-premises, where it has access to local logs and performance data. Without the agent, you can collect data only from the host machine because you would have no access to the client operating system and to running processes.
 
-The agent can be installed by using different methods, as described in [Install and manage the Azure Monitor Agent](./azure-monitor-agent-manage.md). You can install the agent on a single machine or at scale by using Azure Policy or other tools. In some cases, the agent is automatically installed when you enable a feature that requires it, such as Microsoft Sentinel.
+The agent can be installed by using different methods, as described in [Install and manage the Azure Monitor Agent](./azure-monitor-agent-manage.md). You can install the agent on a single machine or at scale by using Azure Policy or other tools. In some cases, the agent is automatically installed when you enable a feature that requires it, such as Microsoft Sentinel. The automatic installation only occurs when the feature is first enabled. For continued automated installation for new VM deployments a policy should be created and enabled following the instructions here: [Using a Policy to Install AMA](/azure/azure-monitor/agents/azure-monitor-agent-policy).
 
 ## Data collection
 

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

@@ -124,8 +124,6 @@ Use the following ARM template to create a DCR for collecting text log files, ma
 | Table name | Name of the destination table in your Log Analytics Workspace. |     
 | Record delimiter | Not currently used but reserved for future potential use allowing delimiters other than the currently supported end of line (`/r/n`). | 
 | Transform | [Ingestion-time transformation](../essentials/data-collection-transformations.md) to filter records or to format the incoming data for the destination table. Use `source` to leave the incoming data unchanged. |
-| timeFormat| The following times formats are supported.  Use the quotes strings in your ARM template. Do not include the sample time that is in parentheses. <br> - “yyyy-MM-ddTHH:mm:ssk”   (2024-10-29T18:28:34) <br> - “YYYY-MM-DD HH:MM:SS”   (2024-10-29 18:28:34) <br> - “M/D/YYYY HH:MM:SS AM/PM”   (10/29/2024 06:28:34 PM) <br> - “Mon DD, YYYY HH:MM:SS”   (October 29, 2024 18:28:34) <br> - “yyMMdd HH:mm:ss”   (241029 18:28:34) <br> - “ddMMyy HH:mm:ss”   (291024 18:28:34) <br> - “MMM d HH:mm:ss”   (Oct 29 18:28:34) <br> - “dd/MMM/yyyy:HH:mm:ss zzz”   (14/Oct/2024:18:28:34 -000) |
-
 
 
 Use the following ARM template to create or modify a DCR for collecting text log files. In addition to the parameter values, you may need to modify the following values in the template:
@@ -176,13 +174,7 @@ Use the following ARM template to create or modify a DCR for collecting text log
             "metadata": {
               "description": "Resource ID of the Log Analytics workspace with the target table."
             }
-        },
-        "timeFormat": {
-            "type": "string"
-            "metadata": {
-                "discription": "The time format that you would like to use to split multi line imput"
-            }
-      }
+        }
     },
     "variables": {
       "tableOutputStream": "[concat('Custom-', parameters('tableName'))]"