Merge branch 'main' into lucciz01-improve-error-2147209462-logged-mailbox-record.md

Author: lucciz01

.openpublishing.redirection.developer.json

@@ -5784,6 +5784,16 @@
       "source_path": "support/developer/visualstudio/installation/known-issues-visual-studio-2012-update.md",
       "redirect_url": "/troubleshoot/developer/visualstudio/welcome-visual-studio",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "support/developer/webapps/iis/site-behavior-performance/default-maximum-stack-size-thread.md",
+      "redirect_url": "/troubleshoot/developer/webapps/iis/iis-welcome",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "support/developer/webapps/iis/site-behavior-performance/page-cannot-displayed-when-you-connect-ssl.md",
+      "redirect_url": "/troubleshoot/developer/webapps/iis/iis-welcome",
+      "redirect_document_id": false
     }
   ]
 }

.openpublishing.redirection.json

@@ -12580,6 +12580,11 @@
       "redirect_url": "/troubleshoot/power-platform/dataverse/email-exchange-synchronization/incoming-emails-unexpectedly-synchronized-have-unexpected-missing-data",
       "redirect_document_id": true
     },
+    {
+      "source_path": "support/dynamics-365/sales/tracked-to-dynamics-365-category-added.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/email-exchange-synchronization/tracked-to-dynamics-365-category-added",
+      "redirect_document_id": true
+    },
     {
       "source_path": "support/dynamics-365/sales/cannot-send-email-as-another-user.md",
       "redirect_url": "/troubleshoot/power-platform/dataverse/email-exchange-synchronization/cannot-send-email-as-another-user",
@@ -12589,6 +12594,26 @@
       "source_path": "support/windows-server/certificates-and-public-key-infrastructure-pki/delete-enterprise-windows-certificate-authority.md",
       "redirect_url": "/previous-versions/troubleshoot/windows-server/delete-enterprise-windows-certificate-authority",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "support/dynamics-365/sales/error-when-signing-dynamics-365.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/email-exchange-synchronization/error-when-signing-dynamics-365",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "support/dynamics-365/sales/you-are-not-part-this-organization.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/email-exchange-synchronization/error-when-signing-dynamics-365",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "support/power-platform/power-automate/desktop-flows/no-ethernet-after-pad-install.md",
+      "redirect_url": "/previous-versions/troubleshoot/content-retirement",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "support/windows-server/group-policy/apply-group-policy-objects-terminal-services.md",
+      "redirect_url": "/troubleshoot/windows-server/group-policy/apply-group-policy-objects-rds",
+      "redirect_document_id": true
     }
   ]
 }

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

@@ -6249,6 +6249,51 @@
         "source_path": "azure-storage/files/alerts/files-troubleshoot-create-alerts.md",
         "redirect_url": "/azure/storage/files/files-monitoring-alerts",
         "redirect_document_id": false
+      },
+      {
+        "source_path": "virtual-machines/linux/ed25519-ssh-keys.md",
+        "redirect_url": "/troubleshoot/azure/virtual-machines/linux/welcome-virtual-machines-linux",
+        "redirect_document_id": false
+      },
+      {
+        "source_path": "azure-kubernetes/create-upgrade-delete/upgrades-to-kubernetes-fail-using-node-labels.md",
+        "redirect_url": "/troubleshoot/azure/azure-kubernetes/welcome-azure-kubernetes",
+        "redirect_document_id": false
+      },
+      {
+        "source_path": "azure-kubernetes/create-upgrade-delete/error-code-requestdisallowedbypolicy-delete.md",
+        "redirect_url": "/troubleshoot/azure/azure-kubernetes/welcome-azure-kubernetes",
+        "redirect_document_id": false
+      },
+      {
+        "source_path": "general/support-policy-containers.md",
+        "redirect_url": "/troubleshoot/azure/azure-kubernetes/welcome-azure-kubernetes",
+        "redirect_document_id": false
+      },
+      {
+        "source_path": "azure-kubernetes/connectivity/stale-watch-azure-ad-pod-identity-nmi-status-500.md",
+        "redirect_url": "/troubleshoot/azure/azure-kubernetes/welcome-azure-kubernetes",
+        "redirect_document_id": false
+      },
+      {
+        "source_path": "azure-kubernetes/create-upgrade-delete/error-code-cnidownloadtimeoutvmextensionerror.md",
+        "redirect_url": "/troubleshoot/azure/azure-kubernetes/error-codes/vmextensionerror-cnidownloadtimeout",
+        "redirect_document_id": true
+      },
+      {
+        "source_path": "azure-kubernetes/create-upgrade-delete/error-code-k8sapiserverconnfailvmextensionerror.md",
+        "redirect_url": "/troubleshoot/azure/azure-kubernetes/error-codes/vmextensionerror-k8sapiserverconnfail",
+        "redirect_document_id": true
+      },
+      {
+        "source_path": "azure-kubernetes/create-upgrade-delete/error-code-k8sapiserverdnslookupfailvmextensionerror.md",
+        "redirect_url": "/troubleshoot/azure/azure-kubernetes/error-codes/vmextensionerror-k8sapiserverdnslookupfail",
+        "redirect_document_id": true
+      },
+      {
+        "source_path": "azure-kubernetes/create-upgrade-delete/error-code-outboundconnfailvmextensionerror.md",
+        "redirect_url": "/troubleshoot/azure/azure-kubernetes/error-codes/vmextensionerror-outboundconnfail",
+        "redirect_document_id": true
       }
   ]
 }

support/azure/app-service/scaling-web-app-faq.yml

@@ -4,9 +4,9 @@ metadata:
   description: Describe common questions and answers about scaling in Azure App Service.
   services: app-service
   author: auolivei
-  ms.reviewer: amehrot, rimarr, genli
+  ms.reviewer:  genli
   ms.topic: faq
-  ms.date: 08/03/2022
+  ms.date: 12/05/2024
   ms.author: auolivei
   ms.service: azure-app-service
 title: Frequently asked questions about scaling web apps in Azure App Service
@@ -62,7 +62,7 @@ sections:
           Autoscale is triggered when metrics exceed preconfigured boundaries. Sometimes, you might notice that the capacity is only partially filled compared to what you expected. This behavior might occur when the number of instances you want isn't available. In that scenario, autoscale partially fills in with the available number of instances. Autoscale then runs the rebalance logic to get more capacity. It allocates the remaining instances, and this allocation might take a few minutes. If you don't see the expected number of instances after a few minutes, it might be because the partial refill was enough to bring the metrics within the boundaries. Or, autoscale might have scaled down because it reached the lower metrics boundary.
 
       - question: |
-           When I scale up an App Service Plan to a Premium V3 tier, the "Premium V3 is not supported for this scale unit. Please consider redeploying or cloning your app." error occurs. What should I do?
+           When I scale up an App Service Plan to a Premium V3 tier, the "Premium V3 isn't supported for this scale unit. Please consider redeploying or cloning your app." error occurs. What should I do?
         answer: |
           The Premium V3 feature requires the site to run on the newest hardware infrastructure. To scale up an App Service Plan to Premium V3, the Web App must be running in an App Service deployment that supports PremiumV3. For more information, see [Scale up from an unsupported resource group and region combination](/azure/app-service/app-service-configure-premium-tier#scale-up-from-an-unsupported-resource-group-and-region-combination).
 
@@ -76,5 +76,10 @@ sections:
         answer: |
           The file change audit logs "AppServiceFileAuditLogs" are only available for App Services in Premium, PremiumV2, and Isolated App Service Plans. If you need "AppServiceFileAuditLogs," you won't be able to scale down to the Basic tier. To have these audit logs available, configure your App Service Plan for Premium or higher tier. 
 
+      - question: |
+          I'm getting the "App Service Plans with fewer than 3 workers aren't allowed for zone redundancy. Requested number of workers: number" error. What should I do?
+        answer: |
+          [Availability zone support](/azure/reliability/reliability-app-service#availability-zone-support) requires at least three instances. Verify if the App Service Plan has zone redundancy enabled and if you have autoscale on the App Service Plan. If so, correct the autoscale rule to not set the number of instances to a value less than three.
+
 
           [!INCLUDE [Azure Help Support](../../includes/azure-help-support.md)]

support/azure/azure-kubernetes/availability-performance/node-not-ready-expired-certificates.md

@@ -55,9 +55,9 @@ Check the expiration dates of certificates by invoking the [openssl-x509](https:
 
 You might receive certain error codes after you invoke these commands. For information about error codes 50, 51, and 52, see the following links, as necessary:
 
-- [Troubleshoot the OutboundConnFailVMExtensionError error code (50)](../create-upgrade-delete/error-code-outboundconnfailvmextensionerror.md)
-- [Troubleshoot the K8SAPIServerConnFailVMExtensionError error code (51)](../create-upgrade-delete/error-code-k8sapiserverconnfailvmextensionerror.md)
-- [Troubleshoot the K8SAPIServerDNSLookupFailVMExtensionError error code (52)](../create-upgrade-delete/error-code-k8sapiserverdnslookupfailvmextensionerror.md)
+- [Troubleshoot the VMExtensionError_OutboundConnFail error code (50)](../error-codes/vmextensionerror-outboundconnfail.md)
+- [Troubleshoot the VMExtensionError_K8SAPIServerConnFail error code (51)](../error-codes/vmextensionerror-k8sapiserverconnfail.md)
+- [Troubleshoot the VMExtensionError_K8SAPIServerDNSLookupFail error code (52)](../error-codes/vmextensionerror-k8sapiserverdnslookupfail.md)
 
 If you receive error code 99, this indicates that the [apt-get update](https://linux.die.net/man/8/apt-get) command is being blocked from accessing one or more of the following domains:
 

support/azure/azure-kubernetes/availability-performance/node-not-ready-then-recovers.md

@@ -1,41 +1,36 @@
 ---
 title: Node not ready but then recovers
-description: Troubleshoot scenarios in the status of an Azure Kubernetes Service (AKS) cluster node is Node Not Ready, but then the node recovers.
-ms.date: 04/15/2022
+description: Troubleshoot scenarios in which the status of an AKS cluster node is Node Not Ready, but then the node recovers.
+ms.date: 12/09/2024
 ms.reviewer: rissing, chiragpa, momajed, v-leedennis
 ms.service: azure-kubernetes-service
-#Customer intent: As an Azure Kubernetes user, I want to prevent the Node Not Ready status for nodes that later recover so that I can avoid future errors within an Azure Kubernetes Service (AKS) cluster.
+#Customer intent: As an Azure Kubernetes user, I want to prevent the Node Not Ready status for nodes that later recover so that I can avoid future errors within an AKS cluster.
 ms.custom: sap:Node/node pool availability and performance
 ---
 # Troubleshoot Node Not Ready failures that are followed by recoveries
 
-This article helps troubleshoot scenarios in which a node within a Microsoft Azure Kubernetes Service (AKS) cluster shows the Node Not Ready status, but then automatically recovers to a healthy state.
-
-## Symptoms
-
-You notice that your application stops responding while the node is reporting that it has a Not Ready status. However, the node recovers automatically, and now, it's looking for a root cause analysis (RCA).
+This article provides a guide to troubleshoot and resolve "Node Not Ready" issues in Azure Kubernetes Service (AKS) clusters. When a node enters a "Not Ready" state, it can disrupt the application's functionality and cause it to stop responding. Typically, the node recovers automatically after a short period. However, to prevent recurring issues and maintain a stable environment, it's important to understand the underlying causes to be able to implement effective resolutions. 
 
 ## Cause
 
-Possible causes of this issue include the following scenarios:
+There are several scenarios that could cause a "Not Ready" state to occur:
 
-- The API server isn't available, and you're using a readiness probe for the deployment.
+- The unavailability of the API server. This causes the readiness probe to fail. This prevents the pod from being attached to the service so that traffic is no longer forwarded to the pod instance.
 
-  If a pod is running but isn't ready, that situation means that the readiness probe is failing. If the readiness probe fails, the pod isn't attached to the service, and traffic isn't forwarded to the pod instance.
-
-- Virtual machine (VM) host faults occur. To determine whether VM host faults occurred, check the following information sources:
+- Virtual machine (VM) host faults. To determine whether VM host faults occurred, check the following information sources:
   - [AKS diagnostics](/azure/aks/concepts-diagnostics)
   - [Azure status](https://status.azure.com/)
   - Azure notifications (for any recent outages or maintenance periods)
 
+## Resolution
+
+Check the API server availability by running the `kubectl get apiservices` command. Make sure that the readiness probe is correctly configured in the deployment YAML file.
+
+For further steps, see [Basic troubleshooting of Node Not Ready failures](node-not-ready-basic-troubleshooting.md).
+
 ## Prevention
 
 To prevent this issue from occurring in the future, take one or more of the following actions:
 
 - Make sure that your service tier is fully paid for.
 - Reduce the number of `watch` and `get` requests to the API server.
-- Replace the node pool with a healthy node pool.
-
-## More information
-
-- For general troubleshooting steps, see [Basic troubleshooting of Node Not Ready failures](node-not-ready-basic-troubleshooting.md).