Merge remote-tracking branch 'upstream/main' into Branch-CI3607

Author: AmandaAZ

.openpublishing.redirection.json

@@ -12755,6 +12755,134 @@
     {
       "source_path": "support/dynamics-365/sales/your-device-is-currently-unsupported.md",
       "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/your-device-is-currently-unsupported"
-    }
+    },
+    {
+      "source_path": "support/mem/configmgr/client-management/cannot-download-content-from-cmg.md",
+      "redirect_url": "/troubleshoot/mem/configmgr/client-management/cmg-communication-error"
+    },
+    {
+      "source_path": "support/mem/configmgr/client-management/cmg-communication-error-403.md",
+      "redirect_url": "/troubleshoot/mem/configmgr/client-management/cmg-communication-error"
+    },
+    {
+      "source_path": "support/dynamics-365/sales/attachments-not-tracked-to-dynamics-365-after-office-365-atp-is-enabled.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/attachments-not-tracked-to-dynamics-365-after-office-365-atp-is-enabled"
+    },
+    {
+      "source_path": "support/dynamics-365/sales/buttons-such-as-track-and-set-regarding-are-missing.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/buttons-such-as-track-and-set-regarding-are-missing"
+    },
+    {
+      "source_path": "support/dynamics-365/sales/cannot-connect-to-exchange-message-when-using-dynamics-365-app-for-outlook.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/cannot-connect-to-exchange-message-when-using-dynamics-365-app-for-outlook"
+    },
+    {
+      "source_path": "support/dynamics-365/sales/dynamics-365-app-for-outlook-is-missing.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/dynamics-365-app-for-outlook-is-missing"
+    },
+    {
+      "source_path": "support/dynamics-365/sales/dynamics-365-app-outlook-did-not-load.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/dynamics-365-app-outlook-did-not-load"
+    },
+    {
+      "source_path": "support/dynamics-365/sales/emails-tracked-by-dynamics-365-app-for-outlook-show-track-pending.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/emails-tracked-by-dynamics-365-app-for-outlook-show-track-pending"
+    },
+    {
+      "source_path": "support/dynamics-365/sales/error-incomingemailrejected-install-dynamics-365-app-outlook.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/error-incomingemailrejected-install-dynamics-365-app-outlook"
+    },
+    {
+      "source_path": "support/dynamics-365/sales/error-install-dynamics-365-app-outlook.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/error-install-dynamics-365-app-outlook"
+    },
+    {
+      "source_path": "support/dynamics-365/sales/error-when-accessing-crm-app-outlook.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/error-when-accessing-crm-app-outlook"
+    },
+    {
+      "source_path": "support/dynamics-365/sales/error-when-opening-365-app-outlook.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/error-when-opening-365-app-outlook"
+    },
+    {
+      "source_path": "support/dynamics-365/sales/error-when-using-365-app-outlook.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/error-when-using-365-app-outlook"
+    },
+    {
+      "source_path": "support/dynamics-365/sales/privilege-error-occurs-when-using-dynamics-365-app-for-outlook.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/privilege-error-occurs-when-using-dynamics-365-app-for-outlook"
+    },
+    {
+      "source_path": "support/dynamics-365/sales/the-view-is-not-available-error-when-opening-emails.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/the-view-is-not-available-error-when-opening-emails"
+    },
+    {
+      "source_path": "support/dynamics-365/sales/troubleshoot-item-level-server-side-synchronization-issues.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/troubleshoot-item-level-server-side-synchronization-issues"
+    },
+    {
+      "source_path": "support/dynamics-365/sales/trying-to-access-dynamics-365-app-for-outlook-from-email-do-not-recognize-error.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/trying-to-access-dynamics-365-app-for-outlook-from-email-do-not-recognize-error"
+    },
+    {
+      "source_path": "support/dynamics-365/sales/we-are-unable-to-connect-to-your-dynamics-365-app-for-outlook-error.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/we-are-unable-to-connect-to-your-dynamics-365-app-for-outlook-error"
+    },
+    {
+      "source_path": "support/dynamics-365/sales/you-do-not-have-permission-to-access-this-app-error-when-accessing-dynamics-365-app-for-outlook.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/you-do-not-have-permission-to-access-this-app-error-when-accessing-dynamics-365-app-for-outlook"
+    },
+    {
+      "source_path": "support/dynamics-365/sales/you-do-not-have-required-role-privilege.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/you-do-not-have-required-role-privilege"
+    },
+    {
+      "source_path": "support/dynamics-365/sales/you-do-not-have-the-required-role-or-privilege-to-complete-this-action-error.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/you-do-not-have-the-required-role-or-privilege-to-complete-this-action-error"
+    },
+    {
+      "source_path": "support/windows-server/performance/use-userdump-create-dump-file.md",
+      "redirect_url": "/sysinternals/downloads/procdump"
+    },
+    {
+      "source_path": "support/power-platform/dataverse/d365-app-outlook/troubleshoot-dynamics-365-app-outlook.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/welcome-dataverse"
+    },
+    {
+      "source_path": "support/power-platform/dataverse/d365-app-outlook/error-when-accessing-crm-app-outlook.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/welcome-dataverse"
+    },
+    {
+      "source_path": "support/power-platform/dataverse/d365-app-outlook/new-forms-formatted-incorrectly.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/welcome-dataverse"
+    },
+    {
+      "source_path": "support/power-platform/dataverse/d365-app-outlook/error-when-using-365-app-outlook.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/welcome-dataverse"
+    },
+    {
+      "source_path": "support/power-platform/dataverse/d365-app-outlook/your-device-is-currently-unsupported.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/welcome-dataverse"
+    },
+    {
+      "source_path": "support/power-platform/dataverse/d365-app-outlook/this-organization-has-already-been-configured-error-when-connecting.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/welcome-dataverse"
+    },
+    {
+      "source_path": "support/power-platform/dataverse/d365-app-outlook/you-do-not-have-permission-to-access-this-app-error-when-accessing-dynamics-365-app-for-outlook.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/welcome-dataverse"
+    },
+    {
+      "source_path": "support/power-platform/dataverse/d365-app-outlook/the-given-key-was-not-present-in-dictionary.md",
+      "redirect_url": "/previous-versions/troubleshoot/dynamics/crm/the-given-key-was-not-present-in-dictionary"
+    },
+    {
+      "source_path": "support/power-platform/dataverse/d365-app-outlook/error-when-installing-crm-2016-outlook.md",
+      "redirect_url": "/previous-versions/troubleshoot/dynamics/crm/error-when-installing-crm-2016-outlook"
+    },
+    {
+      "source_path": "support/power-platform/dataverse/d365-app-outlook/current-user-role-not-have-required-permissions.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/privilege-error-occurs-when-using-dynamics-365-app-for-outlook"
+    }   
   ]
 }

support/azure/.openpublishing.redirection.azure.json

@@ -6283,6 +6283,22 @@
       {
         "source_path": "azure-monitor/app-insights/availability/profiler-troubleshooting.md",
         "redirect_url": "/azure/azure-monitor/profiler/profiler-troubleshooting"
+      },
+      {
+        "source_path": "azure-monitor/app-insights/availability/code-optimizations-troubleshooting.md",
+        "redirect_url": "/azure/azure-monitor/insights/code-optimizations-troubleshoot"
+      },
+      {
+        "source_path": "azure-monitor/app-insights/debug/snapshot-debugger-troubleshoot.md",
+        "redirect_url": "/azure/azure-monitor/snapshot-debugger/snapshot-debugger-troubleshoot"
+      },
+      {
+        "source_path": "azure-kubernetes/error-codes/vhdfilenotfound.md",
+        "redirect_url": "/troubleshoot/azure/azure-kubernetes/error-codes/vmextensionerror-vhdfilenotfound"
+      },
+      {
+        "source_path": "virtual-machines/linux/linux-vm-no-boot-hyper-v-driver-issues.md",
+        "redirect_url": "/troubleshoot/azure/virtual-machines/linux/troubleshoot-lis-driver-issues-on-linux-vms"
       }
   ]
 }

support/azure/azure-container-instances/connectivity/web-socket-is-closed-or-could-not-be-opened.md

@@ -1,11 +1,11 @@
 ---
 title: Error - Web socket is closed or could not be opened
 description: Learn how to resolve the (Web socket is closed or could not be opened) error. This error prevents you from connecting to your container from a virtual network.
-ms.date: 12/28/2023
+ms.date: 02/24/2025
 author: tysonfms
 ms.author: tysonfreeman
 editor: v-jsitser
-ms.reviewer: v-leedennis
+ms.reviewer: albarqaw, v-weizhu, v-leedennis
 ms.service: azure-container-instances
 ms.custom: sap:Connectivity
 #Customer intent: As an Azure administrator, I want to learn how to resolve the "Web socket is closed or could not be opened" error so that I can successfully deploy an image onto a container instance.
@@ -22,10 +22,12 @@ When you try to connect to your container from the Azure portal, you receive the
 
 ## Cause
 
-Your firewall blocks access to port 19390. This port is required to connect to Container Instances from the Azure portal when container groups are deployed in virtual networks.
+Your firewall or corporate proxy blocks access to port 19390. This port is required to connect to Container Instances from the Azure portal when container groups are deployed in virtual networks.
 
 ## Solution
 
-Allow ingress to TCP port 19390 in your firewall. At a minimum, make sure that your firewall gives access to that port for all public client IP addresses that the Azure portal has to connect to.
+To resolve this error, allow ingress to TCP port 19390 in your firewall. At a minimum, make sure that your firewall gives access to that port for all public client IP addresses that the Azure portal has to connect to.
+
+In some scenarios where the corporate proxy blocks port 19390, allow this port for corporate proxy, and then verify the traffic by using the **Network** tab in the browser developer tools.
 
 [!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

support/azure/azure-kubernetes/connectivity/insufficientsubnetsize-error-advanced-networking.md

@@ -1,7 +1,7 @@
 ---
 title: InsufficientSubnetSize error code
 description: Learn how to fix an InsufficientSubnetSize error that occurs when you deploy an Azure Kubernetes Service (AKS) cluster that uses advanced networking.
-ms.date: 11/29/2023
+ms.date: 02/20/2025
 author: jotavar
 ms.author: jotavar
 ms.reviewer: chiragpa, nickoman, v-leedennis

support/azure/azure-kubernetes/create-upgrade-delete/429-too-many-requests-errors.md

@@ -1,7 +1,7 @@
 ---
 title: 429 Too Many Requests errors
 description: Troubleshoot why you receive 429 Too Many Requests errors on your Kubernetes clusters.
-ms.date: 08/29/2023
+ms.date: 02/20/2025
 ms.reviewer: chiragpa, nickoman, v-leedennis, v-weizhu
 ms.service: azure-kubernetes-service
 keywords:

support/azure/azure-kubernetes/create-upgrade-delete/aks-common-issues-faq.yml

@@ -3,8 +3,8 @@ metadata:
   title: Azure Kubernetes Service (AKS) common issues FAQ
   description: Review a list of frequently asked questions (FAQ) about common issues when you're working with an Azure Kubernetes Service (AKS) cluster.
   ms.topic: faq
-  ms.date: 11/14/2023
-  ms.reviewer: chiragpa, nickoman, v-leedennis
+  ms.date: 03/06/2025
+  ms.reviewer: chiragpa, nickoman, jotavar, v-leedennis, v-weizhu
   ms.service: azure-kubernetes-service
   ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool)
 
@@ -26,8 +26,7 @@ sections:
       - question: |
           Can I move my cluster to a different subscription, or move my subscription with my cluster to a new tenant?
         answer: |
-          If you've moved your AKS cluster to a different subscription or the cluster's subscription to a new tenant, the cluster won't function because of missing cluster identity permissions. AKS doesn't support moving clusters across subscriptions or tenants because of this constraint.
-
+          No. If you've moved your AKS cluster to a different subscription or the cluster's subscription to a new tenant, the cluster won't function because of missing cluster identity permissions. AKS doesn't support moving clusters across subscriptions or tenants because of this constraint. For more information, see [Operations FAQ](/azure/aks/faq#operations).
       - question: |
           What naming restrictions are enforced for AKS resources and parameters?
         answer: |
@@ -42,7 +41,10 @@ sections:
           - AKS node pool names must be all lowercase. The names must be 1-12 characters in length for Linux node pools and 1-6 characters for Windows node pools. A name must start with a letter, and the only allowed characters are letters and numbers.
 
           - The *admin-username*, which sets the administrator user name for Linux nodes, must start with a letter. This user name may only contain letters, numbers, hyphens, and underscores. It has a maximum length of 32 characters.
-
+          
+          For more information about naming convention. see the following resources:
+           - [Naming rules and restrictions for Azure resources](/azure/azure-resource-manager/management/resource-name-rules#microsoftcontainerservice)
+           - [Abbreviation recommendations for Azure resources](/azure/cloud-adoption-framework/ready/azure-best-practices/resource-abbreviations#containers)
 additionalContent: |
   [!INCLUDE [Third-party disclaimer](../../../includes/third-party-disclaimer.md)]
   

support/azure/azure-kubernetes/create-upgrade-delete/aks-increased-memory-usage-cgroup-v2.md

@@ -1,8 +1,8 @@
 ---
 title: Increased memory usage reported in Kubernetes 1.25 or later versions
 description: Resolve an increase in memory usage that's reported after you upgrade an Azure Kubernetes Service (AKS) cluster to Kubernetes 1.25.x.
-ms.date: 07/13/2023
-editor: v-jsitser
+ms.date: 03/03/2025
+editor: momajed
 ms.reviewer: aritraghosh, cssakscic, v-leedennis
 ms.service: azure-kubernetes-service
 ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool)
@@ -23,23 +23,49 @@ You experience one or more of the following symptoms:
 
 ## Cause
 
-This increase is caused by a change in memory accounting within version 2 of the Linux control group (cgroup) API. [Cgroup v2](https://kubernetes.io/docs/concepts/architecture/cgroups/) is now the default cgroup version for Kubernetes 1.25 on AKS.
+This increase is caused by a change in memory accounting within version 2 of the Linux control group (`cgroup`) API. [Cgroup v2](https://kubernetes.io/docs/concepts/architecture/cgroups/) is now the default `cgroup` version for Kubernetes 1.25 on AKS.
 
 > [!NOTE]  
-> This issue is distinct from the memory saturation in nodes that's caused by applications or frameworks that aren't aware of cgroup v2. For more information, see [Memory saturation occurs in pods after cluster upgrade to Kubernetes 1.25](./aks-memory-saturation-after-upgrade.md).
+> This issue is distinct from the memory saturation in nodes that's caused by applications or frameworks that aren't aware of `cgroup` v2. For more information, see [Memory saturation occurs in pods after cluster upgrade to Kubernetes 1.25](./aks-memory-saturation-after-upgrade.md).
 
 ## Solution
 
 - If you observe frequent memory pressure on the nodes, upgrade your subscription to increase the amount of memory that's available to your virtual machines (VMs).
 
 - If you see a higher eviction rate on the pods, [use higher limits and requests for pods](/azure/aks/developer-best-practices-resource-management#define-pod-resource-requests-and-limits).
 
+- `cgroup` v2 uses a different API than `cgroup` v1. If there are any applications that directly access the `cgroup` file system, update them to later versions that support `cgroup` v2. For example:
+
+  - **Third-party monitoring and security agents**:
+
+     Some monitoring and security agents depend on the `cgroup` file system. Update these agents to versions that support `cgroup` v2.
+
+  - **Java applications**:
+
+     Use versions that fully support `cgroup` v2:
+    - OpenJDK/HotSpot: `jdk8u372`, `11.0.16`, `15`, and later versions.
+    - IBM Semeru Runtimes: `8.0.382.0`, `11.0.20.0`, `17.0.8.0`, and later versions.
+    - IBM Java: `8.0.8.6` and later versions.
+
+  - **uber-go/automaxprocs**:  
+    If you're using the `uber-go/automaxprocs` package, ensure the version is `v1.5.1` or later.
+
+- An alternative temporary solution is to revert the `cgroup` version on your nodes by using the DaemonSet. For more information, see [Revert to cgroup v1 DaemonSet](https://github.com/Azure/AKS/blob/master/examples/cgroups/revert-cgroup-v1.yaml).
+
+> [!IMPORTANT]
+> - Use the DaemonSet cautiously. Test it in a lower environment before applying to production to ensure compatibility and prevent disruptions.
+> - By default, the DaemonSet applies to all nodes in the cluster and reboots them to implement the `cgroup` change.  
+> - To control how the DaemonSet is applied, configure a `nodeSelector` to target specific nodes.
+
+
 > [!NOTE]  
 > If you experience only an increase in memory use without any of the other symptoms that are mentioned in the "Symptoms" section, you don't have to take any action.
 
 ## Status
 
-We're actively working with the Kubernetes community to fix the underlying issue, and we'll keep you updated on our progress. We also plan to change the eviction thresholds or [resource reservations](/azure/aks/concepts-clusters-workloads#resource-reservations), depending on the outcome of the fix.
+We're actively working with the Kubernetes community to resolve the underlying issue. Progress on this effort can be tracked at [Azure/AKS Issue #3443](https://github.com/kubernetes/kubernetes/issues/118916). 
+
+As part of the resolution, we plan to adjust the eviction thresholds or update [resource reservations](/azure/aks/concepts-clusters-workloads#resource-reservations), depending on the outcome of the fix.
 
 ## Reference