Merge branch 'main' into Branch-CI2957

Author: AmandaAZ

.openpublishing.redirection.developer.json

@@ -5838,6 +5838,10 @@
     {
       "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-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/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,7 +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 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,9 +67,9 @@ 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 with Error Code 0x800705AA**
+<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, please free up memory on the server and retry installation.
+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**

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 message: "The server endpoints per server limit has been reached" (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,16 +97,16 @@ 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 and installation log shows error code 0x80c84111 with message:
+- 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.
   ```
 

support/developer/webapps/iis/toc.yml

@@ -165,8 +165,6 @@ items:
     href: www-administration-management/enable-ssl-all-customers.md
   - name: Error when you configure 32-bit managed handlers
     href: www-administration-management/error-when-you-configure-32-bit-handlers.md
-  - name: HTTP error 400 when you send requests
-    href: www-administration-management/http-bad-request-response-kerberos.md
   - name: HTTPS connections fail and SSL bindings are deleted
     href: www-administration-management/https-connections-fail-ssl-bindings-deleted.md
   - name: IIS events are not displayed remotely
@@ -200,6 +198,8 @@ items:
     href: www-authentication-authorization/error-install-certificate.md
   - name: Exporting configuration files fails
     href: www-authentication-authorization/configuration-files-cannot-exported.md
+  - name: HTTP error 400 when you send requests
+    href: www-authentication-authorization/http-bad-request-response-kerberos.md
   - name: HTTP error 403.7
     href: www-authentication-authorization/http-403-forbidden-open-webpage.md
   - name: IIS authenticates browser clients

…nt/http-bad-request-response-kerberos.md …on/http-bad-request-response-kerberos.mdsupport/developer/webapps/iis/www-administration-management/http-bad-request-response-kerberos.md renamed to support/developer/webapps/iis/www-authentication-authorization/http-bad-request-response-kerberos.md support/developer/webapps/iis/www-administration-management/http-bad-request-response-kerberos.md renamed to support/developer/webapps/iis/www-authentication-authorization/http-bad-request-response-kerberos.md

@@ -1,9 +1,9 @@
 ---
 title: HTTP 400 error responses to HTTP requests
 description: Works around an HTTP 400 error that the HTTP request header is too long.
-ms.date: 05/14/2021
+ms.date: 01/10/2025
 ms.custom: sap:WWW Authentication and Authorization\Windows Authentication
-ms.reviewer: ivanpash
+ms.reviewer: ivanpash, paulboc
 ---
 # HTTP 400 Bad Request (Request Header too long) responses to HTTP requests
 
@@ -34,8 +34,7 @@ Decrease the number of Active Directory groups that the user is a member of.
 
 Increase the settings for the `MaxFieldLength` and the `MaxRequestBytes` registry entries on the server so that the user's request headers don't exceed these values. To determine the appropriate settings, use the following calculations:
 
-1. Calculate the size of the user's Kerberos token by using the formula described in the following article:  
-[Problems with Kerberos authentication when a user belongs to many groups](https://support.microsoft.com/kb/327825).
+1. Calculate the size of the user's Kerberos token by using the formula described in [Problems with Kerberos authentication when a user belongs to many groups](../../../../windows-server/windows-security/kerberos-authentication-problems-if-user-belongs-to-groups.md).
 
 2. Set the value of `MaxFieldLength` and `MaxRequestBytes` on the server to 4/3 * T bytes, where T is the user's token size in bytes. HTTP encodes the Kerberos token by using base64 encoding.
 
@@ -48,7 +47,8 @@ Depending on your application environment, you might also work around this probl
 
 By default, there is no `MaxFieldLength` registry entry. This entry specifies the maximum size limit of each HTTP request header. The `MaxRequestBytes` registry entry specifies the upper limit for the total size of the Request line and the headers. Typically, this registry entry is configured together with the `MaxRequestBytes` registry entry. If the `MaxRequestBytes` value is lower than the `MaxFieldLength` value, the `MaxFieldLength` value is adjusted. In large Active Directory environments, users may experience logon failures if the values for both these entries aren't set to a sufficiently high value.
 
-For IIS 6.0 and later, the `MaxFieldLength` and `MaxRequestBytes` registry keys are located at the following sub key:  
+For IIS versions shipped with Windows Server 2016 and later, the `MaxFieldLength` and `MaxRequestBytes` registry keys are located in the following subkey:  
+
 `HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters`
 
 Set the key values as shown in the following table:
@@ -68,12 +68,12 @@ Set the key values as shown in the following table:
 > [!IMPORTANT]
 > Changing these registry keys should be considered to be extremely dangerous. These keys allow larger HTTP packets to be sent to IIS. This, in turn, may cause Http.sys to use more memory. Therefore, such changes can increase the computer's vulnerability to malicious attacks.
 
-If `MaxFieldLength` is set to its maximum value of 64 KB, the `MaxTokenSize` registry value should be set to 3/4 * 64 = 48 KB. For more information about the `MaxTokenSize` setting, see [Problems with Kerberos authentication when a user belongs to many groups](https://support.microsoft.com/help/327825).
+If `MaxFieldLength` is set to its maximum value of 64 KB, the `MaxTokenSize` registry value should be set to 3/4 * 64 = 48 KB. For more information about the `MaxTokenSize` setting, see [Problems with Kerberos authentication when a user belongs to many groups](../../../../windows-server/windows-security/kerberos-authentication-problems-if-user-belongs-to-groups.md).
 
 ## References
 
-- [Http.sys registry settings for IIS](https://support.microsoft.com/help/820129/http-sys-registry-settings-for-windows)  
+- [Http.sys registry settings for IIS](../iisadmin-service-inetinfo/httpsys-registry-windows.md)  
 
-- [Error logging in HTTP API](https://support.microsoft.com/help/820729/error-logging-in-http-apis)
+- [Error logging in the HTTP server API](/windows/win32/http/error-logging-in-the-http-server-api)
 
-- [Problems with Kerberos authentication when a user belongs to many groups](https://support.microsoft.com/help/327825)
+- [Problems with Kerberos authentication when a user belongs to many groups](../../../../windows-server/windows-security/kerberos-authentication-problems-if-user-belongs-to-groups.md)