Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into rolyon-rbac-classic-admins-deprecation-update

Author: rolyon

articles/app-service/overview-vnet-integration.md

@@ -178,6 +178,8 @@ Route tables and network security groups only apply to traffic routed through th
 
 When configuring network security groups or route tables that applies to outbound traffic, you must make sure you consider your application dependencies. Application dependencies include endpoints that your app needs during runtime. Besides APIs and services the app is calling, these endpoints could also be derived endpoints like certificate revocation list (CRL) check endpoints and identity/authentication endpoint, for example Microsoft Entra ID. If you're using [continuous deployment in App Service](./deploy-continuous-deployment.md), you might also need to allow endpoints depending on type and language. Specifically for [Linux continuous deployment](https://github.com/microsoft/Oryx/blob/main/doc/hosts/appservice.md#network-dependencies), you need to allow `oryx-cdn.microsoft.io:443`. For Python you additionally need to allow `files.pythonhosted.org`, `pypi.org`.
 
+Azure uses UDP port 30,000 to do network health checks. If you block this traffic, it will not directly impact your app, but it will be more difficult for Azure support to detect and troubleshoot network related issues. 
+
 When you want to route outbound traffic on-premises, you can use a route table to send outbound traffic to your Azure ExpressRoute gateway. If you do route traffic to a gateway, set routes in the external network to send any replies back. Border Gateway Protocol (BGP) routes also affect your app traffic. If you have BGP routes from something like an ExpressRoute gateway, your app outbound traffic is affected. Similar to user-defined routes, BGP routes affect traffic according to your routing scope setting.
 
 ## Service endpoints

articles/automation/change-tracking/overview-monitoring-agent.md

@@ -13,8 +13,7 @@ ms.service: azure-automation
 **Applies to:** :heavy_check_mark: Windows VMs :heavy_check_mark: Linux VMs :heavy_check_mark: Windows Registry :heavy_check_mark: Windows Files :heavy_check_mark: Linux Files :heavy_check_mark: Windows Software :heavy_check_mark: Windows Services & Linux Daemons
 
 > [!Important]
-> - Currently, Change tracking and inventory uses Log Analytics Agent and this is scheduled to retire by 31.August.2024. We recommend that you use Azure Monitoring Agent as the new supporting agent.
-> - Guidance on migration from Change Tracking & Inventory using Log Analytics agent to Azure Monitoring Agent will be available once it is generally available. [Learn more](guidance-migration-log-analytics-monitoring-agent.md).
+> - Change Tracking and Inventory using Log Analytics agent has retired on **31 August 2024**. Follow the guidelines for  [migration from Change Tracking and inventory using Log Analytics to Change Tracking and inventory using Azure Monitoring Agent version](guidance-migration-log-analytics-monitoring-agent.md)
 > - We recommend that you use Change Tracking with Azure Monitoring Agent with the Change tracking extension version 2.20.0.0 (or above) to access the GA version of this service.
 
 This article explains on the latest version of change tracking support using Azure Monitoring Agent as a singular agent for data collection. 

articles/azure-arc/.openpublishing.redirection.azure-arc.json

@@ -134,6 +134,81 @@
             "source_path_from_root": "/articles/azure-arc/vmware-vsphere/switch-to-new-version-vmware.md",
             "redirect_url": "/azure/azure-arc/vmware-vsphere/switch-to-new-version",
             "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-arc/edge-storage-accelerator/how-to-single-node-k3s.md",
+            "redirect_url": "/azure/azure-arc/container-storage/install-cache-volumes",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-arc/edge-storage-accelerator/install-edge-storage-accelerator.md",
+            "redirect_url": "/azure/azure-arc/container-storage/install-edge-volumes",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-arc/edge-storage-accelerator/attach-app.md",
+            "redirect_url": "/azure/azure-arc/container-storage/attach-app",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-arc/edge-storage-accelerator/azure-monitor-kubernetes.md",
+            "redirect_url": "/azure/azure-arc/container-storage/azure-monitor-kubernetes",
+            "redirect_document_id": false
+        },        
+        {
+            "source_path_from_root": "/articles/azure-arc/edge-storage-accelerator/create-pv.md",
+            "redirect_url": "/azure/azure-arc/container-storage/create-persistent-volume",
+            "redirect_document_id": false
+        },        
+        {
+            "source_path_from_root": "/articles/azure-arc/edge-storage-accelerator/create-pvc.md",
+            "redirect_url": "/azure/azure-arc/container-storage/create-persistent-volume-claim",
+            "redirect_document_id": false
+        },        
+        {
+            "source_path_from_root": "/articles/azure-arc/edge-storage-accelerator/index.yml",
+            "redirect_url": "/azure/azure-arc/container-storage/index",
+            "redirect_document_id": false
+        },        
+        {
+            "source_path_from_root": "/articles/azure-arc/edge-storage-accelerator/jumpstart.md",
+            "redirect_url": "/azure/azure-arc/container-storage/jumpstart",
+            "redirect_document_id": false
+        },        
+        {
+            "source_path_from_root": "/articles/azure-arc/edge-storage-accelerator/multi-node-cluster.md",
+            "redirect_url": "/azure/azure-arc/container-storage/multi-node-cluster",
+            "redirect_document_id": false
+        },        
+        {
+            "source_path_from_root": "/articles/azure-arc/edge-storage-accelerator/overview.md",
+            "redirect_url": "/azure/azure-arc/container-storage/overview",
+            "redirect_document_id": false
+        },        
+        {
+            "source_path_from_root": "/articles/azure-arc/edge-storage-accelerator/prepare-linux.md",
+            "redirect_url": "/azure/azure-arc/container-storage/prepare-linux",
+            "redirect_document_id": false
+        },        
+        {
+            "source_path_from_root": "/articles/azure-arc/edge-storage-accelerator/release-notes.md",
+            "redirect_url": "/azure/azure-arc/container-storage/release-notes",
+            "redirect_document_id": false
+        },        
+        {
+            "source_path_from_root": "/articles/azure-arc/edge-storage-accelerator/single-node-cluster.md",
+            "redirect_url": "/azure/azure-arc/container-storage/single-node-cluster",
+            "redirect_document_id": false
+        },        
+        {
+            "source_path_from_root": "/articles/azure-arc/edge-storage-accelerator/support-feedback.md",
+            "redirect_url": "/azure/azure-arc/container-storage/support-feedback",
+            "redirect_document_id": false
+        },        
+        {
+            "source_path_from_root": "/articles/azure-arc/edge-storage-accelerator/third-party-monitoring.md",
+            "redirect_url": "/azure/azure-arc/container-storage/third-party-monitoring",
+            "redirect_document_id": false
         }
     ]
 }