Merge branch 'main' into jdaly-main-web-api-errors

Author: JimDaly

.openpublishing.redirection.developer.json

@@ -5784,6 +5784,68 @@
       "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
+    },
+    {
+      "source_path": "support/developer/webapps/iis/general/instances-httpsys-not-cache.md",
+      "redirect_url": "/troubleshoot/developer/webapps/iis/www-modules-features/instances-httpsys-not-cache"
+    },
+    {
+      "source_path": "support/developer/webapps/iis/health-diagnostic-performance/troubleshoot-502-2-bad-gateway-error-in-cgi-apps.md",
+      "redirect_url": "/troubleshoot/developer/webapps/iis/site-behavior-performance/troubleshoot-502-2-bad-gateway-error-in-cgi-apps"
+    },
+    {
+      "source_path": "support/developer/webapps/iis/health-diagnostic-performance/troubleshoot-http-400-errors-in-iis.md",
+      "redirect_url": "/troubleshoot/developer/webapps/iis/site-behavior-performance/troubleshoot-http-400-errors-in-iis"
+    },
+    {
+      "source_path": "support/developer/webapps/iis/site-behavior-performance/exception-integrated-pipeline-mode.md",
+      "redirect_url": "/troubleshoot/developer/webapps/iis/development/exception-integrated-pipeline-mode"
+    },
+    {
+      "source_path": "support/developer/webapps/iis/www-administration-management/http-error-500-when-you-visit-web-site.md",
+      "redirect_url": "/troubleshoot/developer/webapps/iis/site-behavior-performance/http-error-500-when-you-visit-web-site"
+    },
+    {
+      "source_path": "support/developer/webapps/iis/www-authentication-authorization/401-error-preauthentication-header.md",
+      "redirect_url": "/troubleshoot/developer/webapps/iis/site-behavior-performance/401-error-preauthentication-header"
+    },
+    {
+      "source_path": "support/developer/webapps/iis/www-authentication-authorization/information-associated-iis-site-is-not-deleted.md",
+      "redirect_url": "/troubleshoot/developer/webapps/iis/www-administration-management/information-associated-iis-site-is-not-deleted"
+    },
+    {
+      "source_path": "support/developer/webapps/iis/www-administration-management/http-status-code.md",
+      "redirect_url": "/troubleshoot/developer/webapps/iis/health-diagnostic-performance/http-status-code"
+    },
+    {
+      "source_path": "support/developer/webapps/iis/health-diagnostic-performance/http-403-14-forbidden-webpage.md",
+      "redirect_url": "/troubleshoot/developer/webapps/iis/site-behavior-performance/http-403-14-forbidden-webpage"
+    },
+    {
+      "source_path": "support/developer/webapps/iis/www-authentication-authorization/default-permissions-user-rights.md",
+      "redirect_url": "/troubleshoot/developer/webapps/iis/www-administration-management/default-permissions-user-rights"
+    },
+    {
+      "source_path": "support/developer/webapps/iis/health-diagnostic-performance/http-403-forbidden-access-website.md",
+      "redirect_url": "/troubleshoot/developer/webapps/iis/site-behavior-performance/http-403-forbidden-access-website"
+    },    
+    {
+      "source_path": "support/developer/webapps/iis/www-administration-management/http-bad-request-response-kerberos.md",
+      "redirect_url": "/troubleshoot/developer/webapps/iis/www-authentication-authorization/http-bad-request-response-kerberos"
+    },
+    {
+      "source_path": "support/developer/webapps/iis/health-diagnostic-performance/troubleshoot-native-memory-leak-iis-7x-application-pool.md",
+      "redirect_url": "/troubleshoot/developer/webapps/iis/site-behavior-performance/troubleshoot-native-memory-leak-iis-7x-application-pool"
     }
   ]
 }

.openpublishing.redirection.json

@@ -6915,11 +6915,6 @@
       "redirect_url": "/previous-versions/troubleshoot/windows-server/windows-virtual-desktop-blank-screen",
       "redirect_document_id": false
     },
-    {
-      "source_path": "support/azure/virtual-desktop/welcome-virtual-desktop.yml",
-      "redirect_url": "/azure/virtual-desktop",
-      "redirect_document_id": false
-    },
     {
       "source_path": "support/windows-client/windows-troubleshooters/introduction-to-troubleshootingscript-toolset-tss.md",
       "redirect_url": "/troubleshoot/windows-client/windows-tss/introduction-to-troubleshootingscript-toolset-tss",
@@ -11147,7 +11142,7 @@
     },
     {
       "source_path": "support/windows-server/active-directory/lingering-objects-remain.md",
-      "redirect_url": "/previous-versions/troubleshoot/windows-server/lingering-objects-remain",
+      "redirect_url": "/troubleshoot/windows-server/active-directory/manually-remove-lingering-objects",
       "redirect_document_id": false
     },
     {
@@ -12595,6 +12590,11 @@
       "redirect_url": "/previous-versions/troubleshoot/windows-server/delete-enterprise-windows-certificate-authority",
       "redirect_document_id": false
     },
+    {
+      "source_path": "support/dynamics-365/sales/exception-appears-server-side-sync.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/email-exchange-synchronization/exception-appears-server-side-sync",
+      "redirect_document_id": true
+    },
     {
       "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",
@@ -12610,10 +12610,55 @@
       "redirect_url": "/previous-versions/troubleshoot/content-retirement",
       "redirect_document_id": false
     },
+    {
+      "source_path": "support/dynamics-365/sales/unknownincomingemailintegrationerror.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/email-exchange-synchronization/exception-appears-server-side-sync",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "support/dynamics-365/sales/unknownincomingemailintegrationerror-2147167669-shows-in-alert-in-mailbox.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/email-exchange-synchronization/exception-appears-server-side-sync",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "support/dynamics-365/sales/unknownincomingemailintegrationerror-2147220192.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/email-exchange-synchronization/exception-appears-server-side-sync",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "support/dynamics-365/sales/unknownincomingemailintegrationerror-2147220970-exception.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/email-exchange-synchronization/exception-appears-server-side-sync",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "support/dynamics-365/sales/alert-appears-users-dynamics-365-mailbox-record.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/email-exchange-synchronization/exception-appears-server-side-sync",
+      "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
+    },
+    {
+      "source_path": "support/dynamics-365/sales/an-error-occurred-while-synchronizing-item.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/email-exchange-synchronization/an-error-occurred-while-synchronizing-item",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "support/dynamics-365/sales/http-server-returned-serviceunavailable.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/email-exchange-synchronization/an-error-occurred-while-synchronizing-item",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "support/dynamics-365/sales/incomingmailboxinternalcrmerror.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/email-exchange-synchronization/an-error-occurred-while-synchronizing-item",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "support/dynamics-365/sales/errorinternalservertransienterror-error.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/email-exchange-synchronization/an-error-occurred-while-synchronizing-item",
+      "redirect_document_id": false
     }
   ]
 }

support/azure/app-service/capture-memory-dumps-app-service.md

@@ -100,7 +100,9 @@ In the following sections, we discuss each of these debugging features in more d
 
 The [auto-heal](/azure/app-service/overview-diagnostics#auto-healing) (request duration) feature is useful for capturing a memory dump if the response is taking longer than expected to finish. You can see the link to **Auto-Heal** in the **Diagnostic Tools** tile in the previous screenshot. Select that link to go directly to the feature, or select the **Diagnostic Tools** tile to review all the available tools on the **Diagnostic Tools** page. For information about how to configure this feature, see the following articles:
 
-- [App Services auto heal](https://appserviceblog.com/app-services-auto-heal/)
+- [Announcing the New Auto Healing Experience in App Service Diagnostics](https://azure.github.io/AppService/2018/09/10/Announcing-the-New-Auto-Healing-Experience-in-App-Service-Diagnostics.html) 
+
+- [Announcing Auto Heal for Linux](https://azure.github.io/AppService/2021/04/21/Announcing-Autoheal-for-Azure-App-Service-Linux.html)
 
 - [Collect and automate diagnostic actions with Azure App Services](https://devblogs.microsoft.com/premier-developer/collect-and-automate-diagnostic-actions-with-azure-app-services/)
 
@@ -112,7 +114,7 @@ Another feature that's named "Collect a Memory dump" is useful in this scenario
 
 #### Collect a memory dump feature
 
-To understand the configuration of the Collect a Memory dump feature, see [Collect memory dump app services](https://appserviceblog.com/collect-memory-dump-app-services/). This approach requires manual intervention. The following screenshot shows the **Collect a Memory dump** page.
+This approach requires manual intervention. The following screenshot shows the **Collect a Memory dump** page.
 
 :::image type="content" source="./media/capture-memory-dumps-app-service/collect-memory-dump.png" alt-text="Azure portal screenshot of the 'Collect a Memory dump' page in Diagnostic Tools." lightbox="./media/capture-memory-dumps-app-service/collect-memory-dump.png":::
 

support/azure/automation/updates/find-azurermresource-fails.md

@@ -25,6 +25,6 @@ Starting in Microsoft AzureRM 6.0.0, the `Find-AzureRmResource` cmdlet functiona
 
 ## Resolution
 
-To fix this issue, update your runbooks to use `Get-AzureRmResource` instead of `Find-AzureRmResource`. For more information, see the [usage of Get-AzureRmResource](/powershell/module/azurerm.resources/get-azurermresource?view=azurermps-6.1.0&preserve-view=true).
+To fix this issue, update your runbooks to use `Get-AzureRmResource` instead of `Find-AzureRmResource`. For more information, see the [usage of Get-AzureRmResource](/previous-versions/powershell/module/azurerm.resources/get-azurermresource).
 
 [!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

support/azure/azure-functions/monitoring/functions-monitoring-appinsightslogs.md

@@ -1,8 +1,8 @@
 ---
 title: Application Insights logs are missing or incorrect
 description: Ths article helps you resolve issues related to missing or incorrect logs for Application Insights logs in Azure Functions.
-ms.date: 08/24/2023
-ms.reviewer: gasridha, v-jayaramanp
+ms.date: 01/16/2025
+ms.reviewer: gasridha, v-jayaramanp, agaltrai, jarrettr 
 ms.custom: sap:Monitoring using Application Insights, Metrics and Alerts
 ---
 
@@ -30,6 +30,23 @@ If the Application Insights logs are missing, or if the data appears to be parti
 
   **Recommendation**: The function app should be on version 4 and the runtime version should be at least 4.15.2*xx*. This is because, from this version onwards, you can track the log flows from Azure Functions to the Application Insights service. By monitoring the log flows, you can check for missing logs.
 
+## Custom application logs
+
+By default, custom application logs you write are sent to the Functions host, which then sends them to Application Insights under the [Worker category](/azure/azure-functions/configure-monitoring#configure-categories). However, some language stacks allow you to send the logs directly to Application Insights, which gives you full control over how logs you write are emitted. In this case, the logging pipeline changes from `worker > Functions host > Application Insights` to `worker > Application Insights`.
+
+The following table summarizes the configuration options available for each stack:
+
+| Language stack | Where to configure custom logs |
+|-|-|
+| .NET (in-process model) | `host.json` |
+| .NET (isolated model) | Default (send custom logs to the Functions host): `host.json`<br/>To send logs directly to Application Insights, see [Configure Application Insights in the HostBuilder](/azure/azure-functions/dotnet-isolated-process-guide#application-insights).  |
+| Node.JS | `host.json` |
+| Python | `host.json` |
+| Java | Default (send custom logs to the Functions host): `host.json`<br/>To send logs directly to Application Insights, see [Configure the Application Insights Java agent](/azure/azure-monitor/app/monitor-functions#distributed-tracing-for-java-applications). |
+| PowerShell | `host.json` |
+
+When you configure custom application logs to be sent directly, the host no longer emits them, and `host.json` no longer controls their behavior. Similarly, the options exposed by each stack apply only to custom logs, and they don't change the behavior of the other runtime logs described in this article. In this case, to control the behavior of all logs, you might need to make changes in both configurations.
+
 ## Logs are missing or partial
 
 Application Insights collects log, performance, and error data. [Sampling configuration](/azure/azure-functions/configure-monitoring#configure-sampling) is used to reduce the volume of telemetry. The Sampling feature is enabled by default with the settings shown in the following [host.json](/azure/azure-functions/functions-host-json#applicationinsights) example. Excluded types aren't sampled.

support/azure/azure-kubernetes/create-upgrade-delete/error-code-cnidownloadtimeoutvmextensionerror.md

@@ -58,4 +58,4 @@ If you can't download these files, make sure that traffic is allowed to the down
 
 - [General troubleshooting of AKS cluster creation issues](troubleshoot-aks-cluster-creation-issues.md)
 
-[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
+[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

support/azure/azure-kubernetes/create-upgrade-delete/error-code-k8sapiserverconnfailvmextensionerror.md

@@ -30,7 +30,6 @@ When you try to start or create an AKS cluster, you receive the following error
 > "ExitCode": "51",
 >
 > "Output": "Thu Oct 14 18:07:37 UTC 2021,aks-nodepool1-18315663-vmss000000\\nConnection to
-
 ## Cause
 
 Your cluster nodes can't connect to your cluster API server pod.
@@ -51,4 +50,4 @@ In rare cases, the firewall's outbound IP address can be blocked if you've autho
 
 - [General troubleshooting of AKS cluster creation issues](troubleshoot-aks-cluster-creation-issues.md)
 
-[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
+[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

support/azure/azure-kubernetes/create-upgrade-delete/error-code-k8sapiserverdnslookupfailvmextensionerror.md

@@ -32,7 +32,6 @@ When you try to start or create an AKS cluster, you receive the following error
 > "ExitCode": "52",
 >
 > "Output": "Fri Oct 15 10:06:00 UTC 2021,aks- nodepool1-36696444-vmss000000\\nConnection to mcr.microsoft.com 443 port [tcp/https]
-
 ## Cause
 
 The cluster nodes can't resolve the cluster's fully qualified domain name (FQDN) in Azure DNS. Run the following DNS lookup command on the failed cluster node to find DNS resolutions that are valid.
@@ -63,9 +62,8 @@ Also verify that your DNS server is configured correctly for your private cluste
 
 > [!NOTE]
 > Conditional Forwarding doesn't support subdomains.
-
 ## More information
 
 - [General troubleshooting of AKS cluster creation issues](troubleshoot-aks-cluster-creation-issues.md)
 
-[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
+[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]