Merge pull request #285784 from MicrosoftDocs/main

8/29 11:00 AM IST Publish

Author: Saisang

.openpublishing.redirection.json

@@ -4744,6 +4744,16 @@
       "source_path_from_root": "/articles/virtual-network/tutorial-filter-network-traffic-cli.md",
       "redirect_url": "/azure/virtual-network/tutorial-filter-network-traffic",
       "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/virtual-network/virtual-network-service-endpoint-policies-portal.md",
+      "redirect_url": "/azure/virtual-network/virtual-network-service-endpoint-policies",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/virtual-network/virtual-network-service-endpoint-policies-powershell.md",
+      "redirect_url": "/azure/virtual-network/virtual-network-service-endpoint-policies",
+      "redirect_document_id": false
     }
   ]
 }

articles/api-management/workspaces-overview.md

@@ -91,7 +91,7 @@ Manage gateway capacity by manually adding or removing scale units, similar to t
 Workspace gateways need to be in the same Azure region and subscription as the API Management service. 
 
 > [!NOTE]
-> Starting in August 2024, workspace gateway support will be rolled out in the following regions. These regions are a subset of those where API Management is available.
+> These regions are a subset of those where API Management is available.
 
 * West US
 * North Central US

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

@@ -25,7 +25,6 @@ Migration is a complex task. Start planning your migration to Azure Monitor Agen
 > - **Installation:** The ability to install the legacy agents will be removed from the Azure Portal and installation policies for legacy agents will be removed. You can still install the MMA agents extension as well as perform offline installations.
 > - **Customer Support:** You will not be able to get support for legacy agent issues.
 > - **OS Support:** Support for new Linux or Windows distros, including service packs, won't be added after the deprecation of the legacy agents.
-> - Log Analytics Agent will continue to function but not be able to connect Log Analytics workspaces.
 > - Log Analytics Agent can coexist with Azure Monitor Agent. Expect to see duplicate data if both agents are collecting the same data.
 
 

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

@@ -2,7 +2,7 @@
 title: Collect logs from a JSON file with Azure Monitor Agent 
 description: Configure a data collection rule to collect log data from a JSON file on a virtual machine using Azure Monitor Agent.
 ms.topic: conceptual
-ms.date: 08/23/2024
+ms.date: 08/28/2024
 author: guywi-ms
 ms.author: guywild
 ms.reviewer: jeffwo
@@ -16,7 +16,7 @@ Many applications and services will log information to a JSON files instead of s
 ## Prerequisites
 
 - Log Analytics workspace where you have at least [contributor rights](../logs/manage-access.md#azure-rbac).
-- A data collection endpoint (DCE) if you plan to use Azure Monitor Private Links. The data collection endpoint must be in the same region as the Log Analytics workspace. See [How to set up data collection endpoints based on your deployment](../essentials/data-collection-endpoint-overview.md#how-to-set-up-data-collection-endpoints-based-on-your-deployment) for details.
+- A data collection endpoint (DCE) in the same region as the Log Analytics workspace. See [How to set up data collection endpoints based on your deployment](../essentials/data-collection-endpoint-overview.md#how-to-set-up-data-collection-endpoints-based-on-your-deployment) for details.
 - Either a new or existing DCR described in [Collect data with Azure Monitor Agent](./azure-monitor-agent-data-collection.md).
 
 ## Basic operation
@@ -133,6 +133,7 @@ Use the following ARM template to create a DCR for collecting text log files, ma
 | Setting | Description |
 |:---|:---|
 | Data collection rule name | Unique name for the DCR. |
+| Data collection endpoint resource ID | Resource ID of the data collection endpoint (DCE). |
 | Location | Region for the DCR. Must be the same location as the Log Analytics workspace. |
 | File patterns | Identifies the location and name of log files on the local disk. Use a wildcard for filenames that vary, for example when a new file is created each day with a new name. You can enter multiple file patterns separated by commas (AMA version 1.26 or higher required for multiple file patterns on Linux).<br><br>Examples:<br>- C:\Logs\MyLog.json<br>- C:\Logs\MyLog*.json<br>- C:\App01\AppLog.json, C:\App02\AppLog.json<br>- /var/mylog.json<br>- /var/mylog*.json |
 | Table name | Name of the destination table in your Log Analytics Workspace. |     
@@ -152,6 +153,12 @@ Use the following ARM template to create a DCR for collecting text log files, ma
                 "description": "Unique name for the DCR. "
             }
         },
+        "dataCollectionEndpointResourceId": {
+            "type": "string",
+            "metadata": {
+              "description": "Resource ID of the data collection endpoint (DCE)."
+            }
+        },
         "location": {
             "type": "string",
             "metadata": {
@@ -175,12 +182,6 @@ Use the following ARM template to create a DCR for collecting text log files, ma
             "metadata": {
                 "description": "Resource ID of the Log Analytics workspace with the target table."
             }
-        },
-        "dataCollectionEndpointResourceId": {
-            "type": "string",
-            "metadata": {
-                "description": "Resource ID of the Data Collection Endpoint to be used with this rule."
-            }
         }
     },
     "variables": {
@@ -193,6 +194,7 @@ Use the following ARM template to create a DCR for collecting text log files, ma
             "name": "[parameters('dataCollectionRuleName')]",
             "location": "[parameters('location')]",
             "properties": {
+                "dataCollectionEndpointId": "[parameters('dataCollectionEndpointResourceId')]",
                 "streamDeclarations": {
                     "Custom-Json-stream": {
                         "columns": [
@@ -256,8 +258,7 @@ Use the following ARM template to create a DCR for collecting text log files, ma
                         "transformKql": "source",
                         "outputStream": "[variables('tableOutputStream')]"
                     }
-                ],
-                "dataCollectionEndpointId": "[parameters('dataCollectionEndpointResourceId')]"
+                ]
             }
         }
     ]

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

@@ -2,7 +2,7 @@
 title: Collect logs from a text file with Azure Monitor Agent 
 description: Configure a data collection rule to collect log data from a text file on a virtual machine using Azure Monitor Agent.
 ms.topic: conceptual
-ms.date: 08/23/2024
+ms.date: 08/28/2024
 author: guywi-ms
 ms.author: guywild
 ms.reviewer: jeffwo
@@ -16,7 +16,7 @@ Many applications and services will log information to text files instead of sta
 ## Prerequisites
 
 - Log Analytics workspace where you have at least [contributor rights](../logs/manage-access.md#azure-rbac).
-- A data collection endpoint (DCE) if you plan to use Azure Monitor Private Links. The data collection endpoint must be in the same region as the Log Analytics workspace. See [How to set up data collection endpoints based on your deployment](../essentials/data-collection-endpoint-overview.md#how-to-set-up-data-collection-endpoints-based-on-your-deployment) for details.
+- A data collection endpoint (DCE) in the same region as the Log Analytics workspace. See [How to set up data collection endpoints based on your deployment](../essentials/data-collection-endpoint-overview.md#how-to-set-up-data-collection-endpoints-based-on-your-deployment) for details.
 - Either a new or existing DCR described in [Collect data with Azure Monitor Agent](./azure-monitor-agent-data-collection.md).
 
 ## Basic operation
@@ -143,6 +143,12 @@ Use the following ARM template to create or modify a DCR for collecting text log
               "description": "Unique name for the DCR. "
             }
         },
+        "dataCollectionEndpointResourceId": {
+            "type": "string",
+            "metadata": {
+              "description": "Resource ID of the data collection endpoint (DCE)."
+            }
+        },
         "location": {
             "type": "string",
             "metadata": {
@@ -178,6 +184,7 @@ Use the following ARM template to create or modify a DCR for collecting text log
             "location": "[parameters('location')]",
             "apiVersion": "2022-06-01",
             "properties": {
+                "dataCollectionEndpointId": "[parameters('dataCollectionEndpointResourceId')]",
                 "streamDeclarations": {
                     "Custom-Text-stream": {
                         "columns": [

articles/azure-monitor/app/release-and-work-item-insights.md

@@ -389,6 +389,9 @@ The new work item integration offers the following features over [classic](#clas
 
     You can set specific work item properties directly from the template itself. This includes the assignee, iteration path, projects, & more depending on your version control provider.
 
+   > [!NOTE]
+   > For on-premises Azure DevOps environments, a sample URL such as https://dev.azure.com/test/test can be used as a placeholder for the Azure DevOps Project URL. Once the work item template is created, you can modify the URL and its validation rule within the generated [Azure workbook](/azure/azure-monitor/visualize/workbooks-create-workbook).
+
 ## Create a work item
 
  You can access your new template from any End-to-end transaction details that you can access from Performance, Failures, Availability, or other tabs.

articles/azure-portal/TOC.yml

@@ -36,6 +36,8 @@
     href: azure-portal-video-series.md
 - name: Dashboards
   items:
+  - name: Create and manage dashboards in Dashboard hub
+    href: dashboard-hub.md
   - name: Create an Azure dashboard
     href: azure-portal-dashboards.md
   - name: Share an Azure dashboard