Merge branch 'main' of https://github.com/microsoftdocs/SupportArticles-docs-pr into main1224

Author: genlin

.openpublishing.redirection.developer.json

@@ -5834,6 +5834,14 @@
     {
       "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"
     }
   ]
 }

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-monitor/app-insights/telemetry/java-standalone-troubleshoot.md

@@ -2,7 +2,7 @@
 title: Troubleshoot Azure Monitor Application Insights for Java
 description: This article presents troubleshooting information for the Java agent for Azure Monitor Application Insights.
 ms.topic: conceptual
-ms.date: 11/06/2024
+ms.date: 01/15/2025
 editor: v-jsitser
 ms.reviewer: aaronmax, jeanbisutti, trstalna, toddfous, heya, v-leedennis
 ms.service: azure-monitor
@@ -253,6 +253,32 @@ You can also try the [monitoring solutions for Java native](/azure/azure-monitor
 - With Spring Boot, the Microsoft distribution of the OpenTelemetry starter.
 - With Quarkus, the Quarkus Opentelemetry Exporter for Microsoft Azure.
 
+
+## Understand duplicated operation IDs
+
+Application logic can result in an operation ID being reused by multiple telemetry items, as shown in [this example](/azure/azure-monitor/app/distributed-trace-data#example). The duplication might also come from incoming requests. To identify this, do the following operations:
+
+* Enable the capture of the `traceparent` header in the **applicationinsigths.json** file as follows:
+
+    ```json
+      {
+        "preview": {
+          "captureHttpServerHeaders": {
+            "requestHeaders": [
+              "traceparent"
+            ]
+          }
+        }
+      }
+    ```
+* Enable [self-diagnostics](/azure/azure-monitor/app/java-standalone-config#self-diagnostics) at the DEBUG level and restart the application.
+
+    In the following log example, the operation ID comes from an incoming request, not Application Insights:
+
+    ```output
+    {"ver":1,"name":"Request",...,"ai.operation.id":"4e757357805f4eb18705abd24326b550)","ai.operation.parentId":"973487efc3db7d03"},"data":{"baseType":"RequestData","baseData":{...,"properties":{"http.request.header.traceparent":"00-4e757357805f4eb18705abd24326b550-973487efc3db7d03-01", ...}}}}
+    ```
+
 [!INCLUDE [Third-party disclaimer](../../../../includes/third-party-disclaimer.md)]
 
 [!INCLUDE [Azure Help Support](../../../../includes/azure-help-support.md)]

support/azure/azure-storage/blobs/alerts/storage-explorer-troubleshooting.md

@@ -154,9 +154,13 @@ Having to reenter credentials is most likely the result of Conditional Access po
 
 To reduce the frequency of having to reenter credentials because of errors like the preceding ones, talk to your Microsoft Entra admin.
 
-### Conditional access policies
+### Other conditional access policy issues
 
-If you have conditional access policies that need to be satisfied for your account, make sure you're using the **Default Web Browser** value for the **Sign in with** setting. For information on that setting, see [Changing where sign-in happens](/azure/storage/common/storage-explorer-sign-in#changing-where-sign-in-happens).
+If you have other conditional access policies that need to be satisfied for your account, try using either the **Authentication Broker** or **Default Web Browser** value for the **Sign in with** setting. For information on that setting, see [Changing where sign-in happens](/azure/storage/common/storage-explorer-sign-in#changing-where-sign-in-happens).
+
+### Issues with authentication broker on Windows
+
+The Windows operating system uses the Web Account Manager (WAM) as its authentication broker. If you're using the **Authentication Broker** sign-in method on Windows and experience issues, see [this guide](/entra/msal/dotnet/advanced/exceptions/wam-errors) for steps to resolve common errors.
 
 ### Browser complains about HTTP redirect or insecure connection during sign-in
 

support/azure/azure-storage/files/file-sync/file-sync-troubleshoot-cloud-tiering.md

@@ -4,7 +4,7 @@ description: Troubleshoot common issues with cloud tiering in an Azure File Sync
 author: khdownie
 ms.service: azure-file-storage
 ms.topic: troubleshooting
-ms.date: 10/24/2024
+ms.date: 01/13/2025
 ms.author: kendownie
 ms.reviewer: vritikanaik, v-weizhu
 ms.custom: sap:File Sync
@@ -103,6 +103,7 @@ If content doesn't exist for the error code, follow the general troubleshooting
 | 0x800703e3 | -2147023901 | ERROR_OPERATION_ABORTED | The file failed to tier because it was recalled at the same time. | No action required. The file will be tiered when the recall completes and the file is no longer in use. |
 | 0x80c80264 | -2134375836 | ECS_E_GHOSTING_FILE_NOT_SYNCED | The file failed to tier because it hasn't synced to the Azure file share. | No action required. The file will tier once it has synced to the Azure file share. |
 | 0x80070001 | -2147942401 | ERROR_INVALID_FUNCTION | The file failed to tier because the cloud tiering filter driver (*storagesync.sys*) isn't running. | To resolve this issue, open an elevated command prompt and run the following command: `fltmc load storagesync`<br/>If the Azure File Sync filter driver fails to load when running the `fltmc` command, uninstall the Azure File Sync agent, restart the server, and reinstall the Azure File Sync agent. |
+| 0x80c86041 | -2134351807 | ECS_E_AFS_FILTER_NOT_LOADED | The file failed to tier because the cloud tiering filter driver (*storagesync.sys*) isn't running. | To resolve this issue, open an elevated command prompt and run this command `fltmc load storagesync`. <br/>If the Azure File Sync filter driver fails to load when running the `fltmc` command, uninstall the Azure File Sync agent, restart the server, and reinstall the Azure File Sync agent. |
 | 0x80070070 | -2147024784 | ERROR_DISK_FULL | The file failed to tier due to insufficient disk space on the volume where the server endpoint is located. | To resolve this issue, free at least 100 MiB of disk space on the volume where the server endpoint is located. |
 | 0x80070490 | -2147023728 | ERROR_NOT_FOUND | The file failed to tier because it hasn't synced to the Azure file share. | No action required. The file will tier once it has synced to the Azure file share. |
 | 0x80c80262 | -2134375838 | ECS_E_GHOSTING_UNSUPPORTED_RP | The file failed to tier because it's an unsupported reparse point. | If the file is a Data Deduplication reparse point, follow the steps in the [planning guide](/azure/storage/file-sync/file-sync-planning#data-deduplication) to enable Data Deduplication support. Files with reparse points other than Data Deduplication aren't supported and won't be tiered.  |

support/azure/azure-storage/files/file-sync/file-sync-troubleshoot-installation.md

@@ -4,7 +4,7 @@ description: Troubleshoot common issues with installing the Azure File Sync agen
 author: khdownie
 ms.service: azure-file-storage
 ms.topic: troubleshooting
-ms.date: 01/03/2025
+ms.date: 01/13/2025
 ms.author: kendownie
 ms.custom: sap:File Sync
 ---
@@ -67,6 +67,11 @@ MSI (s) (0C:C8) [12:23:40:994]: Note: 1: 2265 2:  3: -2147287035
 
 For this example, the agent installation failed with error code -2147287035 (ERROR_ACCESS_DENIED).
 
+<a id="agent-installation-gpo"></a>**Agent installation fails with error ERROR_NO_SYSTEM_RESOURCES and error code 0x800705AA**
+
+The agent installation failed due to insufficient system resources. To resolve this issue, free up memory on the server and retry installation.
+
+
 <a id="agent-installation-gpo"></a>**Agent installation fails with error: Storage Sync Agent Setup Wizard ended prematurely because of an error**
 
 In the agent installation log, the following error is logged:
@@ -174,7 +179,7 @@ This issue occurs due to a known issue that has been fixed in File Sync Agent v1
 
 :::image type="content" source="media/file-sync-troubleshoot-installation/server-already-registered-error.png" alt-text="Screenshot that shows the Server Registration dialog box with the 'server is already registered' error message.":::
 
-This message appears if the server was previously registered with a Storage Sync Service. To unregister the server from the current Storage Sync Service and then register with a new Storage Sync Service, complete the steps that are described in [Unregister a server with Azure File Sync](/azure/storage/file-sync/file-sync-server-registration#unregister-the-server-with-storage-sync-service).
+This message with error code 0x80C80064 appears if the server was previously registered with a Storage Sync Service.  To unregister the server from the current Storage Sync Service and then register with a new Storage Sync Service, complete the steps that are described in [Unregister a server with Azure File Sync](/azure/storage/file-sync/file-sync-server-registration#unregister-the-server-with-storage-sync-service).
 
 If the server isn't listed under **Registered servers** in the Storage Sync Service, on the server that you want to unregister, run the following PowerShell commands:
 

support/azure/azure-storage/files/file-sync/file-sync-troubleshoot-sync-errors.md

@@ -280,6 +280,13 @@ No action required. Azure File Sync has a scheduled task (VssSyncScheduledTask)
 | **Error string** | WININET_E_TIMEOUT |
 | **Remediation required** | Yes |
 
+| Error | Code |
+|-|-|
+| **HRESULT** | 0x80072EFE |
+| **HRESULT (decimal)** | -2147012866 |
+| **Error string** | WININET_E_CONNECTION_ABORTED |
+| **Remediation required** | Yes |
+
 This error can occur whenever the Azure File Sync service is inaccessible from the server. You can troubleshoot this error by working through the following steps:
 
 1. Verify the Windows service *FileSyncSvc.exe* is not blocked by your firewall.

support/azure/azure-storage/files/file-sync/file-sync-troubleshoot-sync-group-management.md

@@ -4,7 +4,7 @@ description: Troubleshoot common issues in managing Azure File Sync sync groups,
 author: khdownie
 ms.service: azure-file-storage
 ms.topic: troubleshooting
-ms.date: 12/16/2024
+ms.date: 01/13/2025
 ms.author: kendownie
 ms.reviewer: v-weizhu
 ms.custom: sap:File Sync
@@ -100,7 +100,7 @@ This error occurs because Azure File Sync doesn't support server endpoints on vo
     compact /u /s
     ```
 
-<a id="-2134376345"></a>**Server endpoint creation fails, with this error: "MgmtServerJobFailed" (Error code: -2134376345 or 0x80C80067)**
+<a id="-2134376345"></a>**Server endpoint creation fails with this error message: "The server endpoints per server limit has been reached" (Error code: -2134376345 or 0x80C80067)**
 
 This error occurs if the limit of server endpoints per server is reached. Azure File Sync currently supports up to 30 server endpoints per server. For more information, see
 [Azure File Sync scale targets](/azure/storage/files/storage-files-scale-targets?toc=/azure/storage/filesync/toc.json#azure-file-sync-scale-targets).

support/azure/azure-storage/files/file-sync/file-sync-troubleshoot.md

@@ -4,7 +4,7 @@ description: Troubleshoot common issues that you might encounter with Azure File
 author: khdownie
 ms.service: azure-file-storage
 ms.topic: troubleshooting
-ms.date: 08/01/2024
+ms.date: 01/13/2025
 ms.author: kendownie
 ms.custom: sap:File Sync
 ---
@@ -97,13 +97,18 @@ After installing or upgrading the Azure File Sync agent (v17.3 or later), you ma
   Error 0x80070057: The parameter is incorrect. 
   ```
 
-- Registering a server using the Register-AzStorageSyncServer cmdlet fails with the following error: 
+- Registering a server using the `Register-AzStorageSyncServer` cmdlet fails with the following error: 
 
   ```
   Register-AzStorageSyncServer: Exception of type 'Commands.StorageSync.Interop.Exceptions.ServerRegistrationException' was thrown.
   ```
 
 - ServerRegistration.exe or AfsUpdater.exe fails to open
+- Agent installation fails. The installation log shows the error code 0x80c84111 with the following message:
+
+  ```output
+  Exception occurred while configuring MitigationRedirection policy. This could indicate that required windows updates not installed on the computer.
+  ```
 
 This issue occurs because the Azure File Sync agent has a dependency on a Windows security feature and updates for this security feature are not installed.
 

support/azure/virtual-machines/linux/how-to-use-perfInsights-linux.md

@@ -19,8 +19,6 @@ ms.author: genli
 
 **Applies to:** :heavy_check_mark: Linux VMs
 
-[!INCLUDE [CentOS End Of Life](../../../includes/centos-end-of-life-note.md)]
-
 [PerfInsights Linux](https://aka.ms/perfinsightslinuxdownload) is a self-help diagnostics tool that collects and analyzes the diagnostic data, and provides a report to help troubleshoot Linux virtual machine performance problems in Azure. PerfInsights can be run on supported virtual machines as a standalone tool, or directly from the portal by using [Performance Diagnostics for Azure virtual machines](../windows/performance-diagnostics.md).
 
 If you are experiencing performance problems with virtual machines, before contacting support, run this tool.
@@ -199,11 +197,10 @@ The following categories of rules are currently supported:
     | Distribution               | Version                                         |
     |----------------------------|-------------------------------------------------|
     | Oracle Linux Server        | 6.10 [`*`], 7.3, 7.5, 7.6, 7.7, 7.8, 7.9 |
-    | CentOS                     | 6.5 [`*`], 7.6, 7.7, 7.8, 7.9                                    |
-    | RHEL                       | 7.2, 7.5, 8.0 [`*`], 8.1, 8.2, 8.6, 8.8                               |
-    | Ubuntu                     | 14.04, 16.04, 18.04, 20.04, 22.04                               |
-    | Debian                     | 8, 9, 10, 11 [`*`]                                    |
-    | SLES                       | 12 SP4 [`*`], 12 SP5 [`*`], 15 [`*`], 15 SP1 [`*`], 15 SP2 [`*`], 15 SP4 [`*`]                                      |
+    | RHEL                       | 7.4, 7.5, 7.6, 7.7, 7.8, 7.9, 8.0 [`*`], 8.1, 8.2, 8.4, 8.5, 8.6, 8.7, 8.8, 8.9                               |
+    | Ubuntu                     | 16.04, 18.04, 20.04, 22.04                               |
+    | Debian                     | 9, 10, 11 [`*`]                                    |
+    | SLES                       | 12 SP5 [`*`], 15 SP1 [`*`], 15 SP2 [`*`], 15 SP3 [`*`], 15 SP4 [`*`], 15 SP5 [`*`], 15 SP6 [`*`]                                     |
     | AlmaLinux                  | 8.4, 8.5                                               |
     | Azure Linux               | 2.0                                                   |
 
@@ -217,8 +214,6 @@ The following categories of rules are currently supported:
 
 - RHEL 8 doesn't have Python installed by default because both Python 2 and Python 3.6 are available. To install Python 3.6, run the `yum install python3` command.
 
-- Guest Agent information collection may fail on CentOS 6.x.
-
 - PCI devices information is not collected on Debian based distributions.
 
 - LVM information is partially collected on some distributions.